Getting to the Bottom of Project Troubles

[article]
Summary:

It's amazing how many projects, already in a hole, keep sinking deeper. When team members and staff don't have the insight or objectivity to turn things around, an independent consultant can help—or not. In this column, a leading industry consultant gives you "the straight dope" on what to watch out for.

Have you ever said to yourself, "I'm in a hole and I can't get out"? It's amazing to me how many projects, in a hole already, keep sinking deeper. Is it because the only tool available is a shovel? Sometimes it's helpful if someone who is not in the hole with you gives you a hand. Can a project review by an independent consultant help? That depends. You say you've had some awful experiences with consultants brought in to review your project? I believe you. Here are four factors that will help make sure your independent project review pays off.

The Consultant's Independence from Solutions
Effective review of a project depends on the consultant's independence from possible solutions she might recommend. For instance, if you hire a consultant who is in the rope business, she will most likely recommend throwing you a rope. If she is in the business of providing programmers, then she'll recommend more programmers. Ideally, if you select a consultant who is in the business of recommending solutions but does not make a living from delivering the recommended solutions, then you will get an objective project review and helpful recommendations. This type of consultant will provide information about how your project got into its hole and useful recommendations for how to get out and stay out.

The Consultant's Experience 
A consultant's experience with recognizing what contributes to software project successes and failures is key to a successful review. A project's problems are often presented as strictly technical in nature or the fault of the technologists. But in my technical, management, and consulting experience, there are many factors in addition to technical ones that contribute. Projects are complex human systems in themselves. They involve business needs, technologies, processes, and people in a unique combination that is influenced by a company's culture, environment, and business objectives. Projects require executive sponsorship, project management, business-functional and work-process design expertise, technologies, infrastructure, and most of all, people. Project troubles typically involve all of these areas interacting with one another. And when executive sponsorship and management issues are strong contributors to the problem, the people down in the hole are reluctant to talk about them. If you're going to hire a consultant, be sure she has the courage to identify and address these issues with the executives who hired her.

The Client's Willingness to Look in the Mirror
The effectiveness of a review depends heavily on the organization's willingness to face its contribution to the project's trouble. No matter what the consultant recommends, if the organization wants to keep its head down in the hole, it will. If your organization is not ready to face its own contributions to the problem, then no amount of consulting will fix the problem.

About the author

Eileen Strider's picture Eileen Strider

Eileen Strider facilitates project reviews, project retrospectives, and IT organization assessments based on her experience as a developer, software project manager, IT manager, and Chief Information Officer. She occasionally fills in as a temporary CIO. With her partner, Wayne Strider, she leads the annual Strider & Cline Leaders' Forum. See www.striderandcline.com/ or send email to eileenstrider@worldnet.att.net.
 

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!