I’d like you to try this experiment. Take a planning activity that you and your software development team perform on a regular or intermittent basis and cut the allotted time to one tenth of what is normally expected. That’s it. Try it!
You read that correctly. You get 10% of the time that the activity would normally take. That means a week shortens to 4 hours. A month comes down to 2 days. Scary thought, isn’t it?
Here are some examples to get you thinking through this experiment:
- Prepare a product vision statement – Expected: 1 week. Allotted: 4 hours.
- Prepare project plan – Expected: 2 weeks. Allotted: 1 day.
- Write a user story – Expected: 30 minutes. Allotted: 3 minutes
- Write a test plan – Expected: 2 days. Allotted: about 90 minutes
- Lay out a UX design – Expected: 3 days. Allotted: about 2 and a half hours
- Estimate the time for a set of stories – Expected: 2 hours. Allotted: 12 minutes
You can do it.
It’s natural to think that you can’t reduce the usual time for an activity by 90% and still end up with anything of value — but you can. The point of the experiment is to change the way you and your team approach planning activities — you need to change thinking habits and establish new patterns.
We all fall into behavior patterns. After we’ve performed an activity multiple times, we naturally assume the activity will take a prescribed amount of time. Based on that, we structure our tasks such that we will finish the activity in the expected time.
There’s nothing wrong with natural behavior patterns — but they limit our ability to be agile. If you’re serious about improving how work gets done, you need to change how people approach their work. If you’re serious about creating better outcomes, you need to change the rules.
Cutting the expected time by 90% may seem overly drastic. 10% of the original time estimate may not be enough to achieve the quality results you need. That’s okay. The team will will learn a lot about what really matters in performing the target activity. Team members will also learn more about each other by undertaking this experiment. You’ll find ways to reduce the expected time — maybe not by 90% but 75%, 50% or even 25% reductions would be huge wins. Think about it.
Give it a try. You have nothing to lose. If you don’t like the result, very little time has been wasted and you can revert back to your normal approach. Please let me know how the experiment works out by leaving a comment.