Skip to main content
    DevOps
    Way of Working
    1. Home
    2. Capabilities
    3. Plan Backlog Dod

    Definition of Done Standard

    Foundation
    Phase: plan
    LT
    DF

    Quick Reference

    Phase
    plan
    Epic
    Backlog Quality & Planning Enablement
    Milestone
    Foundation
    Target
    >= 90% stories have DoD
    Implementation Time
    Part of Backlog Quality & Planning Enablement epic: 3 weeks (24 hours per capability avg)

    What & Why

    Definition

    Team-wide DoD template applied to >= 90% of work items before sprint planning.

    Business Value

    Reduces sprint scope creep by 40% and improves story completion rate from 60% to 85% through clear acceptance criteria and retrospective-driven improvements Achieving >= 90% stories have DoD is a key milestone toward this goal.

    Context

    This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting LT, DF improvements.

    Success Criteria

    Target

    >= 90% stories have DoD

    Measurement

    Jira/Azure DevOps API query for DoD field population

    Evidence

    • DoD template doc
    • Sample stories with DoD
    • Sprint planning notes

    In Practice

    Real-World Implementation

    Teams use shared DoD checklist including unit tests, code review, and deployment criteria before marking work ready.

    Concrete Example

    Story 'Add payment API' has DoD: Unit tests >= 80%, PR approved, deployed to dev, API docs updated.

    Implementation Guide

    Implementation Steps

    Follow the measurement approach: Jira/Azure DevOps API query for DoD field population

    For detailed step-by-step guidance, refer to the Backlog Quality & Planning Enablement Implementation Kit.

    Resources

    Implementation Kit

    Backlog Quality & Planning Enablement Kit

    Templates

    Browse all templates

    Related Resources

    View learning paths

    Related Capabilities

    Enables

    What this unlocks

    Release Approval Workflow
    Policy-as-Code in Planning
    Automated Compliance Evidence Collection
    AI-Assisted Story Generation

    Complementary

    Often adopted together, from the Backlog Quality & Planning Enablement epic

    Non-Functional Requirements in Backlog
    Lightweight Threat Modeling
    Retrospective Action Item Tracking
    Basic Capacity Planning

    Troubleshooting & FAQs

    Common Issues

    Issue: Target metric not improving

    Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness

    Issue: Team resistance to adoption

    Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition

    Issue: Inconsistent implementation across teams

    Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards

    Frequently Asked Questions

    Can we implement this before completing prerequisites?

    While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.

    How long does implementation typically take?

    Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.

    DevOps
    Way of Working

    DevOps practices for the entire delivery lifecycle

    © 2019-2026 devopswow.com. Created by Burhan Öcüt

    PartnersAboutPrivacyTermsCookies