As a consultant, I’ve parachuted in to save a number of failing software projects.
Here are the most common problems I’ve faced:
Inexperienced team
The company “saves money” by staffing the team with Junior developers. This is especially common with startups. Junior developers are hungry but they need an experienced guide to lead them in the right direction.
Unfamiliar technology
Every company feels like a new product is a great time to revamp their technology stack. It makes sense, but be sure you have someone on the team who has the knowledge to lead the team in the right direction.
Slow delivery
When the team is repeating we’re 90% done but has nothing to show for it, you should be worried. Put the habits and tools in place for your team to continuously deliver what they’re building.
Lack of prioritization
Team’s often feel like order isn’t important. The whole thing has to be built anyway, so where we start doesn’t matter. That couldn’t be further from the truth. Think MVP. What could you build now that could have an immediate impact. Start there.
No product vision
If you don’t know where you’re going how can you map the way. Without a clear product vision, teams meander. Know where you are headed and why. Explain it to everyone on the team so it will guide their decisions.
So remember…
The most common reasons for failure are pretty consistent and entirely avoidable. How?
Bring in someone with decades of experience when you are getting started. I’ve come into projects that were millions over budget, years late, and we turned those projects into a success. These projects could have been completed for 10% or less of their eventual cost had the team received the right guidance up front.
Contact us to find out more.
Related posts:
- How to Rescue a Failing Software Project
- Product Vision is the Foundation of a Successful Agile Team
- Delivery is the Moment your Team Creates Value
More about the author: https://jacoborshalick.me