Present the Principle of SCRUM
Sprint Planning Meeting
- Principle of organizing work by defined time slices (here 3 weeks).
- Define medium/long-term goals with the project manager and the technical lead.
- Review the past 3 weeks.
- Update the task board.
- Reduce the duration of weekly meetings.
Informative Purpose
Allows the team to know
- What everyone is doing in the project
- Follow a clear direction for the next 3 weeks.
Procedure
1. Review
- Sprint timeline: major events such as holidays, trade shows, etc.
- Open the milestone to see what is left in the milestone.
- Person by person, review what has been done during the previous sprint to know the state of the project.
2. Retrospective
Everyone will say what they think they did well or poorly, what they liked or disliked in the past 3 weeks. We can then highlight main themes. This allows for reflection and finding personal and common areas for improvement for the next sprint.
[!info] State what we liked and didn't like about our work during the previous sprint. This works in the form of post-its: + if we are happy, - if we are not.
We can mention:
- What slowed down the project
- What helped it
- What we liked
- What we didn’t like
- Upcoming risks that stress us
3. Planning
Next, with the project manager, technical lead, and engineers, define clear tasks for everyone based on
- Project priorities
- The backlog
[!info] All these tasks will go into the TO DO section.
Assign tasks to everyone. Doing this in the presence of everyone allows us to know who is doing what.
Articulate This With
Weekly Meetings
Allows to reduce the duration of weekly meetings.
Release Every 2 Sprints
So every month and a half.
Possibility of a Daily Meeting with a Small Team if We Have Problems
[!warning] Essential Condition: Subdivide the team by theme.