Stop Estimating...
Increase productivity.
By doing less.
It's the promise of my weekly articles in THIS short LinkedIn newsletter.
I also publish a weekly Saturday morning email around the topic of "Implementing Scrum" (you can subscribe to that one at subscribe.mvizdos.com) and use cartoons that were created around the "Chicken and Pigs" concept in Scrum (see cartoon_origin.mvizdos.com).
The cartoon on the cover today is one of 100+ that were created over many years, and I figured since I created it, I'd bring it into the edition you are reading right now.
So...
The Problem:?We are constantly asked to provide estimates...
This week, imagine we are walking down a hallway to someplace IMPORTANT.
Your choice on where that hallway leads (use your imagination heh).
ME: "Hey, how are you?"
YOU: "I am spending more time creating estimates than actually working."
The Actionable Tip: Stop Estimating
Gulp.
"WAT Mike... are you CRAZY??????" [ you might be thinking ].
Remember, this is a thought exercise ONLY if it would be a career limiting move if you stopped providing estimates.
Or, is it (smile)?
There are plenty of frameworks out there to help us get stuff done.
One of the frameworks to help #deliver is called Scrum (you can learn more about that at www.ImplementingScrum.com).
Take a look at the 2020 Scrum Guide by my mentors and colleagues Ken Schwaber and Jeff Sutherland (I've got a free audio book and interactive online version available at scrumguide.mvizdos.com).
Search for the word "Estimate" in there.
It shows up ZERO times.
I'll let that idea hang in your brain for now.
You're welcome!
Your Next Step...
Think about the problem I've described and my actionable tip above.
Here is the part where?I need YOU contribute YOUR actionable tip?for others who are reading this article....
In the comments below, share ONE actionable tip on?what can (or does) happen once you STOP providing estimates.
Please share in the comments below.
Thank you.
Michael Vizdos
Senior Manager, Digital Engineering
2 年Michael Vizdos, as always, another great hot topic! There is a place for "no estimation" and there is a place for when estimates are needed. There isn't a world where this recommendation is a one size fits all. I have customers that just want to get to get stuff done. With those types, maturity is high, teams are self-organized, they are holding themselves accountable to meet the their goals, and possibly, the organization itself doesn't need estimates as a metric -- it's more about accomplishments. No estimation works in those types of environments, and there are other scenarios as well that are a bit more complex. Now, in my world -- that is consulting, time is money. Effort = dollars. I have an obligation to my customers to adhere to a budget as part of my service. We deliver using Scrum practices, but as part grooming and planning we estimate at the backlog level (for the Product effort), and task level (for the team member effort).
I advise and consult with companies in Print, Media & B2B Tech to help them grow and thrive. #PrintChat host. Bylines: Print Media Centr, LaManna Media, PIA, Label and Narrow Web, Seybold Report. ?? Grammarly Ambassador
2 年Love the cartoon. When I first glanced at it, I thought the bird was sitting in a hot tub -- and the caption works just as well with that scenario. ??
Driving IT innovation and excellence in cybersecurity. Building High Performing Teams | Startups | Cloud Solutions & Delivery | IT Compliance & Risk Management
2 年Heresy just plain heresy I tell you!!! ??
Chief of Staff to the CEO at Appfire
2 年Wait. So is "estimating" something that engineering-led-growth teams do? Is that another reason to go to scrum? (Not asking like some jerk. Asking in earnest.)