User Story Template
The foundation of Agile work. Get it right, and your sprints flow smoothly.
Why This Month? Most BAs struggle with acceptance criteria that are too vague or too technical. This template shows you how to write them clearly so developers know EXACTLY what done looks like.
Filter by Type:
🚀 Agile & Sprint Templates
User Story
Easy
The building block of Agile. Tells who, what, and why.
When to use: Sprint planning, Agile projects, backlog refinement
💡 Pro Tip:
- Keep it small (1-5 story points)
- Acceptance criteria must be testable
- User type should be specific, not generic
Sprint Planning Checklist
Easy
Never forget what to cover in sprint planning meetings.
When to use: At the start of every sprint
💡 Pro Tip:
- Print this and use before every sprint planning
- Takes ~5 minutes to verify everything
- Prevents 80% of sprint problems
Sprint Retrospective Template
Medium
Structure your retros. Get actionable improvements.
When to use: End of every sprint (Friday afternoon)
💡 Pro Tip:
- Keep retros to 45 minutes max
- Focus on 1-2 action items, not 10
- Celebrate wins first, then discuss improvements
🎯 Planning & Discovery Templates
Requirements Document
Hard
Comprehensive specs for Waterfall or detailed planning.
When to use: Waterfall projects, fixed-price contracts, complex systems
💡 Pro Tip:
- Get stakeholder sign-off on requirements upfront
- Use requirement IDs (REQ-001) for traceability
- Include non-functional requirements (performance, security)
Business Requirements Doc (BRD)
Hard
What the business needs, not how to build it.
When to use: Project kickoff, stakeholder alignment, formal projects
💡 Pro Tip:
- Write for business stakeholders, not technical people
- Focus on business goals and outcomes
- Include success metrics and ROI
Discovery Interview Guide
Medium
Questions to ask during requirements gathering.
When to use: Project start, stakeholder interviews, requirements phase
💡 Pro Tip:
- Ask open-ended questions first, then specific
- Listen more than you talk (70/30 rule)
- Record interviews (with permission) to review later
📊 Documentation & Analysis Templates
Use Case Template
Medium
Detailed actor-system interactions with alternative paths.
When to use: Complex workflows, system design, test planning
💡 Pro Tip:
- Include main flow AND alternative/error flows
- Preconditions and postconditions matter
- Use for test case creation
Test Plan Template
Hard
Comprehensive testing strategy and approach.
When to use: Before UAT, large projects, mission-critical systems
💡 Pro Tip:
- Define success criteria upfront
- Map test cases back to requirements
- Include regression testing for existing features
Business Rules Matrix
Medium
Capture all business logic in one place.
When to use: Complex systems, pricing logic, compliance rules
💡 Pro Tip:
- Give each rule a unique ID (BR-001)
- Explain the "why" behind the rule
- Link to related requirements
👥 Stakeholder & Communication Templates
RACI Matrix Template
Easy
Clarify roles: Responsible, Accountable, Consulted, Informed.
When to use: Project kickoff, prevent role confusion, large teams
💡 Pro Tip:
- Only ONE person should be Accountable per task
- Share RACI with team to align expectations
- Update if roles change mid-project
Weekly Status Report
Easy
Keep stakeholders informed with consistent updates.
When to use: Weekly stakeholder updates, executive visibility
💡 Pro Tip:
- Keep it to 1 page (executive summary style)
- Lead with key milestones and issues
- Use red/yellow/green for status
Stakeholder Communication Plan
Hard
Structured approach to keep everyone informed.
When to use: Complex projects, many stakeholders, high visibility
💡 Pro Tip:
- Different stakeholders need different info
- Tailor frequency to stakeholder type
- Include format (email, meeting, dashboard)