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 Wanda Curlee

Project management is partly about establishing and documenting processes and procedures, and maintaining configuration control. Startup companies, on the other hand, often pride themselves on entrepreneurialism, a lack of required processes/procedures and flexibility.

But processes and procedures are not the antithesis of entrepreneurship and flexibility. In fact, project, program and portfolio management can help a startup manage growth.

When a startup’s leadership allows change to happen without any processes, strategy or structure, the organization will struggle. Project managers can help provide structure, while also demonstrating how to adapt to change.

For example, if the organization has 20 employees today but expects to add 180 in the next two years, how exactly will this growth occur? Will all new employees be hired in month 24? Do all resources need the same skills? Does training need to be done? This is where project managers can help.

Later in the organization’s growth, executives, with the help of project managers, can put together a roadmap to deal with issues like sales, IT and system needs, and travel policies. At this point, it may be time to turn to a program manager responsible for the overall strategic view of the program, rather than individual projects.

The program manager may work directly with leadership or report to a portfolio manager. The program may be to deliver organizational change, including IT, processes/procedures, staffing, etc. When I was a program manager, I focused on realizing benefits and the roadmap.

For example, when a small company becomes medium-sized, the number one issue might be staffing to meet sales needs. Let’s say the program manager’s roadmap showed that the second quarter of the program was when benefits would be realized from sales and increased staffing would occur.

If the program manager realizes that sales are occurring much faster than predicted, he or she would discuss alternatives with leadership. One option might be to slow sales; another might be to slow down the development of processes and procedures, and focus more resources on hiring the correct individuals to continue to drive sales.

Finally, the portfolio manager can drive strategic change in a startup growing into an established organization. The portfolio manager listens to leadership’s strategic goals. With a small company that is transitioning fast, the strategic goals should not change often, but can be fluid.

The portfolio manager assists the C-suite with governance and understanding how to select projects/programs to drive to the final result—checked growth without going bankrupt. She will also put governance in place to report to the investors, leadership and stakeholders. With a portfolio manager bridging strategy and execution, the fledgling organization can increase its chances of growing rapidly—and successfully.