post

Footer About

Footer Get Involved

Footer Links

Mind the Product

General

Product Unplugged Episode 3 with Pierce Healy

Product Unplugged Episode 2 with Lorilyn McCue

Product Strategy

Building Product Teams

Diversity and Inclusion

Digital Transformation

Artificial Intelligence (AI) & Machine Learning (ML)

Product Leadership

Product Management Career

Product Ethics

Minimum Viable Product

Enterprise Product Management

OKRs

Customer Research

Hypothesis and Testing

Business Strategy

User Research

👩‍🚀🚀   Live now for MTP members: <a href="https://mtp2017stg.wpengine.com/membership/#events" style="color:#FFFFFF;text-decoration:underline;">Driving Innovation AMA with Tendayi Viki</a>

Roadmaps: Break the rules without breaking the principles

Got questions about your product career?

Product roadmaps vs data – Jeremy Levy on The Product Experience

From engineering to product management at Google

Mind the Product joins Pendo

To find out more, visit tremisskeete.co.uk.

Tremis Skeete

<p><a href="https://www.linkedin.com/in/davidkullmann">David Kullman</a> talks to ProductTank NYC about why most projects are doomed to fail right from the very start. David is a Partner and Development Manager at CitrusByte, working with both large corporations and startups to develop innovative software solutions to challenges they may be facing.</p>
<h2><strong>IT Project Failures – The Statistics</strong></h2>
<p>In 1995, IT spending amounted to around 250 billion dollars in the US alone. In 2015, the worldwide spending in IT was 3.4 trillion dollars. If the majority of projects succeeded, that money would have been well-spent. Unfortunately, that is not the case.</p>
<p>Only about 29 percent of projects ever succeed. Of the remaining, 52 percent are heavily challenged, and 19 percent are cancelled all together. What that means is of the 3.4 trillion dollars that was spent worldwide in 2015, about 2.4 trillion dollars was wasted on challenged or failed projects.</p>
<p>David goes on to explain that on average, successful IT projects are 222 percent late and 189 percent over-budget. Plus, once they are finished, most projects only see about 61 percent of their original scope being completed. Projects are taking twice as long and costing twice as much to only meet half of the original goal.</p>
<h2><strong>Why your project is doomed to fail </strong></h2>
<p>The process of starting a new project can shed some light on this. When the idea for a new project is hatched, people can be excited. Past failures seem distant because this new project seems different. They look for new methods that they’ve heard of and have been successful. Long-term concerns can develop early on, but action isn’t taken due to short-term focus. After the first few months, dates start to slip and expectations aren’t met. People start to realize that deadlines won’t be met and quality is missing. As they realize that it’s too late to fix things in the original timeframe, panic sets in. Eventually, the project fails despite new and improved methods and technology. To back this up, a study by IBM showed that 54 percent of projects fail because of project management, while only 3 percent fail due to technical issues.</p>
<h2><strong>The Size of the Project </strong></h2>
<p>The size of the project is partially to blame for failures. A study conducted by CHAOS Report showed that the larger a project is, the more likely it is to fail. This is mostly because smaller projects have less people involved, which means a tighter system of communication, easier access to resources, and less barriers. Brooks’ Law can support this, stating that “adding manpower to a late software project makes it later.”</p>
<h2><strong>Lack of Planning</strong></h2>
<p>Size is not the only contributing factor to projects failing. Another major cause is a lack of planning. Either the team doesn’t have the expertise or experience needed to plan properly, or planning is cut short to save time and resources. Often, this leads to a month-to-month outline, where each month is focussed on a certain iteration of the project.</p>
<h2><strong>Insufficient Resources</strong></h2>
<p>Frequently, developers will assume that the least expensive approach is always the best one. This often leads to cutting corners on their best practices, which then leads to severe shortcomings. Worst of all, there is often a delayed impact, meaning those shortcomings aren’t apparent until it is too late.</p>
<p>David states that investing in the right team for a project, or choosing the project based on the team’s expertise and experience, can go a long way in terms of the project succeeding.</p>
<h2><strong>People Management</strong></h2>
<p>People tend to be much better at coming up with ideas than sticking to plans. Because of this, it can be difficult for team members understand how and why plans change and certain ideas are dropped. David explains that there needs to be a vetting process in place for agreeing on an idea, and sticking to the plan. That way even though people may not like the idea, they can still understand and believe in the process and be fully vested in the project.</p>
<h2><strong>Takeaways</strong></h2>
<p>David explains that the point to his presentation was not to simply teach how to make your project succeed, but rather, how to setup your project to best avoid failure. In short, his three major pieces of advice are to plan large projects just as you would smaller ones, invest wisely as opposed to minimally, and use a cadence-based planning model with economic prioritization.</p>
<div class="g g-21"><div class="g-single a-75"><a class="gofollow" data-track="NzUsMjEsMSw2MA==" href="https://mtp2017stg.wpengine.com/product-management-training/public-workshops/"><img decoding="async" src="https://mtp2017stg.wpengine.com/wp-content/uploads/2021/10/General-Training-Level-up-FOOTER-scaled.jpg" /></a></div></div>

core/freeform

Product Management Characteristics

What makes for effective product management by Nikolaus Horn and Sebastian Ratcliffe

Walk a Mile in Their Shoes by Egan Cheung

In My Humble Opinion by Thor Mitchell

Mindset – Is Being a Product Manager the Worst Job? With Laurel Gray and Rosemary King

We can Build Better Things Together by Martin Eriksson

Be a Director, not a Manager by Fareed Mosavat

You Don’t Own the Voice of the Customer by Tricia Wang

The Mindset of Empowerment by Laura Scanga

Banish Your Inner Critic by Denise Jacobs

Product Management Strategies for Supporting Collaboration by Gretchen Anderson

Why your IT Project is Doomed to Fail – David Kullmann (ProductTank NYC)

ProductTank Columbus

ProductTank Tauranga

ProductTank Edinburgh

Prioritised Member AMA - Perfecting product roadmaps

ProductTank San Diego

Navigating difficult relationships panel

ProductTank Philadelphia

ProductTank Bucharest

ProductTank NoVa

Remote Training Workshops

ProductTank London

ProductTank Birmingham

ProductTank Oslo

ProductTank Astana

ProductTank NoVA

ProductTank Bratislava

ProductTank New York

ProductTank Kansas City

ProductTank Orlando

ProductTank Dallas

ProductTank Tokyo

ProductTank Belgrade

ProductTank Madrid

ProductTank Leeds

ProductTank Zürich

ProductTank Perth

ProductTank Chicago

ProductTank Auckland

ProductTank Richmond

ProductTank Charlotte

ProductTank Reston

ProductTank Washington

ProductTank Sofia

ProductTank Raleigh

ProductTank Ljubljana

ProductTank Kraków

ProductTank Barcelona

ProductTank Dublin

ProductTank Montréal

ProductTank Bogotá

ProductTank Seattle

ProductTank Madison

ProductTank Singapore

ProductTank Portland

ProductTank Budapest

ProductTank Porto

ProductTank Austin

ProductTank Los Angeles

ProductTank Norwich

ProductTank Des Moines

ProductTank San Francisco

ProductTank Helsinki

ProductTank Reading

ProductTank Brighton

ProductTank Valencia

ProductTank Bielefeld

ProductTank Malmö

ProductTank Canberra

ProductTank Manchester

#mtpcon SF+Americas 2022 Conference

#mtpEngage Hamburg 2022 Leadership Forum

#mtpEngage Hamburg 2022 Workshops

#mtpEngage Hamburg 2022 Conference

#mtpcon London+EMEA 2022 Conference