The proverbial fox guarding the henhouse

Every project needs two project managers with distinct roles to avoid conflicts of interest

Projects fail for many reasons. Although the obvious reasons usually are cost overruns, the failure to properly plan for change and the inability to meet deadlines, the hidden reason is often the same. In too many projects, the same contractor manages the project and performs the project work. Whenever one party is responsible for execution and evaluation, you’ve got a prescription for trouble. The results are predictable when the fox is guarding the henhouse.

Effective project management demands the separation of project management from project implementation. Failing to separate those areas increases the likelihood that a consulting company’s internal pressures will conflict with — or take precedence over — the client’s needs. This can keep costs higher than required to meet a consulting company’s goals for profitability and resource utilization.

Estimates indicate that for every dollar military officials spend purchasing back-office software, they spend another $15 deploying that software. Effective project management significantly reduces this ratio. But when a project manager is part of the same team implementing the project, pressures from the consulting company tend to diminish the focus on reducing costs. Reducing costs typically hurts their employer’s bottom line. Even if the result is unintentional, a lack of third-party accountability costs the government billions of dollars each year.

The federal government has realized the liability inherent in this situation and is addressing the problem. More requests for proposals require consulting organizations to select the project management function or the implementation work, but not both. This separation must become a standard operating procedure if the government wants to become more effective in project deployment.

Separating project management and implementation necessitates at least two project managers: one who fulfills an oversight role and one who leads the implementation team that manages daily operations.

The client project manager is the eyes and ears of the government and is the client’s direct advocate. That person must oversee the work and identify potential problems and issues that can prevent the project from meeting its goals. That manager collects and monitors statistics, then compares them with the project’s criteria and goals. That person supports several overall functions, including scheduling, change control, risk management, budgeting, quality assurance and control, and oversight. The same person tracks projects and develops management reports detailing progress and problems.

The implementation project manager leads the implementation team, keeps statistics on progress and relays them to the client project manager. That person manages the risks of the implementation effort.

The benefits of this separation go beyond improving the client’s project oversight. They include improved communication because an independent group provides a forum for collaboration. Another advantage is a program office capable of supporting multiple projects concurrently. In sum, those benefits improve the efficiency and ability of teams to deliver projects on schedule and within budget.

Common sense dictates that the fox should never be left to guard the henhouse. In project management, common sense dictates that strong but separate management and implementation teams are best for the client.

Slovin is a vice president at EM&I. He has more than 25 years’ experience in application development, maintenance and re-engineering methodologies and processes.

FCW in Print

In the latest issue: Looking back on three decades of big stories in federal IT.


  • Shutterstock image: looking for code.

    How DOD embraced bug bounties -- and how your agency can, too

    Hack the Pentagon proved to Defense Department officials that outside hackers can be assets, not adversaries.

  • Shutterstock image: cyber defense.

    Why PPD-41 is evolutionary, not revolutionary

    Government cybersecurity officials say the presidential policy directive codifies cyber incident response protocols but doesn't radically change what's been in practice in recent years.

  • Anne Rung -- Commerce Department Photo

    Exit interview with Anne Rung

    The government's departing top acquisition official said she leaves behind a solid foundation on which to build more effective and efficient federal IT.

  • Charles Phalen

    Administration appoints first head of NBIB

    The National Background Investigations Bureau announced the appointment of its first director as the agency prepares to take over processing government background checks.

  • Sen. James Lankford (R-Okla.)

    Senator: Rigid hiring process pushes millennials from federal work

    Sen. James Lankford (R-Okla.) said agencies are missing out on younger workers because of the government's rigidity, particularly its protracted hiring process.

  • FCW @ 30 GPS

    FCW @ 30

    Since 1987, FCW has covered it all -- the major contracts, the disruptive technologies, the picayune scandals and the many, many people who make federal IT function. Here's a look back at six of the most significant stories.

Reader comments

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group