Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.
Understanding Bimodal Portfolio Management
Here, Gartner notes that “marrying a more predictable evolution of products and technologies (Mode 1) with the new and innovative (Mode 2) is the essence of an enterprise bimodal capability.”
Put differently, the enterprise does not need to choose solely between an agile approach or a traditional waterfall methodology. Both can be used interchangeably to achieve agility and stability, allowing businesses to successfully expand agile practices into other operations.
Bimodal Portfolio management principles
BimodalPfM combines principles from several existing approaches including DA, SAFe, and SfPfM.
Here are some of the more pertinent principles:
- Senior management commitment. Upper management must champion the value of BimodalPfM by backing up their words with actions and not delegating their obligations to others.
- Alignment of governance, customer, and strategy. Active involvement of key stakeholders is encouraged, but portfolio governance must remain aligned with the wider organizational structure.
- Simplicity. The larger or more complex the project, the higher the chance that it will fail. Businesses should use the iterative and incremental nature of agile principles to their advantage.
- Flexibility. To continuously re-evaluate opportunities, decision-makers should implement a rolling wave over an annual plan. Too many organizations create an annual plan in the knowledge that major changes are likely to render it obsolete. Agility in this area reduces costs associated with delays, losses, and plan revisions.
Five key components of Bimodal Portfolio Management
While BimodalPfM is an effective strategy, many advocates concede that the bimodal approach can create obstacles to delivery speed.
However, these obstacles can be overcome by considering five key elements:
- Dependency management. If a team with the right to prioritize its own work is dependent on others for an outcome, a dependency management strategy should be created to reduce delays.
- Work and delivery teams. How do teams engage with other teams across delivery methods to achieve desired outcomes? Is the process efficient? Saving time here means that teams clearly and concisely articulate the terms of engagement.
- Culture. In the context of BimodalPfM, culture means that staff have respect for alternative delivery models – regardless of whether they are agile or traditional. There should be more of a focus on practicality and less debate on which method is superior.
- Funding. Before beginning, it’s important to clarify funding agreements for work that is being shared by both models. Recognize that Project Funding and Capacity Funding are different models and as a result, require different decisions.
- Decision making. Agile methodologies favor de-centralized decision making which invariably challenges the centralized governance structure common in many organizations. To increase decision-making speed, it is once again important to clarify the most effective model beforehand. Furthermore, businesses should always remember that it is in their best interests to make fast and accurate decisions.
- Bimodal Portfolio Management allows a business to de-risk agile change management initiatives by utilizing a mix of agile and traditional methodologies.
- Bimodal Portfolio Management borrows concepts from many other agile frameworks. Primarily, BimodalPfM works best when there is complete buy-in from upper management and alignment of governance, customer, and strategy.
- During implementation, Bimodal Portfolio Management can create delivery speed issues. Some of these issues can be overcome by determining whether agile or traditional approaches are best suited to a particular context.
Connected Agile Frameworks
Main Free Guides: