Sprint Goals: Why the Plan Matters Less Than You Might Think
This information will help you take a BIG step toward having product dev, service, and support teams be self-managing. (Yes, really!)
Sprint Goals: The Key to a Well-Executed Sprint
What is Scrum?
The most popular Agile Development framework, Scrum, can be explained in many ways. If you're just trying to understand what Scrum is, this post is for you.
Gearing a Team for Maximum Outcomes
Creating a maximum outcome team is every ScrumMaster’s goal, but you must first understand how great teams form and what YOU need to do to create a great team.
Jim's 10 Tips for Scrum Development Teams
With COVID-19 forcing us all to learn about working from home, we're re-publishing our list of "Jim's 10 Tips for Scrum Development Teams," UPDATED for 2020!
Speeding up Your Scrum Teams
Effective Scrum use is more than Sprint Planning, Daily Scrums, and so on. To see a big difference in your team's Sprints, make these workflow changes.
Don't Waste Time in Sprint "Capacity" Planning
Trying to plan detailed capacity for a Sprint? Thankfully, there are two things we can do to make capacity planning easier (and faster) in Sprint Planning.
Why Shorter Sprints Give You a Competitive Edge
Shorter Sprints aren’t just a trend—they’re a strategic advantage. While Scrum allows Sprint lengths up to one calendar month, more and more teams are choosing to run 1- or 2-week Sprints. This post explores why shorter cycles reduce complexity, increase adaptability, and result in higher-performing teams—and how to experiment with Sprint length to find your team’s sweet spot.
Sprint in Trouble? Here’s What Great Scrum Teams Do Next
In Scrum, it’s not enough to deliver high-quality work. Teams must also take ownership of how the work is done and how they respond when things don’t go as planned. This post outlines five actions Scrum teams can take when they realize the Sprint Goal is at risk—and how to develop the habit of self-correction before it’s too late.
Why You Should Think Twice Before Changing Sprint Content
High-performing Scrum teams thrive on focus, commitment, and trust. Yet one of the fastest ways to erode that performance is to repeatedly change the Sprint after it’s begun. While Scrum allows flexibility, it’s not a license for chaos. In this article, we explore why scope changes during a Sprint are so damaging—and what leaders can do instead to protect team focus and boost long-term performance.
What to Do Instead of Extending a Sprint
Scrum Sprints provide empiricism, part of the Agile core beliefs, which is why extending a Sprint is never a good idea!