PMO to VMO Notes

PMO Course – PMO to VMO: Towards Value Delivery

Funding Model - VMO

• Challenges of Traditional Budgeting and Funding Methods:
  • Rigid annual planning.
  • Budget overruns and schedule delays.
  • Limits organizational agility and flexibility.
• Case of Nationwide Insurance:
  • Flexible, outcome-oriented funding model.
  • Transition to a product model using agile practices.
  • Improved value delivery and predictability.
• Importance of Adaptive Funding and Governance Models:
  • Prioritize adaptability and business outcomes.
  • Enable quick responses to changes.
  • Maintain strong financial governance.

Flexible Funding Model

• Importance of Flexible Funding for Business Agility:
  • Key predictor of achieving business agility.
  • Necessary for large, established companies.
• Criticism of the Traditional Project Management Model:
  • Incorrect assumption about predicting feature usefulness.
  • Inaccurate belief in knowing the economic value beforehand.
  • Unrealistic expectations regarding accurate estimates.
• Agile-Friendly Funding Principles:
  • Funding value streams, not one-time projects.
  • Using lean business cases and frequent delivery checkpoints.
  • Prioritizing business results over detailed upfront plans.
  • Recognizing the importance of timing in value delivery.

Traditional vs. Agile-Friendly Funding

Value Stream Financing vs Transactional Projects

• Fixed Budget Allocation to Stable Long-Term Business Areas
• Reduction of complexity and overhead in project management.
• Example of Global Budget:
  • 25 million for product development.
  • 5 million for support functions such as HR and accounting.
• Focus on Business Outcomes:
  • Budgets based on expected results, not on specific features.
  • Deliverables aligned with market needs.
• Product Management Responsibility:
  • Decide how to spend the budget to achieve desired outcomes.
  • Business cost-benefit analysis.
• Monthly Reporting Expectations:
  • Transparency on delivered functionality and achievement of business goals.
  • Plans for future releases and features.

Dynamic Approach to Business Outcomes

• Prioritization of Measurable Outcomes Over Predefined Scope Compliance
• Collaboration between the Value Management Office (VMO), senior leadership, and product management.
• Establishment of Quarterly Strategic Objectives
  • Aligned with the organization's global strategy.
  • Use of scenario planning and OKRs to improve processes and enhance customer satisfaction.
• Selection and Prioritization of MMPs (Minimum Marketable Products)
  • Identification of key MMPs to achieve strategic objectives.
• Monitoring Implementation and Business Results
  • Evaluation of the impact of decisions on expected outcomes.
• Outcome- and Feature-Oriented Funding
  • Strategic selection of MMPs based on detailed analysis.
• Contrast with Annual Planning Cycles
  • Greater flexibility and responsiveness to business and market changes.
  • More frequent strategy execution and results-oriented planning.

Features Economy

• Need to Identify Economically Viable Features for Product Development
• Differentiate between high-value, low-cost features and low-value, high-cost ones.
• Function-Level Monetization
  • Critical evaluation of the economic viability of each feature.
  • Aim: Avoid non-profitable functionalities.
• Challenges of the Traditional Approach
  • Tendency to fulfill every stakeholder request without considering real economic value.
• Experimentation
  • Rapid testing of hypotheses to assess economic viability.
• Use of WSJF for Prioritization
  • Weighted Shortest Job First as a tool to assess the economic value of features.
• Challenge of Managing Real Costs
  • Gap between agile project management and traditional financial accountability.
  • How to justify spending and manage real-world costs in monetary terms.

Focus on economic value

• Critique of the Traditional Project Management Approach:
  • Excessive focus on calculating costs with high precision
  • Neglect in evaluating economic value or return on investment (ROI)
• Value Projections vs. Reality:
  • Projections are often vague or overly optimistic, ignoring actual customer behavior
• Consequences of Cost-Value Imbalance:
  • Confusing investment decisions
  • Uncertain ROI
• Factors Influencing Spending Decisions:
  • Demands from key stakeholders
  • Pressure to align with the financial planning cycle
• Focus on Value:
  • Greater emphasis on the economic value of projects (“R” in ROI)
  • Less exclusive focus on cost (“I” in ROI)

Estimation Methods

• Contrast Between Estimation Methods:
  • Traditional (bottom-up) vs. Flexible (top-down).
  • Traditional methods focus on detailed requirements, losing flexibility.
  • The flexible model avoids early elaboration of detailed requirements.
• Flexible Funding Model:
  • Budgeting based on desirable financial outcomes.
• Business Case Development:
  • Based on specific business objectives.
  • Budget allocations justified by the expected return on investment.
• Top-Down Estimation:
  • Supports flexible, adaptive planning.
  • Provides fast, high-level estimates.
• Development of Fixed-Cost Models for Agile Teams:
  • Proposes top-down estimates for speed and simplicity.
  • Allows for greater accuracy through conservative application.

Fixed cost models for Agile Teams

• Efficiency & Simplicity: Agile teams are long-term, multifunctional, and operate with lightweight processes compared to traditional methods.
• Sprint-Based Estimation: Uses sprint cycles to estimate time and cost simply and quickly.
• Early Delivery Benefits: Early functionality helps validate estimates and ensures alignment with business outcomes.
• Economic Value Focus: Encourages selecting high-impact, cost-effective solutions over large upfront investments.
• Top-Down Estimation Preference: Faster and sufficiently accurate without needing detailed breakdowns—minimizes complexity and error risk.

Change Management and Governance

• Scope Change Management Favoring Flexibility
• Incorporation of only requirements that contribute to desired business outcomes.
• Flexible Scope Definition: Excludes requirements not aligned with business goals
  Arr reduces costs.
• Evolution and Change in Requirements: Based on customer behavior and project economics.
• Governance and Control Focused on Results: Scope changes do not negatively affect governance; the focus remains on achieving specific business outcomes.
• Change Management through Communication: Continuous communication ensures alignment and transparency.
• Progress Measurement without Fixed Scope: Business results are key progress indicators; continuous evaluation toward project goals.

Organizational change management- VMO

Transition from PMO to VMO

• Leadership Alignment is Crucial: Change should start with aligning top leaders.
• Resistance from Strong Beliefs: Leaders with entrenched views may resist, causing internal conflict.
• Mixed Signals Undermine Change: Inconsistent messages from leadership allow old habits to persist.
• Effective Change Strategies:
  • Promote self-awareness within the organization.
  • Use external support to manage and accelerate change.

Focus on soft aspects

• Soft factors are critical: Agile success depends on leaders who drive and understand organizational change.
• Adaptability is key: Organizations must be able to shift behaviors to adapt to evolving environments.
• Behavioral change should be structured: A repeatable method for behavior change supports continuous reinvention.
• Leadership responsibility: Leaders must go beyond technical fixes, integrating behavioral and strategic change for lasting impact.

Strategy for change

• Integral Strategy for Change:
  • Need for a long-term strategy to adopt new ways of working.
  • Significant changes require consistency and years of sustained effort.
• Sustained Commitment is Essential:
  • Large-scale Agile adoption requires continuous dedication.
  • Short-term attempts don’t lead to lasting change.
• Risk of Abandoning Agility:
  • Companies may lose interest after one or two years without clear results.
  • Declaring "agility doesn’t work here" without sustained effort.
• Long-Term Commitment is Required:
  • Change can take years.

Why the change?

• Clear purpose and vision
• Developing Purpose and Vision for Change:
  • Strongly argue the need for change.
  • Answer “why” and “why now” with concrete data.
• Selling the Change Internally:
  • Reasons for change must be real and genuine.
  • Lack of a genuine need reduces the likelihood of success.
• Importance of Personal Understanding:
  • People support change if they understand its necessity and personal benefit.
  • Continuously communicate the organizational need to motivate and create urgency.

Metrics aligned with agility

• Metrics Must Support Transformation at All Levels: Individual, Program, and Organizational
• At the Individual Level: Adjust performance metrics to reflect new agile processes.
  • Ex: “How effectively the individual contributes to helping the team meet the sprint goal, by collaborating, removing blockers, and supporting delivery of working software.”
• Examples of Program-Level Metrics:
  • Reduce days and cost per release by half. (negative impact indicator)
  • Do not exceed three months without delivering user value. (positive impact indicator)
  • Measure delivery frequency and collection of market feedback.
• Change in Process Metrics:
  • Track version evolution, sprints, and backlog health.
  • Promote agile behaviors through specific metrics.
• At the Organizational Level: Senior leadership drives macro-level adoption.

Establish the VMO

Cross-Functional and Cross-Hierarchy Organization

• Unified Progress: The entire organization should advance together.
• Bridging Roles: Key individuals are needed to link teams, Value
  Streams, departments, and hierarchical levels, ensuring alignment and coordination.
• Strategic Coordination: The VMO leads at the highest level, managing value delivery and organizational change across multiple value streams.

End-to-End Representative Roles

• Key roles include Director, Program Manager, and Executive Champion.
• VMO Directors and Program Managers coordinate short-term iterations and long-term strategies; they may come from business or IT.
• Liaison representatives connect different organizational levels:
  • Executives → senior leadership
  • Value Stream Managers → related programs
  • Agile team members → their own teams
  • Team representatives should include the Scrum Master, Product Owner, or other relevant members.

VMO Meetings and cadence

• Agile practices and artifacts are used: long-term backlog, short-term backlog, sprint planning, and review meetings.
• Daily or regular stand-up meetings and consistent follow-up.
• Timeboxing is applied in main meetings.
• Retrospectives are held to assess what is working and what is not.

VMO Meetings – The Big Planning Meeting

• The VMO quarterly planning meeting aligns all teams by reviewing results and planning the next quarter.
• It requires strong preparation and aims to:
  • Define OKRs and MMPs for the upcoming quarter
  • Identify dependencies and risks
  • Establish a communication plan
  • Capture executive-level action items in the VMO backlog

VMO kickoff

• A kickoff meeting is held where the following is addressed:
  • Present the concept and details of the Executive Action Team and Agile VMO
  • Briefly discuss the commitments requested from all involved
  • Present the organization’s OKRs and budgets
  • Develop the norms and values of the VMO team
  • Review the role of the Value Stream Manager and facilitate a brief brainstorming session about the responsibilities of the role
  • Begin to develop and prioritize pending work, and be prepared to share short-term plans in the next VMO working session
  • Capture action items for the VMO, especially for the next set of meetings

Managing Agile life cycle

• The Value Management Office (VMO) plays a dual role:
  • Strategically, it drives organizational change.
  • Operationally, it manages a dynamic work portfolio in coordination with Value Stream Managers.
• The agile lifecycle for this work of value flow is organized into two phases: Preparation and Completion.

Managing Agile life cycle - Preparation

• Agile preparation requires strong alignment between business objectives and delivery teams (e.g., SAFe Agile Release Trains).
• Leadership must focus on prioritizing Epics that support strategic goals, ensuring budget and resources align accordingly.
• A solid architecture runway is needed to enable scalable development and capability delivery.
• A visual management system is essential for tracking and guiding workflow effectively.

Work Flow Element Deliverables

Managing Agile life cycle - Finalize

• Once organizational objectives are defined, the focus shifts to continuous execution through:
  • Agile Release Trains (ARTs): Teams grouped and aligned with customer needs and business outcomes via value streams.
  • Program Increments (PI): Delivery is maintained on a regular cadence, ensuring synchronization of efforts across teams.
• Goal: Enable smooth, predictable flow of work tied directly to business value.

Work Flow Element Deliverables