Sprints — how we can plan

• A Sprint means planning your work for the next 2 to 4 weeks.
• During Pre-kick off + kick off meetings the Project Owner will agree how often the team will meet to:
  • Plan the work ahead and add tasks for the next 2 - 4 weeks into your Kanban or progress tracker.
  • Check in on what the squad needs from each other inStand ups — e.g. context, dependencies, progress, blockers, etc.
  • Reflect on the squad’s ways of working with a Retro

<aside> 💡 If your project is 🐓 Medium or 🦁 Large you will find Sprints useful. Otherwise you’ll likely not need them — you’ll already know what needs to happen.

</aside>

Kanban — how we can track progress

<aside> 💡 You don’t have to use a Kanban, but you do have to give visibility over your project’s progress

</aside>

• Kanban is how we track tasks to keep projects flexible and accommodate frequent changes.
• The central element is the Kanban board used to organise the work, split into Backlog, In Progress, Blocked and Done.
• Think of it as if we’re zooming into task level from the Timeline visualisation

This is how it could look