Skip to main content

Progress Mapping

By systematically applying the 4x4 Method, teams can gain a comprehensive understanding of their software delivery process, identify key improvement areas, and make data-driven decisions to enhance their performance across all four DORA metrics.

Metrics​

  1. Deployment Frequency
  2. Lead Time for Changes
  3. Mean Time to Recover (MTTR)
  4. Change Failure Rate

These metrics, developed by the DevOps Research and Assessment (DORA) team, provide a balanced view of both velocity and quality in software delivery.

Four Key Maps​

  1. Outcome Map
  2. Value Stream Maps
  3. Dependency Map
  4. Capability Map

Outcome Map​

Purpose: To clarify and align the team on the desired outcome and contributing factors.

Key components:

  • Desired outcome
  • Contributing factors
  • Obstacles
  • Investigations
  • Measures (to be defined later)
  • Optional: Indicators, Impacts, Roles, Methods

Benefits:

  • Creates alignment and shared understanding
  • Helps identify potential challenges early
  • Sets the foundation for subsequent mapping exercises

Value Stream Maps​

Purpose: To visualize and measure the flow of work through the software delivery process.

Types:

  • Current State Map
  • Ideal State Map
  • Target State Map (3-6 months out)

Key components:

  • Activities in the workflow
  • Wait times between activities
  • Process time for each activity
  • Quality metrics (e.g., defect rates)
  • Value-added vs. non-value-added activities

Benefits:

  • Identifies bottlenecks and waste in the process
  • Provides data for prioritizing improvement efforts
  • Helps visualize the gap between current and ideal states

Dependency Map​

Purpose: To identify external factors affecting the team's ability to deliver value.

Key components:

  • Shared services
  • Meetings
  • SLAs
  • Approvals
  • Other external obligations

Benefits:

  • Highlights areas where the team lacks autonomy
  • Identifies opportunities to break or mitigate dependencies
  • Provides context for capability building needs

Capability Map​

Purpose: To assess the team's internal capabilities and identify areas for improvement.

Key components:

  • Critical capabilities required for success
  • Skill levels
  • Training needs
  • Resource availability
  • Comfort levels with different tasks

Benefits:

  • Identifies skill gaps and training needs
  • Helps prioritize capability building efforts
  • Supports decisions on internalizing dependencies

Implementation​

  1. Start with the Outcome Map to align on goals.
  2. Create Value Stream Maps to visualize current, ideal, and target states.
  3. Develop a Dependency Map to identify external constraints.
  4. Build a Capability Map to assess internal strengths and weaknesses.
  5. Use insights from all maps to create a prioritized improvement roadmap.
  6. Implement changes and measure progress using the DORA metrics.
  7. Repeat the process every 3-6 months to continually improve.

Best Practices​

  1. Involve representatives from all parts of the value stream in mapping exercises.
  2. Use collaborative tools for remote-friendly mapping sessions.
  3. Focus on relative measurements initially; precise data can come later.
  4. Prioritize improvements based on impact and effort.
  5. Communicate findings and plans visually to all stakeholders.
  6. Celebrate quick wins to build momentum.
  7. Be prepared to iterate and adjust as you learn.