Scrum Events Best Practices

Highlights of key practices to ensure alignment across distant teams

Scrum Events create regularity and enable transparency.  Each event is clearly defined and centers around activities that facilitate inspection and adaptation. 

1.       Sprint Planning – Collaborative meeting where the Scrum Team plans the work to be performed in the next Sprint to deliver a usable increment. 

1.1.    Review the Product Backlog, discuss capacity, and forecast PBI’s

1.2.    Craft a Sprint Goal (brief, clear objective for the Sprint)

2.       Daily Scrum – Daily brief meeting for the Development Team to align on the plan for the day to meet the Sprint Goal.  

2.1.    Review the Sprint Goal

2.2.    Raise any blocking issues

2.3.    Align on plan for the day

3.       Sprint Review – Collaborative working session orchestrated by the Product Owner where the Scrum Team and Stakeholders can inspect the outcome of a Sprint and align on what to do next. 

3.1.    Demonstrate working increment

3.2.    Review the Product Backlog

3.3.    Discuss market changes, timeline, and budget

3.4.    Adapt Product Backlog, as needed

4.       Sprint Retrospective – Private meeting where only the Scrum Team can attend.  This meeting creates a virtuous cycle by reviewing the Scrum Team’s people, relationships, process, and tools to identify improvements that can be made. 

4.1.    Evaluation:

4.1.1.Did we reach our goal of the Sprint?

4.1.2.Did we release a usable increment?

4.1.3.Did we perform code reviews?

4.1.4.Did we follow architectural standards?

4.1.5.How can we improve on achieving our goals?

For more information about roles and artifacts, read the Scrum Organizational Framework.