Skip to main content Skip to Footer


May 18, 2017
Help! I have both Waterfall and Agile projects in my program—Part 2
By: Kevin Korterud

I’m frequently asked how program managers can synchronize projects using Waterfall approaches with those using Agile or other approaches.

As programs are launched to address larger and more complex business problems, harmonizing a program’s projects becomes an essential component of success.

In my previous post, I shared two tips for achieving harmony. Here are two more:

  1. Establish a Program PMO and an Agile Center of Excellence
    The program management office (PMO) is a critical success factor for any large program. It enables the program manager to spend time on higher-value activities, while the PMO creates the operational governance, reporting and overall management foundations required to run a program.

    As Agile and other delivery approaches mature, there is a great need for a Center of Excellence (CoE) model that fosters efficient and effective delivery approaches for the projects.

    Just as PMI created a consistent approach to project management, Agile and other delivery approaches are at a point in their maturity cycle where consistency is needed for them as well.

    An Agile CoE can facilitate this consistency while serving as a clearinghouse for improved Agile practices. This CoE can also address different variants in Waterfall, supplier and governmental delivery approaches, thus resulting in an overall harmonized approach for program and project delivery.

  2. Speak the same metrics reporting language
    George Bernard Shaw once said, “England and America are two countries separated by a common language.”

    I can relate. Being a program manager with projects utilizing multiple delivery approaches can feel like living in one country separated by multiple languages!

    Projects must both accurately describe progress and do it in a way consistent with other projects on the program, irrespective of delivery approach.

    When dealing with projects with multiple delivery approaches, a suitable translation needs to be in place for progress metrics. This is particularly necessary for stakeholders such as finance, human resources or other business functions where an easily understood definition of progress is critical.

    For example, Agile projects do a great job in counting projected versus actual requirements and their weighted points. Using the total and completed requirements, a percentage completion can be calculated that is consistent with a Waterfall delivery approach.

    Other Agile-specific metrics, such as effort per story point, can be used to supplement the core progress metrics.

    Even between Waterfall delivery approaches, there needs to be a consistent, defined approach for earned value structures, tracking actual cost and other progress essentials (Note that aside from progress metrics, the concepts of risks, issues, dependencies, milestones, cost forecasts and governance escalations all remain the same, no matter the project delivery approach.)

    Program managers are orchestrators of both project delivery and the attainment of business results. They need to be always thinking about eventual business outcomes, no matter which delivery approaches are in play.

    Remember: Nobody chooses an airline or a car model because the company used Agile or Waterfall on their projects—it’s all about the customer experience.

What methods have you seen employed in programs to handle multiple delivery approaches? Reach me on LinkedIn and let me know.

This blog post was first published in the PMI Voices forum.

Popular Tags



      COMMENTS (0)




      Your Data Privacy

      By providing your e-mail address, you agree to the terms
      outlined in our privacy statement associated with
      commenting on the site. Your e-mail address will not be
      used for promotional marketing purposes.

      Change the CAPTCHA codeSpeak the CAPTCHA code