Jason Knight
Software Developer
Scrum Master
Community Organizer
Writer (a bit)
2 Goals
Understand Scrum at a high level
Why Scrum is Awesome and extremely difficult
Exercise
Questions:
1) Future Developers of Revolutionary Products?
2) Future Business and Product Leaders?
3) Future Project Managers?
Scrum, why should I care!?
Manifesto for Agile Software Development
Analysis
Design
Testing
Maintenance
Coding
Waterfall Methodology
(6 - 18 months)
Risk / Value over Time
(Release)
Enter Scrum
Risk / Value over Time
(Release)
(Release)
(Release)
(Release)
(Release)
(Release)
(Release)
(Release)
(Release)
The "Rub"
Employee Roles are up-ended
Organizational Structure is deconstructed
Technical practices are pushed to the limit!
Scrum Roles
Development Team Member
3 - 9 Developers
Cross-functional
Self-organizing
Do the work of developing the product
Scrum Roles
Product Owner
One person, not committee
Optimizes value of Dev Team's work by ordering Product Backlog
Scrum Roles
Scrum Master
Manages Scrum
Coaches and Teaches
Servant Leader
Scrum Events
The Sprint
30 Days or less
Contains all other events
Goal is to produce a potentially releasable increment of the Product
Scrum Events
Sprint Planning
Forecast work that can be done in Sprint
Collaborate to form goal for Sprint
Developers form plan to accomplish goal
Scrum Events
Daily Scrum
15 Minutes or Less
Form Daily Plan to progress toward goal of Sprint
Daily!!
Scrum Events
Sprint Review
Get feedback on Product Increment
Add to and update Product Backlog
Pivot!?
Scrum Events
Sprint Retrospective
Examine the Scrum Team
Make Improvements
Kaizen!!
