User Storys, Backlogs and Backlog Grooming compact

Whitepaper:

User Stories, Backlogs and Backlog Grooming compact

Format: PDF
Pages: 15
Filesize: 558 KB

As a basis for the agile release planning, sprint planning and team planning, the user stories have to be prioritized and estimated. Then the teams need backlogs for the planning steps as well as support for backlog management.

Businesses that have decided on the path to agility because Scrum has already worked well in small projects have large challenges ahead of them: in large projects, stakeholders‘ requirements are often highly complex. The project team has to understand requirements on the level of features and epics and refine them into traceable stories. As a basis for the agile release planning, sprint planning and team planning, the user stories have to be prioritized and estimated. That means: the teams need, first of all, techniques for agile requirements engineering. Then they need backlogs for the planning steps as well as support for backlog management.

What are user stories, what advantages do they offer, and how do you differentiate between features, epics, technical stories and spike stories? How do you manage these backlogs? And why should you regularly carry out backlog grooming? You can find the answers here:

Get your download-link here:

We will send a download-link to your email-address. Therefore please enter a valid email-address, your first and last name and that’s it:

* By submitting your email address you agree to receive information and tips about project management and requirements engineering. Of course you can always cancel that service.