Learn how you can improve your business analysis with Agile story mapping, a technique that maps your stories back to business value. Thus you will be able to know if they make or save the company money and you will learn the benefits of bi-directional requirements traceability .
The “rightsizing” of user stories occurring during the planning of the next sprint in Scrum is not always an easy task to perform. Inexperienced teams have difficulties to split user stories into smaller chunks that still deliver business value and would rather use technical criteria. In this blog post, “Specifications by Example” author Gojko Adzic provides a new approach to achieve this goal using the hamburger as a reference. You identify the tasks making up a user story. Then you use this breakdown to identify different levels of quality for each step and create vertical slices to identify smaller deliverables, thus creating your next sprint’s hamburger.
Epics are used to get a bigger picture of user stories, but we need another level of abstraction. We need to bring together the various Epics that describe how our solution will evolve to its final endpoint, and how different functional teams and specialists will interact.
The Scrum Expectation Line is defined by Zsolt Fabók as the line that follows the expectations of the Product Owner during each sprint. In this blog post, he discusses the difference between the team capacity to deliver and what the Product Owner wants in each Sprint and explains how his team deals with it.
This article describes a Lean and Scalable Requirements Information Model that extends the basic team‐based agile requirements practices to the needs of the largest, lean‐thinking software enterprise. While fully scalable to all levels of the project, program and portfolio levels, the foundation of the model is a quintessentially lean and agile subset in support of the agile project teams that write and test all the code.
Henrik Larsson presents in this post the user stories lifecycle from their origin in a Minimum usable feature (MUF/MMF) to their validation by the product owner at the end of a Scrum sprint.
In this blog post, Sten Johnsen discusses the impact of moving uncompleted user stories from one Scrum sprint to another. He focuses on the unfinished user stories, its impact on the team velocity and its influence on the ability of the team to change.
Scrum Expert Copyright © 2009-2024 Martinig & Associates