1 / 22

SCRUM 59 minutes Giovanni Asproni Rachel Davies

SCRUM 59 minutes Giovanni Asproni Rachel Davies. Red Yellow Green Blue Red Blue Yellow Green Blue. 59- Minute SCRUM – Bringing SCRUM Alive!. Timetable: Introduce the SCRUM Concepts 30 minutes 59-Minute Exercise: Complete Sprint Planning Meeting 10 minutes

corine
Download Presentation

SCRUM 59 minutes Giovanni Asproni Rachel Davies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCRUM 59 minutesGiovanni AsproniRachel Davies

  2. Red Yellow Green Blue Red Blue Yellow Green Blue

  3. 59- Minute SCRUM – Bringing SCRUM Alive! Timetable: Introduce the SCRUM Concepts 30 minutes 59-Minute Exercise: Complete Sprint Planning Meeting 10 minutes Conduct a Sprint “Day 1” 10 minutes Conduct a Daily Scrum Meeting 05 minutes Conduct a Sprint “Day 2” 10 minutes Conduct a Sprint Review and Demo 06 minutes per team (x4) Debrief the exercise 15 minutes Questions 15 minutes

  4. SCRUM Practices • Product Backlog • Sprint • Sprint Planning Meeting • Sprint Backlog • Roles • Product Owner, Scrum Master, Scrum Team • Daily Scrum Meeting • Sprint Review Meeting

  5. SCRUM Lifecycle 24 hours Daily Scrum Meeting Backlog tasks expanded by team 30 days Sprint Backlog Potentially Shippable Product Increment Product Backlog As prioritized by Product Owner

  6. Product Backlog • Prioritized list of work to be performed on a product • Anyone can contribute backlog items • Product Owner responsible for prioritisation

  7. Sprint • A fixed period of 30 days to develop a deliverable product • The Sprint includes design, coding, testing, and documentation • Once a Sprint has started only the Scrum Team can add or remove items in Sprint backlog • Abnormal termination of Sprint is called for when the Sprint Goal no longer makes sense

  8. Sprint Planning Meeting to set the next Sprint goal Product Backlog Team Capabilities Business Conditions Technology Stability Executable Product Increment ReviewConsider Organize Next Sprint Goal Sprint Backlog

  9. Sprint Burndown Chart

  10. Daily Scrum Daily 15 minute status meeting Team stands in a circle facing each other Each team member answers 3 questions: • What have you done since the last Scrum? • What will you do between now and the next Scrum? • What got in your way of doing work? For synchronization not problem solving!

  11. Sprint Review • During this meeting the team presents to management, customers, users and the Product Owner the product increment that has been built during the Sprint • The team tells the story of its journey during the Sprint. • Powerpoint presentations are forbidden!

  12. Scrum Team • Self-organizing • Cross-functional with no roles • Seven plus or minus two • Responsible for committing to work • Authority to do whatever is needed to meet commitment

  13. Chickens & Pigs • Members of Scrum Team are known as Pigs because they are committed to delivering Sprint Goal • People who are involved but not dedicated to the project are known asChickens - they attend Scrum meetings as observers

  14. Product Owner • Sets development schedule by prioritizing backlog • One person in this role ensures that only one set of requirements drives development • Can be influenced by committees, management, customers, sales people, but is the only person that prioritizes • Works with others to estimate items on Product Backlog • Eliminates confusion of multiple bosses, different opinions, and interference

  15. Scrum Master • The Scrum Master is responsible for • the success of SCRUM • establishing SCRUM practices and rules, shielding the team and removing obstacles • representing management to the project

  16. Exercise - Sprint Planning Sprint Planning Meeting 10 mins • Review the Product Backlog • Select an achievable Sprint Goal with Product Owner • Determine what the number of features might be that your team can complete • Think about initial assignments • Produce a Sprint Backlog on team worksheet

  17. Example Sprint Backlog Sprint Goal: Explain Entertainment Potential effort: 6 members * 20 min = 120 minutes • Describe entertainment in the park • Music 20 min • Comedy/Improv 20 min • Describe special events • Bonfire Night 15 min • Sandwich appreciation month 10 min • Suggest related nearby activities and events • Lego Museum 25 min • Giant ball of twine 17 min = 107minutes

  18. YOUR Sprint Backlog Sprint Goal: • ___________________________ • ___min • ___ min • ___________________________ • ___min • ___min • ___________________________ • ___min • ___min • ____________________________ • ___min • ___min = _____ TOTAL

  19. Exercise - Daily Scrum Scrum Meeting 5 mins Team stands in a circle facing each other Each team member answers 3 questions: • What have I completed since our last meeting ? • What do I intend to complete before our next meeting ? • What is getting in my way ?

  20. Exercise - Sprint Review Sprint Review 6 mins Elect a spokesperson to facilitate the Sprint Review and Demo Meeting Conduct a Sprint Review and Demo of your brochure at the end of the sprint: • What is the potentially shippable increment (Demo)? • What did we complete of our Sprint Backlog? • What is the feedback from our Product Owner?

  21. A Few Rules • Each team MUST work together • Everyone MUST have work in the Sprint • Each team MUST demo something at the end of the Sprint (free of choice about how) • Each team MUST complete their Sprint Planning with a Sprint Backlog on the worksheet • Each team MUST conduct their Daily Scrum meeting • No Scrum Master is used in this exercise • No predefined roles on Team; self-organization rules!

  22. Questions You can find out more information at: • http://www.scrumalliance.org/ • Book “Agile Software Development with SCRUM” by Ken Schwaber, Mike Beedle • Book “Agile Project Management with SCRUM” by Ken Schwaber • http://www.controlchaos.com/ - Ken Schwaber’s own site

More Related