How to Build a Useful Sprint Backlog

A Sprint Backlog isn’t just a list of tasks—it’s the engine that drives a Scrum team through the sprint. In this Scrum Foundations lesson, Mike Cohn breaks down the three elements every Sprint Backlog must include: a clear Sprint Goal, the subset of Product Backlog Items the team selects, and a flexible, collaborative plan for getting the work done. You’ll see why a strong Sprint Goal gives teams both focus and freedom—clarity on what to achieve without dictating how to achieve it. Mike shares a real example from a data visualization team whose goal was simple (“triple chart throughput”), yet required thoughtful experimentation and teamwork to reach. You’ll also learn why Sprint Backlogs must remain emergent. Even the best teams can’t think of every step up front—and they shouldn’t try. As complexity unfolds, new tasks appear. That’s not scope creep; that’s reality. The key is knowing the difference between adding tasks and adding new Product Backlog Items, which should almost never happen mid-sprint. This lesson helps teams plan confidently, adapt intelligently, and avoid the trap of treating the sprint backlog like a rigid contract. 👉 Want deeper skills in planning, story slicing, and coordinating fast-moving work? Explore the Agile Skills Video Library: https://www.mountaingoatsoftware.com/training/courses/agile-skills-video-library?utm_source=YouTube Chapters 00:00 What Should Be Included in the Sprint Backlog 00:21 Sprint Goal 01:04 Product Backlog Items to be Worked On 01:23 Sprint Plan 01:48 Tasks 02:20 Adding Tasks Vs Backlog Items to the Sprint