Skip to content

Planning Guide

Plannings should be scheduled and conducted by the Tutor Scrum Master (SM); the Tutor Tech Lead should lead all technical discussions and task delivery planning. Below is a clear guide to the most important steps of a planning session.

  1. Presentation of the sprint's business refinement: Present the sprint's business refinement to make it very clear what the proposed value delivery is for this sprint.
  2. Presentation of the sprint's detailed epics: Present the detailed epics with all the rules and acceptance criteria for that epic.
  3. Analyze and plan the epics' stories: With the architectural refinement in hand, discuss the scope of each story.
  4. Review the stories' tasks and plan the delivery: With the engineering refinement in hand, discuss the solutions for the tasks and who will work on each task.

Note

This process can be reviewed in retrospectives with the team. We recommend only modifying this process after these discussions.

Important Points

  1. At CI&T, tasks are normally estimated in hours and the story is estimated by the sum of the tasks' hours. In some cases, the hour value is converted into Story Points, but this is a very time-consuming and complex activity, especially for teams that are just starting their journey. Give preference to the Kanban throughput model. For this model to work well, it requires stories and tasks to be well-broken down and of more or less the same size. In our case, the stories and tasks already follow this pattern, helping to create a no estimations environment.

  2. It may seem like a lot to do in one planning session. If the team feels there won't be enough time to go over everything, the team can skip the document review phases and agree to use the documents as guides during the Sprint's development.