Lightweight Threat Modeling
Quick Reference
What & Why
Definition
STRIDE checklist applied to >= 60% of features touching sensitive data or external integrations.
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 >= 60% sensitive features have threat model 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
>= 60% sensitive features have threat model
Measurement
Security review tracking system query
Evidence
- STRIDE checklist template
- Completed threat models
- Mitigation backlog items
In Practice
Real-World Implementation
Teams complete 15-min STRIDE worksheet for features handling PII, payments, or external APIs before coding starts.
Concrete Example
Implementation Guide
Implementation Steps
Follow the measurement approach: Security review tracking system query
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
Enables
What this unlocks
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.