Mais conteúdo relacionado Semelhante a A Scrum Conversation (20) A Scrum Conversation3. PRODUCT BACKLOG REFINEMENT
3
Part 1 Business Needs
Who When
Team (Optional)
Product Owner
Scrum Master (Optional)
Potential SME’s
As Needed
Key Activities Key Data Points
Review Roadmap/Release Plan
Discovery and Refinements
Sessions with Product Owner
and relevant stakeholders and
SMEs
N/A
Outcomes Time Box
Clear Understanding of Business
Needs and Acceptance Criteria
Clear Priorities
Updated Product Roadmap &
Release Plan
As Needed
Product Backlog Refinement is often done in two
part:
• Part 1 is facing outward to the business
organization to understand and validate business
needs and priorities
• Part 2 is facing inward to the delivery team
clarifying those needs to support the
development of the solution
THE MAC IVER GROUP, LLC © 2005-2016
4. PRODUCT BACKLOG REFINEMENT
4
Product Backlog Refinement
Part 2 Team Understanding
Who When
Team
Product Owner
Scrum Master
Potential SME’s
Day 6 or 7 of the
Sprint
Key Activities Key Data Points
Review Roadmap/Release Plan
Refine User Stories
–Refine Acceptance Criteria
–Size Stories (Story Points)
Velocity Trends
Outcomes Time Box
Clear Understanding of User Stories,
& Acceptance Criteria
Stories for 2–3 Sprints That Meet
Team’s Definition of Ready (DoR)
Backlog is Sized and Prioritized
1–2 Hours
THE MAC IVER GROUP, LLC © 2005-2016
5. SPRINT PLANNING
Who When
Team
Product Owner
Scrum Master
SME’s (Optional)
First Day of the Iteration
(Mid-Week)
Key Activities Key Data Points
Capacity Planning
Product Owner Discusses the
Prioritized Stories with the Team
Candidate Stories
Task Breakdown
Commit!
Available Hours
Planned Hours
% Capacity Planned
Planned Story Points
Average Velocity
Outcomes Time Box
Team commitment to an achievable
goal
Detailed plan to achieve the goal
2–4 Hours
5THE MAC IVER GROUP, LLC © 2005-2016
6. DAILY SCRUM
Who When
Team
Product Owner (Optional)
Scrum Master
SME’s (Optional)
Daily (at the same time &
place)
Key Activities Key Data Points
Team Report Outs
Discuss Burndown
Recommit to Sprint Goal
Blocks or Impediments
Hours Remaining*
Story Points Accepted*
Outcomes Time Box
Recommitment to Sprint
Goal
Plan for the Day
15 Minutes
6THE MAC IVER GROUP, LLC © 2005-2016
7. SPRINT REVIEW & DEMONSTRATION
Who When
Team
Product Owner
Scrum Master
SME’s/Stakeholders
Management
Last Day of the Iteration
Key Activities Key Data Points
Sprint work assessed against the
Sprint Goal
Demo new Features
Get (Formal) Acceptance
Discuss Defects
Release Status/Upcoming Work
Story Points
Accepted/Not
% Accepted
Average Velocity
Sprint Burndown
Release Burndown or
Burnup
Outcomes Time Box
Team produced a coded, tested
and usable solutions (working
software)
Understanding of progress toward
Sprint Goals
Successful Demo
Understanding of progress toward
release goals
Improvement items identified
1–2 Hours
7THE MAC IVER GROUP, LLC © 2005-2016
8. SPRINT RETROSPECTIVE
Who When
Team
Product Owner (Optional)
Scrum Master
Immediately following the
Sprint Review
Key Activities Key Data Points
Review previous improvement
action items
Reflect on process, product,
team performance, team needs
Identify improvements action
items
Acceptance % & Trends
Velocity trends
Sprint Burndown/Release
Burnup
Team Capacity & Trends
Team
performance/interactions
Outcomes Time Box
Improvement Action Items
Team Agreements
1–2 hours
8THE MAC IVER GROUP, LLC © 2005-2016
10. Would your team find
this session useful?
Contact me to arrange a
session for one or more
of your teams.
DO THIS SESSION FOR YOUR TEAM?
10THE MAC IVER GROUP, LLC © 2005-2016
11. Robbie Mac Iver
▪ Past President/Advisor National Board of Directors
▪ Founder Houston Chapter
www.robbiemaciver.com robbie@robbiemaciver.com @robbiemaciverrobbiemaciver
Consulting ▪ Coaching ▪ Mentoring
▪ Agile Adoption ▪ Agile Leadership ▪ Product Management
▪ Leadership Agility 360™ Assessment
▪ Certified LeSS Practitioner
10+ Years Agile Techniques ▪ 10+ Years Project Leadership
▪ 20+ Years Information Technology