Scrum introduction
Download as PPT, PDF0 likes634 views
This document provides an overview of Scrum, an agile software development framework. Scrum uses short iterations called sprints, daily stand-up meetings, and emphasizes self-organizing cross-functional teams, transparency, empirical process control, and flexibility. The key Scrum roles are Product Owner, Scrum Master, and Team. Scrum artifacts include the Product Backlog, Sprint Backlog, and Burndown Chart. Meetings include Sprint Planning, Daily Stand-up, Sprint Review and Sprint Retrospective.
Scrum introduction
- 1. Scrum Primer José Teixidó - Web Development Supervisor
- 2. Status Quo Any similarities to real events in this presentation are not coincidence José Teixidó - Web Development Supervisor
- 3. Status Quo The Waterfall or cascade model José Teixidó - Web Development Supervisor
- 4. Status Quo The Waterfall Usually better when single threaded + Works by gravity (stuff always goes down) + Has a constant flow (conveyor effect) = Fail late process If something goes wrong you will find out at the worst possible moment Since you can't go against the current, and stuff keeps flowing down, you can't do anything without a lot of effort and disruption to the process José Teixidó - Web Development Supervisor
- 5. Status Quo Waterfall, usually this is more like it José Teixidó - Web Development Supervisor
- 6. Quo vadis? Scrum José Teixidó - Web Development Supervisor Credit: http://www.flickr.com/photos/kiwi/24658003/
- 7. Scrum Is based on: Empirical process control: Inspect the facts and adapt Transparency and honesty Time boxed iterations (Sprints) Incremental delivery Predictability optimization Risk control José Teixidó - Web Development Supervisor
- 8. Scrum Scrum - Who is using it? Microsoft Apple Google Samsung Nokia Mtvi + a lot of others... José Teixidó - Web Development Supervisor
- 9. Scrum The Roles José Teixidó - Web Development Supervisor
- 10. Scrum The Roles Pigs (committed) Product Owner/s Scrum Master Team Chickens (involved) Stake Holders Managers José Teixidó - Web Development Supervisor
- 11. Scrum Product Owner Maintains the Product Backlog Prioritizes desirables/features based on ROI Represents product users and customers Can be part of the Team but can’t act as Scrum Master José Teixidó - Web Development Supervisor Credit: http://www.flickr.com/photos/popculturegeek/5134635574/
- 12. Scrum The Team Estimates Does the actual work Self organized cross-functional team Maintains the Sprint Backlog Inspects and adapt as the sprint progress Ideally not just the developers but everybody required to make the product José Teixidó - Web Development Supervisor Credit: http://www.flickr.com/photos/hyku/2627349317/in/photostream/
- 13. Scrum The Scrum Master Enforces Scrum process rules Remove team impediments Protects the team from disturbances Provides Scrum coaching Can be part of the team José Teixidó - Web Development Supervisor Credit: http://www.flickr.com/photos/fdolleus/3844650865/sizes/z/in/photostream/
- 14. Scrum José Teixidó - Web Development Supervisor
- 15. Scrum Artifacts - Product Backlog Prioritized list of features posted as "User Stories" Constantly maintained and evolving Anyone can contribute but the Product Owners own the Product Backlog José Teixidó - Web Development Supervisor
- 16. Scrum Artifacts - Sprint Backlog List of features or items taken from the Product Backlog, that are going to be addressed on the next sprint The Team owns the Sprint Backlog and is responsible for keeping it updated José Teixidó - Web Development Supervisor
- 17. Scrum Artifacts - Sprint Burndown Chart José Teixidó - Web Development Supervisor
- 18. Scrum Meetings - Sprint Planing Meeting Who: All What: Product Owners + Team discuss and agree on which items will make it into the next Sprint based on Team estimations and dev/hour availability How long: Usually 2 hr limit Where: Meeting room José Teixidó - Web Development Supervisor
- 19. Scrum Meetings - Daily Stand Up Meeting Who: Team + Product Owners, however only the Team can speak (PO's can only speak if requested by somebody on the team) How long: 15 mins max, starts on time Where: Same place each day, team should be standing and nobody is leading José Teixidó - Web Development Supervisor
- 20. Scrum Meetings - Daily Stand Up Meeting Every Team member needs to answer three questions: What have you done since yesterday's Stand Up? What are you going to do today? Do you have any problems preventing you from accomplishing your tasks? José Teixidó - Web Development Supervisor
- 21. Scrum Meetings - Review Who: Everybody What: Review of what was "done" in the last sprint. Team discusses successes and problems on the last sprint José Teixidó - Web Development Supervisor
- 22. Scrum Meetings - Retro Who: Everybody, Scrum Master leads What: Team + PO reflects on problems and issues during last sprint. Scrum Master decides on process changes or adjustments based on input This is the basis of the empirical process José Teixidó - Web Development Supervisor
- 23. Scrum Meetings - Retro Two main questions: What went well during the last sprint? What could be improved for the next sprint? Inspect and adapt José Teixidó - Web Development Supervisor
- 24. Scrum Summary Scrum is agile, time boxed, adaptive and transparent 3 Main Roles: Product Owner Scrum Master Team 4 Meetings: Sprint Planning Daily Stand Up Sprint Review Sprint Retro 3 Artifacts: Product Backlog Sprint Backlog Burndown Chart José Teixidó - Web Development Supervisor
- 25. Scrum “ Scrum makes all news visible, be it good or bad. It considers intelligent people will want those news regardless so they can do the most beneficial thing for the whole organization” Ken Shwaber, co-developer of SCRUM Framework José Teixidó - Web Development Supervisor