Scrum Schedule In Practice
The scrum meeting schedule I set up for my teams at one place I gigged at was as follows, and based on the basic sprint/release cycle. Our sprints varied from 2-3 weeks; releases usually after two sprints. After doing 2 week, 3 week, and one month sprints I kinda like the 3 week cycle; at another place we did two week sprints BUT our team was cranking out code nonstop; we had none of the issues present in the giant health care corporate IT system (for instance, just to get a DEV server took almost three months).
Of course there were other meetings such as reviews of QA test plans, long term infrastructure meetings and pieces beyond the boundaries of the sprint.
SM = Scrum Master, BA = Business Analyst, the rest should be self explanatory.
| Meeting Name | Who | Occurance | Objective |
| Release Planning | Required: SM,BA’s Optional: Lead Dev,Lead QA |
1-2 weeks before start of Sprint | Review and update release/project backlog. |
| Business Story Planning | Required: SM,BA’s,Lead Dev,Lead QA | 1 week before start of Sprint | Review all stories for presentation at the Story Review, update backlog and sprint story list. Initial estimates. |
| Tech Story Planning | Required: SM,Lead Dev Optional: Dev Team |
< 1 week before start of Sprint | Identify any refactors/pattern breakouts/upgrades/etc. that need a tech story, initial estimate. |
| Story Review | Required: SM,BA’s,Dev Team,QA Team | First Day of Sprint | BA’s present story documents to team, all details are discussed. Meeting is at least two hours long. |
| Story Tasking | Required: SM,Dev Team | First Day of Sprint | All stories are initially tasked out, initial task responsibilities are taken by team members the rest are left on the queue. |
| Daily Scrums | Required: SM,Dev Team,QA Team Optional: BA’s | Everyday in Sprint, except major meeting days | Scrum. The three questions: Yesterday, today, impediments. |
| Code Review | Required: SM,Dev Team | Last day of Sprint. | Dev team members present to each other their code (Note: these may informally occur as stories emerge during a sprint as well). |
| Release Demo | Required: SM,BA’s Optional: Dev Team,QA Team |
End of Release | BA’s/Team members present application features to usually high level stakeholders. |
| Retrospective | Required: SM,Dev Team,QA Team Optional: BA’s, |
End of Release | Review the process, improve if needed. |