Cultivating Agile Requirements
Mark Wavle, CBAP, PSM
The Agile Manifesto
The Mission Statement
We Value:
Individuals and Interactions
Working Software
Customer Collaboration
Responding to Change
over
Process and Tools
Comprehensive Documentation
Contract Negotiation
Following a Plan
That is, while there is value in the items on the right, we value the items on the left more.
Scrum Framework
Product Backlog
• List of all remaining desired features for the product
• Ordered / stack ranked (1 to n…)
• Each feature expressed as a Product Backlog Item
• Visible to all stakeholders
• Product Backlog changes constantly throughout
development of the product
Definition of Ready
A ready item is:
• Clear
• Feasible
• Testable
Questions for Backlog Items
•
•
•
•
•
•
•
•
What is the idea?
How does the user benefit?
How important is it?
What high-level items can we do in the next 6-12 months?
How big is it?
What specific items can we do in the next 1-3 Sprints?
How are we going to implement it?
How will we know it is done?
Discuss with
stakeholder
Analyze and
decompose
Identify Acceptance
Criteria
Identify test data
Document idea
Estimate (t-shirt sizes)
Estimate (story
points)
Complete UX/UI
design
Identify user benefit
Identify
dependencies
Work dependencies
Legal, compliance,
security reviews
Prioritize
Identify place in 6-12
month plan
Identify place in next
1-3 Sprints
Plan for team delivery
Free-form
User Story
Acceptance Criteria
Supplementary
artifacts, wireframes
Techniques to Mature Backlog Items
Backlog Grooming Sessions
•
Ensures whole team understands backlog items as they are matured
Estimating/Sizing
•
Drives whole-team understanding of each item as it is sized
Splitting Backlog Items
•
Splits items so they deliver value and fit within one Sprint
Modeling Visually
•
Encourages conversation and collaboration while ensuring the whole
team understands the item
Thank You
Mark Wavle
Email: mwavle@cardinalsolutions.com
Twitter: @wavle