Avoid putting your Scrum team in harm’s way by ignoring a capacity check during Sprint Planning, endangering the Sprint Goal—Making Your Scrum Work #23.
Join the DZone community and get the full member experience. There are plenty of failure possibilities with Scrum. Since Scrum is an intentionally incomplete framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, the Developers are ignoring a capacity check during the Sprint Planning, and as a result, the Scrum team creates a Sprint Goal that most likely cannot be accomplished. Join me and delve into the effects of this trust-shattering practice in less than 80 seconds. Let’s refresh our memories regarding the Sprint Planning, the capacity check, and what amount of work might be accomplished: Topic Two: What can be Done this Sprint? Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence. Selecting how much can be completed within a Sprint may be challenging.
