Policy-as-Code in Planning
Quick Reference
What & Why
Definition
>= 80% of planning templates integrate OPA/Kyverno policies validating security, compliance, cost constraints.
Business Value
Reduces compliance audit preparation time by 75% and provides real-time policy violation detection with 99% accuracy through automated evidence collection Achieving >= 80% work items validated by policy is a key milestone toward this goal.
Context
This capability is part of the Acceleration milestone's focus on scale automation, embed compliance, improve speed & reliability. Essential for teams targeting LT, DF improvements.
Success Criteria
Target
>= 80% work items validated by policy
Measurement
Policy enforcement rate from planning tool integration
Evidence
- OPA policy files
- Policy validation logs
- Exception requests
In Practice
Real-World Implementation
Teams define policies: max pod CPU, required security labels, cost threshold. Planning tool validates stories against policies before sprint commit.
Concrete Example
Implementation Guide
Prerequisites
Implementation Steps
Follow the measurement approach: Policy enforcement rate from planning tool integration
For detailed step-by-step guidance, refer to the Continuous Planning & Compliance Integration Implementation Kit.
Resources
Implementation Kit
Continuous Planning & Compliance Integration KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Prerequisites
Implement these first
Complementary
Often adopted together, from the Continuous Planning & Compliance Integration 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 Acceleration milestone. Individual timelines vary based on team size and existing practices.