Related Content
 |
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. |
|
 |
Are You Experiencing Product Manager Insomnia? What should be keeping you awake is what keeps your customers awake. Remember to be market-driven and to focus on the problems that your customers value—and are willing to pay to solve. |
|
 |
Clean Language in Business Analysis Clean Language originated within the discipline of therapy and focuses on understanding other people’s personal metaphors. It can help business analysts to form better questions and prevent inadvertently leading or pre-supposing a solution. |
|
 |
The Right Way to Split User Stories One of the key techniques in the mechanics of agile software development is the splitting of epics into stories. Scott Sehlhorst highlights examples of ways to split user stories and discusses the debate between breadth-first and depth-first development. |
|
 |
Dodging the Requirements Hazard Tacit knowledge includes the knowledge that business stakeholders possess that isn’t codified or written down anywhere—and information they don’t even know they possess. The challenge for business analysts is that it is essential to get at this type of information in order to write requirements. |
