![]() Self-organization requires two critical elements: You can’t just tell the team to“self-organize and expect the magic to happen. Self-organization is a beautiful, albeit challenging, concept. That does not happen with a mere list of sprint backlog items. Whenever a new request or ticket appears, the team can assess whether it contributes to their sprint goal and prioritize accordingly. In such cases, a sprint goal helps keep the team grounded in what’s truly important. It’s not uncommon to plan a few key items during sprint planning just to realize after a few days that you are working on entirely different tasks. Framing sprint goals:Ī lot can happen within 1–2 weeks of sprint time, such as ad hoc bugs, priority changes, among many others. Why even bother with framing sprint goals? Isn’t just pulling tickets from the product backlog to the sprint backlog enough?Īlthough selecting tickets for the next sprint constitutes a vast majority of sprint planning, there are a few ways framing specific sprint goals brings value to the team. To put it into context, here are some examples of sprint goals: It isn’t necessarily a strict estimate but a committed declaration of intent.īy principle, achieving a sprint goal is a big step toward your overarching product goal: In simple terms, a sprint goal briefly explains what the team sets to achieve during a sprint. Hold the team accountable for sprint goals. ![]() Let’s revisit what a sprint goal is, its purpose, and how to use sprint goals. Although they are one of the most important aspects of scrum itself, they are sadly also one of the most neglected. Properly implemented sprint goals can help you propel the team to a new level. What are sprint goals? Why you need them and how to write them Writing about what I discovered along the way. Bart Krawczyk Follow Learning how to build beautiful products without burning myself out (again).
0 Comments
Leave a Reply. |