A Management Bug is a problem, cause, or impact in a human manager’s decision that produces an incorrect or unexpected result.
Since we believe the Management Bugs are common and typical, every description is created and adapted from articles, blog posts, and definitions from other sources and authors.
This week’s MngtBug is…
This week’s “Lack of Sprint Planning” is a particular Scrum implementation problem.
By definition, sprint planning is the work to be performed in the Sprint. It is time-boxed to a maximum of eight hours for a one-month Sprint.
The purpose of the Sprint Planning is to answer these questions:
- What can be delivered in the Increment resulting from the upcoming Sprint?
- How much work will be needed for the Increment to be delivered?
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment. (1)
The purpose of the ceremony is to align the team on what they will be working on during the upcoming Sprint to ensure that their efforts are focused on delivering the highest priority work items in a quality manner while maintaining a sustainable pace of work. Successful sprint planning lays the foundation for a successful sprint. (3)
Without proper Sprint planning the team risks to have:
- missed deadlines
- missed expectations
- undelivered sprints
- working overtime
- excessive pressure & stress
- inability to plan & adjust.
Poor planning is how plenty of projects screw themselves up before they even begin. That’s why Scrum has particular practices around it. Want to have reliable estimates? Involve everyone in evaluation, keep a…