Planning, Estimating and Managing Government Software Projects

Academic papers in computer science and systems engineering as well as newspaper exposés frequently cite horrific examples of cost overruns on software projects. When I see a headline like, “GAO Highlights DoD Cost Overruns” I shrug and say to myself, “here we go again.” What got me going down this thought path today was a recent headline in our local, “Austin Business Journal” titled State lacks sufficient IT planning.

What followed in the article – sorry the full article requires a subscription – chronicles 48 technology projects undertaken by the State of Texas, of which 32 were late and/or over budget. You can read the report, “2010 Quality Assurance Team Annual Report” in its entirety, if you are so inclined. The article suggests that the blame for recurrent failures falls on the “state employees tasked with planning and budgeting new technology projects.” The implication being that if the state employees managing the projects just knew how to estimate software development cost and schedule, then the projects would successfully complete on time and within budget.

In my opinion, it is not that simple.

Software Cost Estimating Theory
Back in December 2010, I talked about Estimating Project Costs. In theory, a project manager uses customer requirements, resource availability and required milestones to construct a realistic project schedule and budget. In complex projects, components may be estimated separately and then the estimates are combined or rolled-up with integration estimates to produce cost and schedule for the total project. Sophisticated cost estimating tools help project managers construct a cost and schedule using parametric models and lessons learned from previous, similar projects.

Software Cost Estimating Reality
First, let me say that no one wants to know how much it will cost to get a software solution to meet their needs because the number will be too high. Senior management wants a software cost and schedule that allows them to win a competition based on lowest bidder. Government agencies want a solution that fits within the budget that was already proposed and approved before the RFP was announced.

Getting from point A to point B often involves a complex dance using multiple contractors, combinations of off-the-shelf and developed software and workers located anywhere around the world working for small or medium sized companies or as individual contractors. The set of vendors working together comprise the “project team” each of whom was pressured to commit to a cost and schedule that meets the target established by the customer.

 I live in a large state with a state government budget that rivals many countries. To meet budget shortfalls, most states – including mine — have gone to a state run outsourcing model that encourages independent contractors and staffing firms to deliver “lowest cost.” What is happening is that they are not getting the right skill set and there is no synergy or “team” concept in these IT programs. Instead of utilizing two or three firms, who specialize in a particular area, they are putting 10 to 20 independent contractors together and saying – here is the schedule, make it happen.

This situation is a project manager’s nightmare. I hate to say I see the same trend in corporations…. They have stopped using small, expert firms and have gone to a staffing model that brings in independent contractors to work individual positions and tasks. I am only glad I am not in charge of one of those projects! 

I would love to say that I have THE SOLUTION. However, I don’t. I applaud government agencies and companies that accept “Best Value” rather than lowest bid – that is a start. I would like to see professional support for government agencies in creating realistic RFPs for software procurements. In addition, I think that a procurement model that involves selecting a trusted contract manager or contractor and then incrementally creating requirements and development cycles, rather than all or nothing development, has merit. Then I would like to see teams made up of the right professionals – especially Project Managers. We have to start acknowledging that not all people are good at everything and a good team is not a collection of random consultants.

Your thoughts, experiences and suggestions are encouraged.

6 Responses to “Planning, Estimating and Managing Government Software Projects”

  1. raidlogs Says:

    Agree entirely. I would add though, for Government projects in particular, that a lack of accountability is one of the major reasons the projects fail to meet time, cost or quality success criteria.

  2. msplesher Says:

    What are the major reasons the projects fail to meet time, cost or quality success criteria?

    1. People – Talent (skill), attitude, Forced solution with no options / alternatives
    2. Underlying method / tools – Software – Programming language / applications prorgam – Stable, fully debugged, embedded OOP processes where program/applicagton to determine outcome (example – Spell checker – Automatic conversion of txo to to, too, two at spell checker choice and not confirmed by user.
    3. Outcome based on not well defined or yet completed options – Example – based on availability of software currently in beta stage.
    4.

  3. Bruce McGraw Says:

    I agree with your 3 reasons – I would order them a little differently:
    1. People – until we use robots this will always be #1
    2. Scope/Outcome – This has got to be # 2 – especially on Gov projects.
    3. Methods/Tools – Too often the project has dictated the wrong process, tools or methods to accomplish the project.

    Good Points!!!

  4. Planning, Estimating and Managing Government Software Projects « Program Management Office Says:

    […] headline in our local, “Austin Business Journal” titled State lacks sufficient IT planning. [READ MORE] Articles    NEW Project Charter Posted […]

  5. Why do Government Projects continue to fail? « Fear No Project – A Project Management Blog Says:

    […] of problems I have seen is in project cost estimating.  I wrote another post on that last year (Planning and Estimating Government projects) where I talk about how both government and corporate management want a “low cost” […]

  6. PM Musings » Government IT projects are prone to failure for 6 very predictable reasons Says:

    […] of problems I have seen is in project cost estimating. I wrote another post on that last year (Planning and Estimating Government projects) where I talk about how both government and corporate management want a “low cost” […]


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

The Lazy Project Manager's Blog

The Home of Productive Laziness Thoughts

ProjectManagement.com

Thoughts, experience, tips and tricks on issues affecting managers and project management

A Girl's Guide to Project Management

Project Management musings for one and all

How to Manage a Camel - Project Management Blog

Project Management Recruitment, Careers and News from Arras People

LeadingAnswers: Leadership and Agile Project Management Blog

Thoughts, experience, tips and tricks on issues affecting managers and project management

Project Management Hut

Thoughts, experience, tips and tricks on issues affecting managers and project management

Herding Cats

Thoughts, experience, tips and tricks on issues affecting managers and project management

beyondcenter

Pushing the Edges Out ...

projectxpert

Just another WordPress.com site

%d bloggers like this: