One of the questions I get asked a lot has to do with when a Sprint ends… what happens with all the work that isn’t finished at the end of the Sprint?
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.
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.
It's hard to stay productive when working from home, but we've got some tips that will make a real difference in your lives. Share them with your teammates!
One small change can make a BIG difference to your Product Owner success. Before worrying about putting value on backlog items, here's some simple tips.
When slicing a backlog item, we're taking a complex problem and paring it down into smaller problems, which are easier to solve and build.
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.
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.
What's the one thing YOU could do as a Scrum Master to improve your team's reliability, quality, and productivity? Read on and find out!
In this article, we'll discuss how a team bares responsibility for the Sprint and what should be done if they can’t get everything done they committed to.
Bigger requirements are more complex, which typically have greater risk, which leads to more cost and/or waste. In other words, bigger is DEFINITELY not better!
The fastest team productivity killer is working on 3+ backlog items at once. You'll end up with a team that's great at starting work, but lousy at finishing it.