PMI Sites
Register
Disciplined Agile
Search

    Hybrid Approaches

    A spectrum where predictive anchors one end and agile on the other. The range between these poles represents the hybrid approach, a blend of elements from both.

    Currently, predictive and agile ways of working are well understood, at least at a high level. The Process Groups Practice Guide sets the industry benchmark for predictive approaches, while the Disciplined Agile knowledge base and various agile frameworks define agile approaches.

    Envision a spectrum where predictive anchors one end and agile on the other. The range between these poles represents a blend of elements from both, commonly termed a "hybrid." Unlike predictive and agile ways of working, "hybrid" lacks a universally accepted definition or a specific framework delineating its practices.

    This is where the Disciplined Agile (DA) concept of a working spectrum becomes crucial; as depicted in Figure 1, DA uses a nuanced approach to this hybrid model, identifying three distinct levels within the spectrum to provide clarity and context. These levels are not exhaustive but serve as benchmarks to locate a team's way of working within the predictive-agile spectrum.

    These levels aren't rigid classifications but markers to help identify the dominant characteristics of a team's methodology at a certain point in the spectrum. Beyond these three, numerous nuances exist, allowing teams to pinpoint their unique blend of predictive and agile practices. Utilize this spectrum to map out where your team's methodology converges within the predictive-agile continuum.

    Disciplined Agile Ways of Working spectrum

    Hybrid is Increasingly Being Utilized

    Hybrid approaches are increasingly being utilized. Transitioning from a predictive approach to an agile one can be challenging. Based on current Project Management Institute (PMI) research, hybrid continues to gain as the fit-for-purpose approach as organizations cope with different challenges and needs in their project work. Adopting the right approach for work should be considered table stakes, serving as a starting point from which to seek additional strategies to increase desired outcomes.

    Hybrid Level 1

    DA Ways of Working Spectrum Hybrid Level 1: "At this point on the spectrum, the predicative approach is the significant contributor to the way of working. The team is beginning to incorporate practices and techniques from agile."

    Benefits

    • The team is gaining awareness of agile strategies, practices, and techniques and their potential benefits.
    • Experimentation with options to reduce pain points such as long duration and large attendance meetings.
    • Desire to move farther to the right of the spectrum, gaining buy-in to continue progressing.

    Considerations

    • Agile approach adoption is not an organizational goal. Teams are beginning to experiment with practices they can use without introducing significant risk or governance issues.
    • Minimal support is available for agile training, coaching, or mentoring.

    Hybrid Level 2

    DA Ways of Working spectrum Hybrid Level 2: "At this point on the spectrum, the predicative approach is a major contributor to the way of working. The team is beginning to use an agile approach at points in the project lifecycle. For example, the development team members use timeboxes (iterations/sprints) to implement the requirements."

    Benefits

    • A portion of the project utilizes more of an agile approach than a predictive approach.
    • Exposure to how agile can solve challenges and improve predictability and outcomes.

    Considerations

    • Team members working in a specific phase, such as development, have experience with Agile and a desire to use it.
    • A substantial delay in the feedback cycle is still present, with requirements gathered in detail upfront and user acceptance testing at the end of the lifecycle.

    Hybrid Level 3

    DA Ways of Working spectrum Hybrid level 3: "At this point on the spectrum, an agile approach is the major contributor to the way of working. The team is using a timeboxed approach; however, they are implementing requirements (stories) across multiple iterations."

    Benefits

    • Vastly improved feedback cycle time over a predictive approach.
    • Cross-functional team vs. groups of specialists dedicated to a specific phase.

    Considerations

    • Although there are considerable benefits over a predictive approach, there are still many missed opportunities, such as feedback cycles, delays, higher effort to accommodate changes, etc.
    • Shifting further to the right often requires additional support from training and coaching.