Scrum: Engineering High-Quality Software – Presentation built with: – Agenda
Scrum: Engineering High-Quality Software – Presentation built with: – Agenda
1 0
scrum-engineering-high-quality-software
On Github agiletodd / scrum-engineering-high-quality-software
Scrum: Engineering High-Quality Software
Presentation built with:
Reveal.js in Visual Studio Code
Agenda
The Scrum Framework
The Scrum Development Team
Pursuing Technical Excellence
Scrum Overview
Roles
Artifacts
Events
Product Owner
Product Backlog
Sprint
Scrum Master
Sprint Backlog
Sprint Planning
Development Team
Increment
Daily Scrum
-
-
Sprint Review
-
-
Sprint Retrospective
Scrum Roles
-
Product Owner
Key Stakeholder, Value Maximizer, ROI, TCO, Responsible for 'What'
-
Scrum Master
Scrum Champion, Impediment Remover, Agile Leader
-
Development Team
6+-3, Responsible for 'How', Cross-functional, Self-organizing
Scrum Artifacts
-
Product Backlog
Requirements are Stored, Owner by Product Owner, Ordered on Value
-
Sprint Backlog
Dev Teams Sprint Focus, Subset of Product Backlog, Owned by Dev Team
-
Increment
"Done", Delivered in a Sprint, Potentially Shippable, High Quality
Scrum Events
Name
Duration
Attendees
Purpose
Sprint
<= 30 days
-
Container Event
Sprint Planning
<= 8 hrs
Scrum Team
Sprint Backlog, Sprint Goal
Daily Scrum
<= 15 mins
Dev Team
Plan for next 24 hours
Sprint Review
<= 4 hrs
Scrum Team + Stakeholders
Increment Inspection, What's next?
Sprint Retrospective
<= 3 hrs
Scrum Team
Inspect & Adapt Sprint, Kaizen
The Development Team
Cross-Functional Teams
Self-Organization
SCRUM VALUES
Technical Excellence
Increment
Definition of "done"
Technical Practices
Technical Design
Closing
- Todd Miller
- Professional Scrum Trainer (Scrum.org)
- Delivery Director (Celerity)
- todd@xperientsoftware.com
- agiletodd
- agiletodd
- todd_miller11
Scrum: Engineering High-Quality Software