Requirements
 |
Stewardship in Agile Software Architecture and Design Software architects typically don’t own the products that individual teams are creating, yet they help define a cohesive approach to developing the products and are often responsible for defining how different products interoperate. Scott Sehlhorst looks at the idea of architecture stewardship. |
|
 |
Brainstorming: A Great Tool for Business Analysts and Everyone Brainstorming is an extremely useful tool in business analysis. In order to yield maximum results, brainstorming sessions need to be well planned and consider the needs and preferences of the attendees. Adrian Reed provides useful tips for preparing a brainstorming session. |
|
 |
A New Software Development Manifesto for Building the Right Things Author and software consultant Gojko Adzic recently gathered together a group of professionals to discuss software delivery and business outcomes, and to identify the core ideas that could be shared with delivery teams to help them focus on building the right things. |
|
 |
The Outside-In Approach to Product Positioning Early on product positioning helps drive focus and clarity for the team and allows a stakeholder to approach funding decisions from a strategic perspective. Scott Sehlhorst highlights some outside-in approaches to product positioning and their benefits. |
|
 |
Reconsidering User Stories User stories, one of the most common agile techniques, are used by delivery teams to support their iterative planning efforts and are typically used to represent items in a backlog. Until recently there has been a general agreement about the form that user stories should take. |
|
 |
Resilience and the Softer Side of Business Analysis Business analysis is a wide and varied discipline that relies on the practitioner's honing and developing skills in a number of areas. Adrian Reed looks at an important business analysis attribute that is rarely talked about—resilience. |
|
 |
User Story Mapping—Goal-Driven Backlog Development When product managers plan what product releases will include, the goal is to deliver value for the users. Every release of a product should make it better than the previous release. User story mapping is a technique for assuring that each release or iteration makes the product tangibly better. |
|
 |
How to Bring Requirements to Life A key skill of the business analyst is to elicit and analyze requirements and to help stakeholders consider a range of possible solutions. Because abstract and logical requirements are extremely hard to digest, Adrian Reed offers concrete ideas on how you can bring requirements to life. |
