Using Scrum effectively is more than just holding Sprint Planning, Daily Scrums, Sprint Reviews, and Sprint Retrospectives. As agile coaches are prone to say (and we agree), Scrum is a good start, but it’s not enough. Just doing the forms (“sure, we hold Sprint Planning events…”) isn’t going to make the difference.
If you really want to see a big difference in the amount of work that your team can do in a Sprint, there are a couple things you can do. In this blog post, we’re going to stuck with the workflow-based changes you will want to make and not get mired in the technical stuff you could also do. Why? Well, here’s the reality — if you focus on technical solutions to performance without addressing the fundamental workflow issues first, you’ll end up with a beautifully constructed product that will still take 10x more time and money than it needed to.
We’ll deal with the technical stuff later. Let’s get the fundamentals right first. Good news! There’s only three!
1. Avoid Technical Debt – Your team needs a DONEness definition that 1) they keep up to date and improve every chance they get and 2) they actually use! DONEness is not about being perfect – we’re human and teams will make mistakes. But a lot of those mistakes can be found before the Sprint ever ends if only we would pay attention while the work was being done.
2. Work Only on Small Backlog Items – The bigger the product backlog item, the greater the complexity, the greater the risk, the greater the cost. Unfortunately, building a software product is not the same as building, for example, a car. Building two cars will, by and large, cost you twice as much as building one car. Building a product backlog item that seems to be twice as complex will likely cost you 5-10x what the simpler item cost. It’s not a linear progression, it’s closer to an exponential progression. So, to reduce errors, work only on small backlog items.
3. Work Only on One or Two Backlog Items at a Time – In other words, keep your work in process low. The more backlog items your team has in progress at the same time, the more chance that team members will be interrupted to help other team members, causing context switching and loss of productivity. Doing more at the same time doesn’t get more done — it gets less done.
So, that’s the plan. If you REALLY want to be Agile, you’ve got to make some changes to how your teams do work. Just calling it a Sprint doesn’t make things better. Get a good DONEness definition in place and don’t compromise it. Work only on small backlog items and, even then, only on one or two at a time to reduce unnecessary overhead. Give it a shot!
If you have difficulties with these concepts or just have some questions, please feel free to contact us!
More About #Productivity
Sprint Goals: The Key to a Well-Executed Sprint
Sprint goals are key to a successful Sprint. They help keep the Scrum team on track and moving together in one direction. Without Sprint goals, the Scrum team can easily lose focus and get sidetracked. In this blog post, we'll discuss what sprint goals are and how they can help your Scrum team stay focused
What is a Sprint Demo? #AskArtisan
What's a Sprint Demo? It's typically a sure sign that your organization has no idea how to do a Sprint Review! I'll explain in this edition of #AskArtisan.
Do Scrum Team Members have to be Full Time? #AskArtisan
Scrum Team members CAN be part-time, but this week’s #AskArtisan video shares insight on helping them maximize their time, and pitfalls to look out for.
How Many People Should be on One Scrum Team? #AskArtisan
I'm often asked about the ideal number of people on one Scrum Team, but maybe a better question is why and how any number becomes too many?
How do you Plan for Support Time in a Sprint? #AskArtisan
Many Scrum Teams ask how to plan for support work in a Sprint. Can you plan the unplanned? There's no simple answer, but there IS an answer!
Can One Sprint Have Multiple Goals? #AskArtisan
Can you have more than one Sprint Goal in a single Sprint? I actually recommend it! In this video, I'll explain how it can improve Scrum team productivity.
How Are Product Goals and Sprint Goals Related? #AskArtisan
I'm often asked about Scrum goals; specifically Sprint Goals, Product Goals, and how they relate to each other. In this video, I'll tie them together for you.
What’s a Sprint Goal? #AskArtisan
Ever been out shopping only to get home and realized you didn't actually get what you needed? This is what happens to Scrum teams without a Sprint Goal!
What’s a Product Goal? #AskArtisan
The 2020 Scrum Guide introduced a new concept called the Product Goal, and many are still confused about the purpose and function of Product Goals.
Leave A Comment