Skip to main content

Planning

The purpose of Planning is to define the upcoming Cadence Goal and outline the associated deliverables. This involves establishing clear objectives for the next iteration or work cycle, ensuring that the team understands what needs to be achieved and what specific outputs are expected. By setting a well-defined Cadence Goal, the Delivery Team can focus their efforts on high-priority tasks, align their work with strategic objectives, and measure their progress effectively throughout the Cadence. Additionally, specifying deliverables ensures that all team members are aware of their responsibilities and the tangible outcomes they need to produce, thereby promoting accountability and facilitating smooth workflow management.

Purpose​

The purpose is to establish the upcoming Cadence Goal and define the deliverables to ensure the team aligns their efforts and meets the defined objectives effectively.

Cadence​

It occurs once per Cadence in the hours leading up to the start of the planned Cadence.

Time​

This meeting, lasting no more than 30 minutes, focuses on determining team velocity and transferring an equivalent number of task points from the backlog into the new Cadence Task Board.

People​

The Delivery Team and Product Owner should be in attendance.

Inputs​

Artifact: Prioritized Product Statements
Artifact: Previous Retrospective Document

Output​

Artifact: Cadence Plan containing Cadence goal and deliverables
Artifact: Task Board Cadence assignments

Process​

Planning may be facilitated by Process Steward or Product Owner. The facilitator guides discussion through the following events, and ensures the Output Artifacts are completed.

  1. Review retrospective action items.
  2. Review expected team attendance for the upcoming Cadence.
  3. Using attendance figures, determine an expected Cadence velocity.
  4. Select tasks from the top of the Product Statements list with point values that total the determined velocity, and assign them to the upcoming Cadence.
    1. Ensure tickets brought into the Cadence have gone through Refinement.
    2. The Product Owner is responsible for having ticket priority established by the ordering of the issues in the Task Board.
    3. The Delivery Team has final say in what units of deliverability are brought into any Cadence.
    4. Teamwork and communication are required to keep priority and implementation in alignment.
  5. Determine what the Cadence Goal is based on the deliverables in the Cadence.
  6. The Delivery Team takes a vote of confidence, 0-5, on the ability to deliver the goal.
    1. If the vote of confidence averages to less than 4 out of 5, remove deliverables from the Cadence or re-determine the Goal, then revote. Repeat until a confidence of 4 out of 5 is reached.