
Project ManagementPlanning
How to Plan a 2-Week Cycle Without a Wasted Meeting
The cycle planning meeting often runs well beyond what it should, because it actually serves to do work that should have been done before it even started.
By Sinra Team
Browse all posts in this category

The cycle planning meeting often runs well beyond what it should, because it actually serves to do work that should have been done before it even started.

Three projects, one team, a single backlog that keeps growing without anyone knowing what belongs to what: this scenario always ends up slowing everyone down, not just the lowest-priority project.

The dev reads the user story: 'As a user, I want to log out to secure my account.' He asks: 'OK but concretely, what do I do?' Welcome to the world of vague user stories.

The Product Manager asks: 'What are we shipping in Q2?'. You open the backlog: 537 unsorted issues, 47 marked 'urgent', 12 different priorities. Nobody has an answer. Welcome to backlog chaos.