In this tutorial, we will discuss the Agile user story flow in a sprint.
Work is identified as part of an inception meeting. At this point, the work may be a very large scale, and will likely require breakdown and further analysis, a product backlog with the initial epics, stories would be created.
Backlog in Jira
When the work is likely to be scheduled for an upcoming sprint, the analyst begins breakdown and further analysis of the product backlog identified in the value increment planning meeting. In this stage, the analysis is working with technical members of the scrum team to refine the created stories and potentially break them into multiple stories if they are too large.
Story Review Session
Once a story has been refined to a degree where the analyst feels there is enough detail to play the story, the story is brought to a review session with members of the scrum team to ensure that it can be played, and is well understood. During this meeting, the analyst works with the delivery team to agree and further refine the acceptance criteria. The story estimate may be revised by the scrum team if the initial estimates were not accurate.
Stories are prioritized and are presented and aligned with the sprint goals for the upcoming sprint. The scrum team agrees to the total scope being added to the sprint and establishes any story dependency needs. Stories are added to the backlog for the sprint.
Sprint planning in Jira Cloud.
Product Owner, BA, and the scrum team meet with the objective to help ensure that the product backlog is populated with relevant user stories. They will help identify any missing or irrelevant user stories, dependencies, epic stories etc
The developer is assigned a story and briefly meets with Analyst and QA to ensure the story is well understood. Development ensues, and the developer constructs story acceptance criteria and coordinates on testing with QA as elements of the story are completed.
User Story Development
Development ensues, and the developer constructs story acceptance criteria and coordinates on testing with QA as elements of the story are completed. Pod level testing, ongoing regression
Demo & Code Review
The user story is deemed complete by development and walked through with the analyst before the developer moves to the next story. The code associated with the story is reviewed before integration with the mainline code branch.
Testing & Automation
The QA team in the scrum team performs story testing. The automation team completes automation for the sprint and ensures that the regression suite is refactored to include the new stories that were delivered.
Sprint Review & Signoff
BA/Product owner reviews the story for completeness and acceptance. The story is demonstrated along with the other work that was accomplished during a sprint.
RTP – Release to Production