Non-Functional Requirements in Backlog
Quick Reference
What & Why
Definition
NFRs (performance, security, reliability) explicitly tracked in >= 70% of epics.
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 >= 70% epics have NFR acceptance criteria 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
>= 70% epics have NFR acceptance criteria
Measurement
Epic field analysis for performance/security/reliability criteria
Evidence
- Epic templates with NFR section
- Sample epics with NFRs
- Acceptance test results
In Practice
Real-World Implementation
Teams document NFRs in epic descriptions using template: response time < 200ms, 99.9% uptime, zero SQL injection vulnerabilities.
Concrete Example
Implementation Guide
Implementation Steps
Follow the measurement approach: Epic field analysis for performance/security/reliability criteria
For detailed step-by-step guidance, refer to the Backlog Quality & Planning Enablement Implementation Kit.
Resources
Implementation Kit
Backlog Quality & Planning Enablement KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Complementary
Often adopted together, from the Backlog Quality & Planning Enablement epic
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.