Mastering Advanced Scrum: Advanced Scrum Techniques for Scrum Teams, Roles, Artifacts, Events, Metrics, Working Agreements, Advanced Engineering Practices, and Technical Agility by Rituraj Patil

Author:Rituraj Patil [Patil, Rituraj]
Language: eng
Format: epub
Publisher: BPB Publications
Published: 2022-08-15T00:00:00+00:00

Figure 8.6: User Story Mapping process

The Story Map always needs to evolve with the Scrum Team’s overall understanding of user personas and the product features getting delivered for them. It is hence required for the team to perform opportunity assessments as a first step in the User Story Mapping process, using which they need to create an opportunity backlog to capture and record all the user needs, wants, and requests. They need to spend a significant amount of time and effort to understand all the details about who, what, and how aspects of user personas. They need to prioritize the opportunity backlog using the outcomes of their discussions. Before mapping the User Stories inside the Story Map, they need to frame the user specific Features. They need to evaluate on, what the features are all about and what problem is getting addressed by the delivery of those features. They also need to evaluate on, who all are the different types of users who will be using those features, how they will be using them, and what is the ultimate value and benefit they will be getting out of those features.

Detailing and confirming the Product Features using Discovery is the next step in User Story Mapping process, where the team needs to identify the Minimum Viable Product and its associated features. While acting as an enabler for the creation of the Product Backlog, the Discovery step needs to determine what the team is supposed to implement during their upcoming Sprints. The Scrum Team needs to explore and reflect on the problems and the corresponding possible, feasible, and useful solutions by considering the Feature Value Optimization. By mapping a big picture of user personas, user actions, and user behaviors, they need to focus on building up and overall understanding of the entire solutioning to be implemented by them. This is required for them to identify all the user activities with their corresponding workflows. During the discovery phase, such mapping of a big picture of user activities always needs to shape the backbone of the Story Map.

The Scrum Team then needs to break the features into multiple PBIs/User Stories. They also need to start defining, describing, and refining the User Stories/PBIs during the next steps of User Story Mapping process known as refinement and delivery. By utilizing the product team planning and story workshop sessions, the Scrum Team needs to discuss with the Stakeholders on the overall progress of Sprints and Release. It eases the refinement and selection of the work items for the upcoming Sprints.

The Scrum Team also need to plan and re-plan for their anticipated work to make their User Stories/PBIs ready for the upcoming Sprints. In this process, a Definition of Ready (DoR) needs to be formulated, refined, and followed by them. Refinements need to happen regularly to capture and record the details under the Product Backlog, where they also need to define and agree on a proper Acceptance Criteria and an agreed Definition of Done (DoD) for the PBIs/User Stories.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.