Sprint Preplanning meeting – occurs Tuesday before the sprint opens. Parties involved: Team Leads. Actions: talk about high level goals for the next sprint and what additional resources, if any, are required. Try to look more than one sprint into the future. Action items: Consult with smaller team and insert tickets for next sprint into backlog before Spring planning meeting. Get points associated with those tickets (Points Poker suggested as mechanism – currently exploring Jira add-in for this purpose).
Spring Planning Finalization Meeting – occurs Thursday before sprint opens. Parties involved: everyone on the team. Actions: Team Leads will review tickets for the next sprint and inform the entire team of their plan for the next sprint, including goals of what they intend to accomplish. Review of point assignments and feedback from entire team. Action items: revise tickets as needed. Ensure all tickets are well defined and workflow outlined (those that need to go to QA vs. those that don’t, etc.).
Sprint Review – occurs the Tuesday sprint closes. Parties involved: everyone on the team. Actions: Team Leads will demo their accomplishments. We will review open tickets and discuss why those didn’t get done. Action items: revise processes as needed.
Sprint Retrospective – occurs immediately following sprint review. Team Leads should remind team members to enter their thoughts prior to the meeting so that we can discuss those issues at this meeting. We will only be effective in this meeting if we have material to work with to discuss.
