Post-contract implementation
Sprint meeting
Sprint meeting
- Outline: A meeting to assess what was done and plan the work for the next Sprint.
- Frequency: Between two Sprints.
Review
- Goal: Present the results from the previous Sprint to the team
- Duration: 15 minutes.
How-to
- Start by doing a live demo of what was added with the current Sprint
- Modify or comment User Stories on Github according to the collected feedback
Planning
- Goal: Agree on what the team will work on during the Sprint.
- Duration: 30 minutes.
How-to
- Open the Project Board
- Go over the Done column and make sure the demo covered all of it
- Go over the remaining columns and make sure all issues are in the right place.
- Add new issues as per Sprint Prep decisions
- Tag User Stories with the version they're expected to be released
- Review the ultimate goal, making sure everyone has no further questions.
Engineering
- Goal: Ensure that the engineering tasks are efficiently distributed.
- Duration: 15-30 minutes.
How-to:
- The lead engineer goes over the User Stories breaking them into logical technical issues
- The technical issues must have a reference to the User Story they contribute to
- Issues are assigned to developers making sure there is a balance in effort