Voices on Project Management

By

Peter Tarhanidis, Ph.D.

Project management methodologies have evolved significantly over the years, with waterfall and agile emerging as two of the most prominent approaches. Each has its strengths and weaknesses, making them suitable for different types of projects and organizational needs.

• Waterfall is a linear, sequential approach to project management. It is characterized by distinct phases; each phase must be completed before the next begins with limited ability to revisit or revise previous stages. Waterfall is effective for projects with well-defined requirements and a clear path to completion, such as construction or manufacturing projects.
• Agile is an iterative, incremental approach designed to accommodate change and foster continuous improvement. It emphasizes collaboration, customer feedback, and small, manageable units of work called sprints. Agile is well-suited for projects where requirements are expected to evolve, such as software development or other innovative fields.

Surveys indicate:

• 51% of companies implement waterfall and 71% of companies utilize agile.
• PMI’s 2020 Pulse of the Profession® report Ahead of the Curve: Forging a Future-Focused Culture indicated that 11.4% of investment is wasted due to poor project performance.
• The Standish Group’s CHAOS report showed only a 31% project success rate.
• Harvard Business Review estimated a $3 trillion annual global financial loss, wasted resources, missed opportunities, and negative societal impacts due to project failures.

Given these statistics, you may ask which method is best for a given project. Many organizations find value in blending these methodologies to create a hybrid approach, leveraging the structured planning of waterfall and the flexibility of agile. This hybrid model can offer a balanced framework that enhances efficiency, adaptability, and customer satisfaction.

While waterfall's structured approach provides clear milestones and accountability, its rigidity can be a drawback in dynamic environments. Agile's flexibility and responsiveness to change make it ideal for such settings, but it can struggle with scope creep and lacks the clear, long-term planning of waterfall.

The hybrid approach seeks to combine the best of both worlds, providing a structured framework that remains flexible and adaptable. By relying on a competency and development framework, management can highlight the key components of hybrid—consistently applying best practices to mature success and project outcomes.

Key components of hybrid project management include:

1. Phase-based structure with iterative execution: Projects are divided into phases similar to waterfall, but within each phase, agile sprints are used to execute tasks. This allows for detailed planning and requirements gathering upfront, followed by iterative development and testing.
2. Defined milestones with flexible deliverables: Hybrid project management sets clear milestones to track progress and ensure alignment with overall goals. However, the deliverables within each milestone can be adjusted based on iterative feedback and changing requirements.
3. Customer collaboration and feedback loops: Regular interactions with customers and stakeholders are maintained to gather feedback and make necessary adjustments. This aligns with agile’s emphasis on customer collaboration and helps ensure the project remains on track to meet user needs.
4. Comprehensive documentation with adaptive planning: Initial project documentation and planning follow a waterfall approach to establish a clear roadmap. Throughout the project, adaptive planning is used to refine and update this documentation based on iterative insights and changes in scope.

Steps for implementing a hybrid model:

1. Assess project requirements and environment: Evaluate the project's nature and complexity, and the environment in which it will be executed. Projects with stable requirements and clear end goals may lean more toward waterfall, while those with uncertain or evolving requirements may benefit more from agile practices.
2. Define phases and iterations: Establish major project phases with clear objectives and timelines. Within these phases, implement agile sprints or iterations to manage work increments, allowing for continuous assessment and adjustment.
3. Foster collaboration and communication: Create a culture of open communication and collaboration among team members, stakeholders, and customers. Regular meetings, such as daily stand-ups and sprint reviews, can help maintain alignment and address issues promptly.
4. Balance documentation and flexibility: Ensure that initial project plans and requirements are well-documented but remain open to revising them as the project progresses. Use documentation as a living document that evolves with the project.
5. Monitor progress and adapt: Use waterfall’s milestone tracking to monitor overall progress, and agile’s sprint reviews to assess interim deliverables. Be prepared to adapt plans and strategies based on feedback and performance metrics.

The leadership required in hybrid project management has a blend of strategic oversight and adaptive facilitation to balance the structured rigor of waterfall with the dynamic responsiveness of agile. Effective leaders in this context must embody several key traits and skills to ensure project success:

1. Visionary thinking: Leaders must articulate to the team a clear vision of the project’s goals. They need to establish long-term objectives while accommodating short-term adjustments, maintaining alignment with overall project aims.
2. Flexibility and adaptability: Leaders must pivot between structured planning and iterative development. They must be comfortable with change and capable of guiding their team through unexpected challenges and shifts in project scope.
3. Strong communication skills: Open, transparent communication is essential. Leaders must facilitate continuous dialogue among team members, stakeholders and customers. Regular updates and feedback loops are crucial for maintaining alignment and addressing issues.
4. Collaborative mindset: Encouraging a culture of collaboration is vital. Leaders should promote teamwork, ensuring that all voices are heard and valued. This involves fostering an environment where team members feel empowered to contribute ideas and solutions.
5. Strategic decision-making: Effective hybrid project leaders must be adept at making informed decisions quickly, balancing the need for detailed planning with the flexibility to adapt plans based on real-time insights and feedback.
6. Risk management: Proactively identifying and mitigating risks through both structured risk assessment and iterative reviews is crucial. Leaders must be vigilant and responsive, adjusting strategies as necessary to keep the project on track.

By embodying these qualities, leaders can successfully navigate the complexities of hybrid project management, ensuring that projects are both well-organized and adaptable to change. The overall benefits of hybrid project management provide for:

1. Enhanced flexibility: Combining structured phases with iterative sprints allows for greater adaptability to changes in project scope, requirements and market conditions.
2. Improved stakeholder engagement: Regular feedback loops and collaborative practices ensure stakeholders are consistently involved and satisfied with the project’s direction.
3. Risk mitigation: The hybrid approach can identify and address risks earlier in the process through iterative reviews, reducing the likelihood of major issues arising late in the project.
4. Balanced planning and execution: It provides a comprehensive planning framework while maintaining the flexibility needed for creative problem-solving and innovation.

In conclusion, hybrid project management offers a robust framework that leverages the strengths of both waterfall and agile methodologies. By blending structured planning with iterative execution, organizations can achieve greater efficiency, adaptability, and customer satisfaction, making it a versatile approach for a wide range of projects.

Please share in the comments how your organization defined hybrid project approaches and any case studies that you would like to share.

References

1. PMI Pulse of the Profession®: Ahead of the Curve: Forging a Future-Focused Culture
2. The Standish Group: Benchmarks and Assessments
3. It’s Time to End the Battle Between Waterfall and Agile
4. Agile vs Waterfall: Which Approach Should You Choose for Your Project
5. Waterfall vs Agile Methodology: What’s Better for Your Project?

By Jen Skrabak, PMP, PfMP

In the first part of this series, I introduced PMI’s new governance practice guide and reviewed basic differences between organizational (corporate) governance, portfolio management governance and portfolio governance.

With that foundation, I’ll now discuss the four basic governance functions, which together can ensure alignment to strategy. Since portfolios include programs and projects by definition, those are not called out separately.

• Oversight. Provide guidance, direction and leadership for portfolios
• Control. How to monitor, measure and report on portfolio status
• Integration. Provide strategic alignment and integration for the portfolio
• Decision-making. Provide decision-making structure, thresholds and membership, including delegation of authority for portfolios

In addition, there are four basic governance domains:

• Alignment. Creating an integrated governance framework, and defining the governance relationships and hierarchy between portfolio governing bodies and other governing bodies (enterprise, functional, program and project-specific)
• Risk. Identifying and resolving threats and opportunities proactively to ensure the balance of risk and reward for the portfolio
• Communications. Disseminating information, engaging stakeholders and ensuring organizational change is carried out effectively
• Performance. Measuring and evaluating KPIs to ensure portfolio value

For some portfolio managers, there may be confusion over governance activities versus portfolio management activities. Portfolio managers may play a governance role on certain programs and projects and provide oversight and decision-making. However, day-to-day portfolio management is distinct from governance, as shown in the diagram below:

Look for part three of this series—which will be focused on key success factors—in the coming weeks! And comment below to share your reactions.