Agile Product Management: User Stories: How To Capture, And Manage Requirements For Agile Product M
Agile Product Management: User Stories: How To Capture, And Manage Requirements For Agile Product M >>> https://urlin.us/2tpWqI
Agile Product Management: User Stories: How To Capture, And Manage Requirements For Agile Product M
User stories are written throughout the agile project. Usually a story-writing workshop is held near the start of the agile project. Everyone on the team participates with the goal of creating a product backlog that fully describes the functionality to be added over the course of the project or a three- to six-month release cycle within it.
Some of these agile user stories will undoubtedly be epics. Epics will later be decomposed into smaller stories that fit more readily into a single iteration. Additionally, new stories can be written and added to the product backlog at any time and by anyone.
Because an epic is generally too large for an agile team to complete in one iteration, it is split into multiple smaller user stories before it is worked on. The epic above could be split into dozens (or possibly hundreds), including these two example user stories:
Whether or not a team is adhering to a certain agile practice (and which one), can further muddy the waters when it comes to what a product manager does. For instance, if a team is practicing scrum, then they also need to have a product owner.
A common challenge with writing user stories is how to handle a product's non-functional requirements. These are requirements that are not about specific functionality ("As a user of a word processor, I want to insert a table into my document."), but are rather about an attribute or characteristic of the system. Examples include reliability, availability, portability, scalability, usability, maintainability. As you can see from that list, non-functional requirements are often referred to as "-ilities." Of course, not all non-functional requirements end in "-ility." We also have security, performance, robustness and so on.
Thinking back into the dark ages, I can remember when I first read about "non-functional requirements." The term threw me for a loop. If it's non-functional, why do I care about it I'm sure the author of that book clarified this for me a page later, but the term has always seemed an odd one to me. I prefer to think of non-functional requirements as "constraints" we put on the system. When a product owner says, "this system must perform adequately with 100,000 concurrent users," the product owner is putting a constraint on the development team.
The product owner is effectively saying, "Develop this software any way you'd like as long as you achieve 100,000 concurrent users." Each constraint we put on a system narrows the design choices a bit; calling these "constraints" rather than "non-functional requirements" helps us remember this. Fortunately constraints/non-functional requirements can be easily handled as user stories. Here are a couple of examples:
Part of the confusion is that the product owner role is relatively new. It originated as part of the Scrum agile framework in software development, which has been around only a couple of decades. As Scrum and agile became more popular, businesses in industries other than software began to adopt the framework, creating jobs for product owners.
When we stated above that product owners manage the backlog, we did not mean they simply moved existing user stories and other task-level details around the backlog. Product owners must be more proactive than that. In many cases, they are responsible for drafting (or at least refining) these stories into tasks that the development team can execute on.
In a large organization, informal communication and simple backlogs are not sufficient for the management of requirements and development work. Many large organizations are struggling to successfully adopt agile methods, but there is still little scientific knowledge on requirements management in large-scale agile development organizations. We present an in-depth study of an Ericsson telecommunications node development organization which employs a large scale agile method to d