So I have a backlog of features and we are about to get started on a sizable project. I am working on defining the structure of our sprints and I'm interested in the communities feedback.
What I'm thinking is:
- One day sprint planning
- Fill the backlog and figure out what each dev will go after this sprint
- Three weeks of development
- GO! GO! GO!
- Daily stand up meeting
- Check to see if anyone needs help or feels off track
- Two days of sprint review
- code reviews happen here, stakeholder presentations
- One day sprint retrospective
- what did we get done in the last sprint? how can we do better next time?
Sprints should always end on a Tuesday (to avoid too much weekend stress).
Anything else? There is obviously more to agile than this. I want to provide the team with a simple outline of how we are going to operate as we get this project started.