? SCRUM: A Typical Sprint, Play-By-Play

The first day: Sprint Planning ??

The whole team, including the Product Owner, meet on the first day 1???? of the Sprint and conduct a Sprint Planning session.

Ensure that the Product Backlog has been ordered and refined to an appropriate level of detail ???.

The team should have an idea of their capacity for this Sprint.

Plan which items from the Product Backlog should be worked on in this Sprint.

By the end of the Sprint a coherent feature may have been delivered, the Sprint Goal is a simple expression of this purpose.

The Sprint Backlog is a plan for meeting the Sprint Goal ??.

By the end of Sprint Planning, a team should be confident that it has made a good forecast ?? of the work that will be needed to meet the Sprint Goal.

Hold a Daily Scrum ???

Every working day, at the same time ?, the Development Team will meet and plan what they will do to bring them closer to the Sprint Goal.

This meeting is called the Daily Scrum and it should never take more than 15 minutes.

By the end of the Daily Scrum, the team should have a clear plan for the next 24 hours and an understanding ?? of how they will need to collaborate in order to achieve it.?

Refine the Product Backlog ??

Refinement is not a formal event but an ongoing activity.??

It’s up to Scrum Teams themselves to decide how often to do this.

Refinement shouldn’t take more than 10% ?? of a team’s total time during a Sprint.

The team starts at the top of the Product Backlog and works its way downwards ??, refining each item in turn.

Always collaborate ??

Any problems or failures are jointly owned by the team.

Examples of collaboration include:

1. ?? Helping peers to complete work in progress before bringing in new work from a backlog
2. ???????? Pair programming, such as taking in turns to use the keyboard and helping and checking each other’s work
3. ?????Peer review
4. Asking for help, and being keen to give it
5. Going to where the work is and helping, instead of waiting for work to be passed over to them
6. Making sure that all work does in fact meet the Definition of Done
7. ?? Calling a Scrum in order to resolve problems that need the team’s immediate attention
8. ??Raising impediments to the Scrum Master so they can be handled in a timely manner
9. Updating a Scrum Task board and burndown chart so that the information is up-to-date and can be relied on
10. ??Skill and knowledge sharing

?

The final day: Review and Retrospective

Hold a Sprint Review ??

The team will have a valuable increment ?? to demonstrate to the Product Owner and any invited stakeholders.

The team must prepare for it.

The review is an opportunity to celebrate ?? the work which has been done.

It’s a good time to get first-hand feedback from any invited parties.

Then conduct a Sprint Retrospective ??

The Sprint Review looked at the Product and the value delivered.

One approach is to identify ??:

1. ?Things that went well ??
2. ?Things that didn’t go so well ??
3. ?Ideas for improvement ??
4. ?Shout-outs to team members who did something exceptional ??

#scrum #sprint #playByPlay?

Src: https://www.scrum.org/resources/blog/typical-sprint-play-play