No Estimates, No Approval, No Dice

Brian Dupperrouzel
Vice President, New York Office

If you work on a well-oiled execution team that can estimate, plan, and deliver the right results at the right time, most of the time, then congratulations, you don’t need to read any further. Go back to your charmed life (We are sure you are not self-delusional).

For the rest of us, executing technology projects - especially complex custom software development - in a new environment with a new team is inherently non-predictable. Teams take a while to gel, some teams never gel. Critical scope items are often discovered midway through the project, which drive additional cost and duration . Trimming scope is like eating kale. You know it’s good for you, but you toss it in salads or juices in a masked form, and rarely want to eat it straight . Yet executive management often requires a well-articulated scope, budget and duration in order to approve the project. It’s a catch-22. So what to do?

Planning or assessment phases often present a false precision for the expected outcome, and executives and consulting partners are often incentivized to get things started quickly to meet strategic goals and sales quotas. Let’s face it: an executive communicating uncertainty to her board or a consultancy doing the same to its partner is a quick ticket to a lower pay scale or out the door. Instead of having the honest, but difficult conversation about unknowns, it’s far less risky, and unfortunately more common, to express the utmost confidence, get approval, and move on.

When uncertainty rears its ugly head, fingers start pointing in every direction. Oftentimes the project delivery team is left holding the bag and must sacrifice quality to validate the false precision handed down from the assessment phase. Once you’ve headed down this path, the best you can hope for is that the only quality sacrificed is the quality of life of your people. You’ll accrue a costly morale debt for the organization , but if you’re lucky, you can manage attrition and offer rewards after the fact to show your gratitude.

Perhaps even more dangerous than incurring morale debt is sacrificing the quality of your product to meet a deadline. In the age of social media and the mobile, always-connected consumer, pushing a half-baked product to market can, and will, damage your brand before you have time to tweet “I’m sorry”.   The same dynamic applies to the tools and services you buy, build, and maintain for your employees. They hold you to the same high standard as your customers.

But enough doom and gloom, what are some solutions?

Unfortunately, if you’ve found yourself at the helm of a current project already doomed by unrealistic expectations and false precision baked in from the start, your options fall into two buckets: “Rub Some Dirt On It” or “Call a Timeout”.

“Rub Some Dirt On It”

Power through and manage morale and stakeholders the best you can. Occasionally, you can dream about better projects and greener pastures, but for the next six months you are sucking it up and building character. The blood will clot and the scars will heal. Never fear, a new internet meme will make you feel good about learning more from failure than success.

“Call a Timeout”

If the game is getting out of control and you fear you are setting your team up to lose, stop, take a breath, and assess. What’s going wrong? Don’t wait for the coroner’s call to perform the dreaded post-mortem. Get to the root problems (there may be more than one) and adjust accordingly. Take a page out of Brooks’ playbook, 40 years young this year, and don’t solve the problem by piling on more estimates and more false certainty. The wisdom in the Mythical Man Month has withstood the test of time. I quote “Until estimating is on a sounder basis, individual managers will need to stiffen their backbones and defend their estimates with the assurance that their poor hunches are better than wish-derived estimates.” (http://www.cs.virginia.edu/~evans/greatworks/mythical.pdf)

To truly achieve superior experiences for your team, partner, and customer, however, the solution needs to happen at project inception. Executives and consulting partners need to be vulnerable and admit their ability to precisely predict and control large and complex outcomes is a 50/50 proposition at best. Transparency feels like a modern trend, but Brooks recommended substituting transparency for questionable estimation techniques back in 1975, writing “We need to develop and publicize productivity figures, bug-incidence figures… and so on”.

Finally, ensure that your organization doesn’t reward big projects just for being big. If promotions and influence are driven by project headcount and budget, your leaders will seek bigger teams and bigger budgets, stacking the deck against their chances of success from the start. Don’t take my word for it. A Gartner survey found that IT projects with budgets exceeding $1 million were nearly 50% more likely to fail than projects with budgets under $350,000. (http://thisiswhatgoodlookslike.com/2012/06/10/gartner-survey-shows-why-projects-fail)

Starting small and recalibrating an outcome trajectory based on thinner slices is a better way to plan a larger effort. You’ll be able to generate real velocity data about your team and execution environment more easily. If you can feed  your team with 2 pizzas (http://www.businessinsider.com/jeff-bezos-two-pizza-rule-for-productive-meetings-2013-10) you’ll change the equation from “more communication” to “effective communication”. Lastly, designing for small, decentralized teams will allow them to move faster, creating a virtuous feedback loop that reinforces the core activity of software

development, namely, knowledge discovery. (http://cacm.acm.org/magazines/2013/1/158762-how-we-build-things/abstract)

Don’t roll the dice on your next project. Have the courage to start small, measure and publish velocity, and be transparent.

For another take on how Pariveda sees small teams, read Mike Strange’s post on “Putting the SWAT back inTeams”   https://www.linkedin.com/pulse/putting-swat-back-teams-michael-strange?trk=v-feed

Contact the authors: Brian Duperrouzel and Jack Warner

Brian Dupperrouzel

About the Author

Mr. Duperrouzel is a Vice President in New York and brings strong technology services experience and leadership to the Pariveda Solutions New York Management Team. He has spent his career analyzing business problems, architecting and designing technology solutions, and implementing those solutions for clients.

More Perspectives

Perspective
by Bruce Ballengee
Teaching Roots Run Deep
Perspective
by Kent Norman and Kevin Moormann
I’ll be Home in Five Story-points
Perspective
By Russell Clarkson
Is your Ecosystem a pipeline or a platform?
Perspective
by Dimitrios Vilaetis
Business Capabilities: a Spotlight for Strategic Decision Making
Perspective
by Russell Clarkson
Mark Your Exits
Perspective
by Bruce Ballengee
Leadership and Company Culture
Perspective
by Kerry Stover
I Know You Believe You Understood What You Think I Said
Perspective
by Brian Duperrouzel
How to Handle Management Kidnapping
Perspective
By Russell Clarkson
What Chuck Yeager Taught Me About Disruption
Perspective
by Brian Duperrouzel
Lessons on Project and Team Management
Perspective
by Bruce Ballengee
Consulting that Focuses on the Individual
Perspective
By Bruce Ballengee
Developing the Individual
Perspective
by Lori Dipprey
Why Performance Reviews are Here to Stay at Pariveda
Perspective
By Nathan Hanks
What it Means to be "in the People Business"
Perspective
By Bruce Ballengee
Pariveda Fin-Centric Design
Perspective
By Bruce Ballengee
Unleashing the Power of Humility
Perspective
By Mike Strange
4 Reasons to Leverage the Power of Small Teams
Perspective
By David Watson
The Benefits of Working in Teams
Perspective
by Sean McCall
Forget Coffee- Energize Your Work Morning
Perspective
By Allison Esenkova
Wearing Heels to the Top
Perspective
by David Watson
Work-Life Balance
Perspective
by Allison Esenkova
Listen to the Still Small Voice
Perspective
By Kerry Stover
Must Read Books from the COO
Perspective
By Russell Clarkson
Why You Should take a Massive Open Online Course
Perspective
By Scott Hajer
The Importance of Making Space to Think
Perspective
by Sean McCall
4 Ways Sports Can Benefit Careers
Perspective
By Russell Clarkson
Stand Up for Good Presentations
Perspective
by Derrick Bowen
How Much of your Project Value is At Risk Due to Cognitive Bias
Perspective
by Susan Paul
Capabilities as Building Blocks
Perspective
By Susan Paul
When Corporate Culture Undermines IT Success
Perspective
by Kent Norman
Limit, to Win It
Perspective
By Brian Duperrouzel
The Case for Onshore Technology Teams
Perspective
By Tim Hurst
Unlocking Marketing ROI Analytics
Perspective
by Brian Duperrouzel
Hippos and Cows are Stopping Your Machine Learning Projects
Perspective
By Jack Warner
Building Smart Deployment Pipeline
Perspective
By Tom Cunningham
The Sound of the Future
Perspective
By Scott Hajer
You Need Only One Kind of Recruiting Technology
Point of View
by Ansley Galjour
Continuous Brand Engagement
Perspective
By Marc Helberg
3 Ways You Can Begin to Take Patient Experience More Seriously
Perspective
By Ryan Gross
What Does It Really Mean to Operationalize a Predictive Model
Perspective
by Sophie Zugnoni
Did You Catch Machine Learning Fever?
Perspective
By Collins DeLoach
What does Cloud Transformation mean it IT?
Perspective
By Mike Strange
Untangling and Understanding DevOps
Perspective
by Clayton Rothschild
Blockchain in an Enterprise Setting
Perspective
by Mike Strange
DevOps a Practical Framework for Technology Process and Organizational Change
Perspective
by Julio Santos - Finity Member
Context as Currency
Perspective
by Oussama Housini
Why DevOps?
Perspective
by Dave Winterhalter
Data in the Dugout
Perspective
by Brian Duperrouzell
3 Tips to get the Blockchain Ball Rolling
Perspective
by Victor Diaz
6 Things to Consider when Choosing a Data Visualization Library
Perspective
By Julio Santos and Jon Landers
How Customer Context and Smarter Algorithms will Power the Next Level of Experiences and Engagement
Perspective
by Mike Strange
Can We Predict the Future?
Perspective
By Brian Duperrouzel
No Estimates, No Approval, No Dice
Perspective
By Marc Helberg
How AI Will Affect Your Patient’s Experience
Perspective
By Sean Beard and Brian Orrell
Life After Mobile
Perspective
by Phillip Manwaring
Let Serverless Solve the Tech Problems You Don't Have
Perspective
by Mike Strange
Bigger is Not Necessarily Better
Perspective
By Marc Helberg
Patient Experience – Taking the Next Step Through Machine Learning
Load More