Scrum	
  history



                            S
                            SCRUM




Monday, September 6, 2010
Scrum	
  history



                                        S
                                        SCRUM




          ...
Scrum	
  history



                                                                      S
                              ...
Scrum	
  history



                                                                                               S
     ...
Scrum	
  history



                                                                                                      ...
Scrum	
  history



                                                                                                      ...
Prescrip0ve	
  vs	
  Adap0ve



                                    S
                                    SCRUM




Monday...
Prescrip0ve	
  vs	
  Adap0ve



                                         S
                                         SCRUM
...
Prescrip0ve	
  vs	
  Adap0ve



                                                        S
                                ...
Prescrip0ve	
  vs	
  Adap0ve



                                                                        S
                ...
Prescrip0ve	
  vs	
  Adap0ve



                                                                                          ...
Prescrip0ve	
  vs	
  Adap0ve



                                                                                          ...
Prescrip0ve	
  vs	
  Adap0ve



                                                                                          ...
Prescrip0ve	
  vs	
  Adap0ve



                                                                                          ...
How	
  do	
  we	
  run	
  a	
  Scrum	
  project?



                                                           S
         ...
Scrum	
  is	
  Simple?



                                 S
                                 SCRUM




Monday, September ...
Scrum	
  is	
  Simple?



                                 S
                                 SCRUM




        ✓Like	
  g...
Scrum	
  is	
  Simple?



                                                            S
                                  ...
Scrum	
  is	
  Simple?



                                                            S
                                  ...
Scrum	
  is	
  Simple?



                                                            S
                                  ...
Team



                                                                       S
                                         ...
Team



                                                                       S
                                         ...
Product	
  Owner



                                                               S
                                     ...
Stakeholders



                                                            S
                                            ...
Stakeholders



                                                            S
                                            ...
Stakeholders



                                                                   S
                                     ...
ScrumMaster



                                                 S
                                                 SCRUM

...
Overview	
  Roles



                            S
                            SCRUM




Monday, September 6, 2010
Overview	
  Roles



                                            S
                                            SCRUM




 ...
Overview	
  Roles



                                                   S
                                                ...
Overview	
  Roles



                                                   S
                                                ...
Sprint




Monday, September 6, 2010
Sprint




                            Vision: anticipated
                            ROI, Releases,
                    ...
Sprint




                              Vision: anticipated
                              ROI, Releases,
                ...
Sprint




                                        Vision: anticipated
                                        ROI, Releas...
Sprint




                                                            Vision: anticipated
                               ...
Sprint




                                                            Vision: anticipated
                               ...
Sprint


   Sprint
   planning II
                 Wed 11:00


           Iteration Plan
                                 ...
Sprint

                             Sprint
   Sprint                    Backlog
   planning II
                 Wed 11:00...
Sprint

                             Sprint
   Sprint                    Backlog
   planning II
                 Wed 11:00...
Sprint

                                                                               Impediment
                        ...
Sprint

                                                                               Impediment
                        ...
Sprint

                                                                               Impediment
                        ...
Sprint

                                                                               Impediment
                        ...
Monday, September 6, 2010
End	
  of	
  Scrum	
  Overview




Monday, September 6, 2010
Upcoming SlideShare
Loading in...5
×

Intro Scrum

842

Published on

Intro to Scrum - with thanks to Zilverline for the nice CSPO training

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
842
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Intro Scrum

  1. 1. Scrum  history S SCRUM Monday, September 6, 2010
  2. 2. Scrum  history S SCRUM 1993 First Scrum team formed by Jeff Sutherland at Easel Corp. Monday, September 6, 2010
  3. 3. Scrum  history S SCRUM 1993 1996 First Scrum team formed by ”Scrum Development Process” Jeff Sutherland at Easel published by Ken Schwaber. Corp. Monday, September 6, 2010
  4. 4. Scrum  history S SCRUM 1993 1996 1998 First Scrum team formed by ”Scrum Development Process” ”Scrum Jeff Sutherland at Easel published by Ken Schwaber. a pattern language for Corp. hyperproductive software development” published by Ken, Jeff, et al. Monday, September 6, 2010
  5. 5. Scrum  history S SCRUM 1993 1996 1998 2001 First Scrum team formed by ”Scrum Development Process” ”Scrum Agile Manifesto Jeff Sutherland at Easel published by Ken Schwaber. a pattern language for Corp. hyperproductive software development” published by Ken, Jeff, et al. Monday, September 6, 2010
  6. 6. Scrum  history S SCRUM 1993 1996 1998 2001 2001 First Scrum team formed by ”Scrum Development Process” ”Scrum Agile Manifesto ”Agile Software Development Jeff Sutherland at Easel published by Ken Schwaber. a pattern language for with Scrum” published by Ken Corp. hyperproductive software Schwaber and Mike Beedle. development” published by Ken, Jeff, et al. Monday, September 6, 2010
  7. 7. Prescrip0ve  vs  Adap0ve S SCRUM Monday, September 6, 2010
  8. 8. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive Monday, September 6, 2010
  9. 9. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive Scrum (11) • ScrumMaster • Product Owner • Team • Sprint planning meeting I + II • Sprint • Daily Scrum • Sprint review • Sprint retrospective • Product backlog • Sprint backlog Monday, September 6, 2010
  10. 10. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive XP Scrum (13) (11) • Whole team • ScrumMaster • Coding • Product Owner standard • Team • Sprint planning • TDD meeting I + II • Collective • Sprint ownership • Daily Scrum • Customer • Sprint review tests • Sprint • Pair retrospective • Product backlog programming • Sprint backlog • Refactoring • Planning game • Continuous integration • Simple design • Sustainable pace • Metaphor • Small releases Monday, September 6, 2010
  11. 11. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive XP Scrum Kanban (13) (11) (3) • Whole team • ScrumMaster • Visualize the • Coding • Product Owner workflow standard • Team • Limit WIP • Sprint planning • TDD meeting I + II • Measure and • Collective • Sprint optimize lead time ownership • Daily Scrum • Customer • Sprint review tests • Sprint • Pair retrospective • Product backlog programming • Sprint backlog • Refactoring • Planning game • Continuous integration • Simple design • Sustainable pace • Metaphor • Small releases Monday, September 6, 2010
  12. 12. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive RUP XP Scrum Kanban (120+) (13) (11) (3) • Architecture Reviewer • Business use case realization • Business Designer • Business use-case model • Business-Model Reviewer • Business vision • Whole team • ScrumMaster • Visualize the • • Business-Process Analyst Capsule Designer • • Change request Configuration audit findings • Coding • Product Owner workflow • Change Control Manager • Configuration management plan standard • Team • Limit WIP • Code Reviewer • Data model • Configuration Manager • Deployment model • Sprint planning • Course Developer • Deployment plan • TDD meeting I + II • Measure and • Database Designer • Design guidelines • Deployment Manager • Design model • Collective • Sprint optimize lead time • Design Reviewer • Development case • Designer • Development-organization ownership • Daily Scrum • Graphic Artist assessment • Implementer • End-user support mateirla • Customer • Sprint review • • Integrator Process Engineer • • Glossary Implementation model tests • Sprint • Project Manager • Installation artifacts • Pair retrospective • Project Reviewer • Integration build plan • Requirements Reviewer • Issues list • Product backlog • Requirements Specifier • Iteration assessment programming • Sprint backlog • Software Architect • Iteration plan • Stakeholder • Manual styleguide • Refactoring • System Administrator • Programming guidelines • System Analyst • Quality assurance plan • Planning • Technical Writer • Reference architecture • Test Analyst • Release notes game • Test Designer • Requirements attributes • Test Manager • Requirements • Continuous • Tester management plan • Tool Specialist • Review record integration • User-Interface Designer • Risk list • Architectural analysis • Risk management plan • Simple design • Assess Viability of architectural • Software architecture proof-of-concept document • Sustainable • Capsule design • Software development • Class design plan pace • Construct architectural proof-of- • Software requirements concept specification • Metaphor • Database design • Stakeholder requests • Describe distribution • Status assessment • Small releases • Describe the run-time • Supplementary business architecture specification • Design test packages and • Supplementary specification classes • Target organization assessment • Develop design guidelines • Test automation architecture • Develop programming • Test cases guidelines • Test environment configuration • Identify design elements • Test evaluation summary • Identify design mechanisms • Test guidelines • Incorporate design elements • Test ideas list • Prioritize use cases • Test interface specification • Review the architecture • Test plan • Review the design • Test suite • Structure the implementation • Tool guidelines model • Training materials • Subsystem design • Use case model • Use-case analysis • Use case package • Use-case design • Use-case modeling guidelines • Analysis model • Use-case realization • Architectural proof-of-concept • Use-case storyboard • Bill of materials • User-interface guidelines • Business architecture document • User-interface prototype • Business case • Vision • Business glossary • Work order • Business modeling guidelines • Workload analysis model • Business object model • Business rules • Business use case Monday, September 6, 2010
  13. 13. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive RUP XP Scrum Kanban Do  Whatever (120+) (13) (11) (3) (0) • Architecture Reviewer • Business use case realization • Business Designer • Business use-case model • Business-Model Reviewer • Business vision • Whole team • ScrumMaster • Visualize the • • Business-Process Analyst Capsule Designer • • Change request Configuration audit findings • Coding • Product Owner workflow • Change Control Manager • Configuration management plan standard • Team • Limit WIP • Code Reviewer • Data model • Configuration Manager • Deployment model • Sprint planning • Course Developer • Deployment plan • TDD meeting I + II • Measure and • Database Designer • Design guidelines • Deployment Manager • Design model • Collective • Sprint optimize lead time • Design Reviewer • Development case • Designer • Development-organization ownership • Daily Scrum • Graphic Artist assessment • Implementer • End-user support mateirla • Customer • Sprint review • • Integrator Process Engineer • • Glossary Implementation model tests • Sprint • Project Manager • Installation artifacts • Pair retrospective • Project Reviewer • Integration build plan • Requirements Reviewer • Issues list • Product backlog • Requirements Specifier • Iteration assessment programming • Sprint backlog • Software Architect • Iteration plan • Stakeholder • Manual styleguide • Refactoring • System Administrator • Programming guidelines • System Analyst • Quality assurance plan • Planning • Technical Writer • Reference architecture • Test Analyst • Release notes game • Test Designer • Requirements attributes • Test Manager • Requirements • Continuous • Tester management plan • Tool Specialist • Review record integration • User-Interface Designer • Risk list • Architectural analysis • Risk management plan • Simple design • Assess Viability of architectural • Software architecture proof-of-concept document • Sustainable • Capsule design • Software development • Class design plan pace • Construct architectural proof-of- • Software requirements concept specification • Metaphor • Database design • Stakeholder requests • Describe distribution • Status assessment • Small releases • Describe the run-time • Supplementary business architecture specification • Design test packages and • Supplementary specification classes • Target organization assessment • Develop design guidelines • Test automation architecture • Develop programming • Test cases guidelines • Test environment configuration • Identify design elements • Test evaluation summary • Identify design mechanisms • Test guidelines • Incorporate design elements • Test ideas list • Prioritize use cases • Test interface specification • Review the architecture • Test plan • Review the design • Test suite • Structure the implementation • Tool guidelines model • Training materials • Subsystem design • Use case model • Use-case analysis • Use case package • Use-case design • Use-case modeling guidelines • Analysis model • Use-case realization • Architectural proof-of-concept • Use-case storyboard • Bill of materials • User-interface guidelines • Business architecture document • User-interface prototype • Business case • Vision • Business glossary • Work order • Business modeling guidelines • Workload analysis model • Business object model • Business rules • Business use case Monday, September 6, 2010
  14. 14. Prescrip0ve  vs  Adap0ve S SCRUM More prescriptive More adaptive RUP XP Scrum Kanban Do  Whatever (120+) (13) (11) (3) (0) • Architecture Reviewer • Business use case realization • Business Designer • Business use-case model • Business-Model Reviewer • Business vision • Whole team • ScrumMaster • Visualize the • • Business-Process Analyst Capsule Designer • • Change request Configuration audit findings • Coding • Product Owner workflow • Change Control Manager • Configuration management plan standard • Team • Limit WIP • Code Reviewer • Data model • Configuration Manager • Deployment model • Sprint planning • Course Developer • Deployment plan • TDD meeting I + II • Measure and • Database Designer • Design guidelines • Deployment Manager • Design model • Collective • Sprint optimize lead time • Design Reviewer • Development case • Designer • Development-organization ownership • Daily Scrum • Graphic Artist assessment • Implementer • End-user support mateirla • Customer • Sprint review • • Integrator Process Engineer • • Glossary Implementation model tests • Sprint • Project Manager • Installation artifacts • Pair retrospective • Project Reviewer • Integration build plan • Requirements Reviewer • Issues list • Product backlog • Requirements Specifier • Iteration assessment programming • Sprint backlog • Software Architect • Iteration plan • Stakeholder • Manual styleguide • Refactoring • System Administrator • Programming guidelines • System Analyst • Quality assurance plan • Planning • Technical Writer • Reference architecture • Test Analyst • Release notes game • Test Designer • Requirements attributes • Continuous A complex process causes • Test Manager • Requirements • Tester management plan • Tool Specialist • Review record integration • User-Interface Designer • Risk list • Architectural analysis • Risk management plan • Simple design simple behavior • Assess Viability of architectural • Software architecture proof-of-concept document • Sustainable • Capsule design • Software development • Class design plan pace • Construct architectural proof-of- • Software requirements concept specification • Metaphor • Database design • Stakeholder requests • Describe distribution • Status assessment • Small releases • Describe the run-time • Supplementary business architecture specification • Design test packages and • Supplementary specification A simple process causes classes • Target organization assessment • Develop design guidelines • Test automation architecture • Develop programming • Test cases guidelines • Test environment configuration • Identify design elements • Test evaluation summary • Identify design mechanisms • Test guidelines complex behavior • Incorporate design elements • Test ideas list • Prioritize use cases • Test interface specification • Review the architecture • Test plan • Review the design • Test suite • Structure the implementation • Tool guidelines model • Training materials • Subsystem design • Use case model • Use-case analysis • Use case package • Use-case design • Use-case modeling guidelines • Analysis model • Use-case realization • Architectural proof-of-concept • Use-case storyboard • Bill of materials • User-interface guidelines • Business architecture document • User-interface prototype • Business case • Vision • Business glossary • Work order • Business modeling guidelines • Workload analysis model • Business object model • Business rules • Business use case Monday, September 6, 2010
  15. 15. How  do  we  run  a  Scrum  project? S SCRUM 3  Roles 2  Backlogs 6  Timeboxes Monday, September 6, 2010
  16. 16. Scrum  is  Simple? S SCRUM Monday, September 6, 2010
  17. 17. Scrum  is  Simple? S SCRUM ✓Like  game  rules Monday, September 6, 2010
  18. 18. Scrum  is  Simple? S SCRUM ✓Like  game  rules ✓Simple  to  explain  chess  or   soccer Monday, September 6, 2010
  19. 19. Scrum  is  Simple? S SCRUM ✓Like  game  rules ✓Simple  to  explain  chess  or   soccer ✓But  difficult  to  play  (to  win) Monday, September 6, 2010
  20. 20. Scrum  is  Simple? S SCRUM ✓Like  game  rules ✓Simple  to  explain  chess  or   soccer ✓But  difficult  to  play  (to  win) ✓You’re  out  on  the  field  and   anyone  can  see Monday, September 6, 2010
  21. 21. Team S SCRUM • Fully  commiGed  team(s) • Cross-­‐func0onal,  7  +/-­‐  2  members • Self  organizing   • Es0mates  and  does  all  the  work   • Demos  work  results  to  the             Product  Owner Monday, September 6, 2010
  22. 22. Team S SCRUM • Fully  commiGed  team(s) • Cross-­‐func0onal,  7  +/-­‐  2  members • Self  organizing   • Es0mates  and  does  all  the  work   • Demos  work  results  to  the             Product  Owner Monday, September 6, 2010
  23. 23. Product  Owner S SCRUM •Fully  CommiGed,  Responsible  for  ROI •Priori0zes  the  work z i l •In-­‐between  customer  and  team:   v e r l i n e walks,  talks,  nego>ates,  communicates •Accepts  or  rejects  work  results Monday, September 6, 2010
  24. 24. Stakeholders S SCRUM • Everyone  that  has  a  stake  in   project,  but  is  not  in  team –Customers –End  users –DBA –Support –Architects –Testers Monday, September 6, 2010
  25. 25. Stakeholders S SCRUM • Everyone  that  has  a  stake  in   project,  but  is  not  in  team –Customers –End  users –DBA –Support –Architects Confusing, right? –Testers Monday, September 6, 2010
  26. 26. Stakeholders S SCRUM • Everyone  that  has  a  stake  in   project,  but  is  not  in  team –Customers –End  users –DBA –Support You’re either in –Architects Confusing, the team, right? or you’re –Testers out Monday, September 6, 2010
  27. 27. ScrumMaster S SCRUM • Ensures  that  the  process   is  followed.   • Removes  impediments • Change  Agent Monday, September 6, 2010
  28. 28. Overview  Roles S SCRUM Monday, September 6, 2010
  29. 29. Overview  Roles S SCRUM Stakeholders Product Owner Monday, September 6, 2010
  30. 30. Overview  Roles S SCRUM Stakeholders Team Product Owner Monday, September 6, 2010
  31. 31. Overview  Roles S SCRUM ScrumMaster Stakeholders Team Product Owner Monday, September 6, 2010
  32. 32. Sprint Monday, September 6, 2010
  33. 33. Sprint Vision: anticipated ROI, Releases, Milestones Monday, September 6, 2010
  34. 34. Sprint Vision: anticipated ROI, Releases, Milestones Product Backlog: Emerging, prioritized requirements Monday, September 6, 2010
  35. 35. Sprint Vision: anticipated ROI, Releases, Milestones Product Backlog Product Backlog: Emerging, prioritized requirements Monday, September 6, 2010
  36. 36. Sprint Vision: anticipated ROI, Releases, Milestones Sprint planning I Product Wed 09:00 Backlog Product Backlog: Emerging, prioritized requirements Monday, September 6, 2010
  37. 37. Sprint Vision: anticipated ROI, Releases, Milestones Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Monday, September 6, 2010
  38. 38. Sprint Sprint planning II Wed 11:00 Iteration Plan Vision: anticipated ROI, Releases, Milestones Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Monday, September 6, 2010
  39. 39. Sprint Sprint Sprint Backlog planning II Wed 11:00 Iteration Plan Vision: anticipated ROI, Releases, Milestones Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Monday, September 6, 2010
  40. 40. Sprint Sprint Sprint Backlog planning II Wed 11:00 Development Iteration Plan Release Installation Vision: anticipated Analysis ROI, Releases, Milestones Testing Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Monday, September 6, 2010
  41. 41. Sprint Impediment Sprint list 09:00 Sprint Backlog Daily standup meeting planning II Wed 11:00 Development Iteration Plan Release Installation Vision: anticipated Analysis ROI, Releases, Milestones Testing Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Monday, September 6, 2010
  42. 42. Sprint Impediment Sprint list 09:00 Sprint Backlog Daily standup meeting planning II Wed 11:00 Development Iteration Plan Release Installation Vision: anticipated Analysis ROI, Releases, Milestones Testing demo Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Monday, September 6, 2010
  43. 43. Sprint Impediment Sprint list 09:00 Sprint Backlog Daily standup meeting planning II Wed 11:00 Development Iteration Plan Release Installation Vision: anticipated Analysis ROI, Releases, Milestones Testing demo Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Tue 13:00 Sprint review Monday, September 6, 2010
  44. 44. Sprint Impediment Sprint list 09:00 Sprint Backlog Daily standup meeting planning II Wed 11:00 Development Iteration Plan Release Installation Vision: anticipated Analysis ROI, Releases, Milestones Testing demo Sprint planning I Product Wed 09:00 Backlog Selected Product Backlog: Requirements Emerging, prioritized requirements Tue 15:00 Tue 13:00 Sprint retrospective Sprint review Monday, September 6, 2010
  45. 45. Monday, September 6, 2010
  46. 46. End  of  Scrum  Overview Monday, September 6, 2010

×