Introduction to  Scrum  <ul><ul><li>Presented  </li></ul></ul><ul><ul><li>at </li></ul></ul><ul><ul><li>Agile Awareness Wo...
Agenda <ul><li>Agile Manifesto </li></ul><ul><li>What is Scrum </li></ul><ul><li>Scrum core ideas </li></ul><ul><li>Diffic...
Quick Poll <ul><li>Agile Manifesto. </li></ul><ul><li>Scrum. </li></ul><ul><li>Agile methodologies. </li></ul><ul><li>Requ...
Agile Manifesto <ul><li>Individuals and Interactions  over processes and tools </li></ul><ul><li>Working software  over co...
Scrum Framework <ul><li>Roles : Product Owner, Scrum Master, Team </li></ul><ul><li>Ceremonies : Spring planning, Spring r...
What is Scrum? <ul><li>The name Scrum </li></ul><ul><li>Prioritized activities in a product backlog </li></ul><ul><li>Spri...
Scrum Flow
Scrum Roles <ul><li>Product owner </li></ul><ul><li>Scrum master </li></ul><ul><li>Scrum team (5-9 people)‏ </li></ul>
Product Owner <ul><li>Maintaining the product backlog </li></ul><ul><ul><ul><ul><li>Prioritizing </li></ul></ul></ul></ul>...
Scrum Team <ul><li>Teams of 7 +/- 2 participants   </li></ul><ul><li>Crossfunctional </li></ul><ul><li>Best experts in the...
Scrum Master <ul><li>Responsible for the process </li></ul><ul><li>Responsible for optimizing the Scrum environment </li><...
Spring Planning / Workshop <ul><li>1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and p...
Daily Scrum <ul><li>Daily Scrum must not last more than 15 minutes </li></ul><ul><li>Held same place, same time, every wor...
Sprint presentation <ul><li>Team presents work done in the sprint.  </li></ul><ul><ul><ul><li>What have we achieved? </li>...
Sprint Retrospective <ul><li>Run by Scrum Master </li></ul><ul><li>Team reflects on the sprint </li></ul><ul><ul><ul><li>W...
Who is using Scrum? <ul><li>US Federal Reserve  </li></ul><ul><li>SAP </li></ul><ul><li>H P </li></ul><ul><li>Motorola </l...
Scrum Core Ideas <ul><ul><li>Everything is time-boxed. </li></ul></ul><ul><ul><li>Inspect & Adapt. </li></ul></ul><ul><ul>...
Common Problems <ul><li>Creating cross-functional teams.  </li></ul><ul><li>Thinking in time-boxed manner – requires disci...
Questions!
Feedback <ul><ul><li>[email_address] </li></ul></ul>
License <ul><ul><li>This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License </l...
Upcoming SlideShare
Loading in...5
×

Introduction To Scrum

7,143

Published on

This is an Introduction to Scrum presentation by Deepak Mittal, IntelliGrape software.

Published in: Technology, Sports
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
7,143
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
849
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Introduction To Scrum

  1. 1. Introduction to Scrum <ul><ul><li>Presented </li></ul></ul><ul><ul><li>at </li></ul></ul><ul><ul><li>Agile Awareness Workshop </li></ul></ul><ul><ul><li>conducted by Xebia </li></ul></ul><ul><ul><li>by </li></ul></ul><ul><ul><li>Deepak Mittal, IntelliGrape Software </li></ul></ul><ul><ul><li>on </li></ul></ul><ul><ul><li>June 14, 2008 </li></ul></ul>
  2. 2. Agenda <ul><li>Agile Manifesto </li></ul><ul><li>What is Scrum </li></ul><ul><li>Scrum core ideas </li></ul><ul><li>Difficulties with practising Scrum </li></ul><ul><li>Questions </li></ul><ul><li>Feedback </li></ul>
  3. 3. Quick Poll <ul><li>Agile Manifesto. </li></ul><ul><li>Scrum. </li></ul><ul><li>Agile methodologies. </li></ul><ul><li>Requirements can be frozen. </li></ul><ul><li>Standish Group report. </li></ul>
  4. 4. Agile Manifesto <ul><li>Individuals and Interactions over processes and tools </li></ul><ul><li>Working software over comprehensive documentation </li></ul><ul><li>Customer collaboration over contract negotiation </li></ul><ul><li>Responding to change over following a plan. </li></ul>
  5. 5. Scrum Framework <ul><li>Roles : Product Owner, Scrum Master, Team </li></ul><ul><li>Ceremonies : Spring planning, Spring review, Sprint retrospective, Daily Scrum Meeting </li></ul><ul><li>Artifacts : Product backlog, Spring backlog, Burndown Chart </li></ul>
  6. 6. What is Scrum? <ul><li>The name Scrum </li></ul><ul><li>Prioritized activities in a product backlog </li></ul><ul><li>Sprint in 30 calendar days (22 working days)‏ </li></ul><ul><li>Self-organized, crossfunctional teams, 7 +/- 2 </li></ul><ul><li>Daily stand-up </li></ul>
  7. 7. Scrum Flow
  8. 8. Scrum Roles <ul><li>Product owner </li></ul><ul><li>Scrum master </li></ul><ul><li>Scrum team (5-9 people)‏ </li></ul>
  9. 9. Product Owner <ul><li>Maintaining the product backlog </li></ul><ul><ul><ul><ul><li>Prioritizing </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Presentation of product backlog to the team </li></ul></ul></ul></ul><ul><li>Participation in sprint planning and sprint presentation </li></ul><ul><li>Responsible for product vision, ROI and release management </li></ul><ul><li>Can follow sprint via Daily Scrum, Burndown chart and via Scrum Master </li></ul>
  10. 10. Scrum Team <ul><li>Teams of 7 +/- 2 participants </li></ul><ul><li>Crossfunctional </li></ul><ul><li>Best experts in the domain area </li></ul><ul><li>Maintaining the sprint backlog </li></ul><ul><li>Self-organizing </li></ul><ul><ul><li>Team decides who shall do what </li></ul></ul><ul><ul><li>They inspect and adapt as the sprint goes along </li></ul></ul><ul><li>Have most of the powers during a sprint </li></ul>
  11. 11. Scrum Master <ul><li>Responsible for the process </li></ul><ul><li>Responsible for optimizing the Scrum environment </li></ul><ul><li>Responsible for Daily Scrum </li></ul><ul><li>Runs Sprint Retrospective </li></ul><ul><li>Coach </li></ul>
  12. 12. Spring Planning / Workshop <ul><li>1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization. </li></ul><ul><li>2. Team determines how much time it has available to commit during the Sprint </li></ul><ul><li>3 . Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan </li></ul><ul><ul><li>- Validates commitment by breaking down into tasks with time estimates </li></ul></ul><ul><ul><li>- Team decides who will do what, when; thinks through sequencing, dependencies, possible task trades, and so forth. </li></ul></ul>
  13. 13. Daily Scrum <ul><li>Daily Scrum must not last more than 15 minutes </li></ul><ul><li>Held same place, same time, every working day </li></ul><ul><li>Participants can not be late </li></ul><ul><li>Anybody can come, but only the team and Scrum Master can speak </li></ul><ul><li>3 questions answered by each team member </li></ul><ul><ul><ul><li>What did I do yesterday? </li></ul></ul></ul><ul><ul><ul><li>What am I going to do today? </li></ul></ul></ul><ul><ul><ul><li>What are my impediments? </li></ul></ul></ul>
  14. 14. Sprint presentation <ul><li>Team presents work done in the sprint. </li></ul><ul><ul><ul><li>What have we achieved? </li></ul></ul></ul><ul><ul><ul><li>Should show finished functionality. </li></ul></ul></ul><ul><ul><ul><li>What is missing. </li></ul></ul></ul><ul><ul><ul><li>Maximum of 2 hours for presentation. </li></ul></ul></ul>
  15. 15. Sprint Retrospective <ul><li>Run by Scrum Master </li></ul><ul><li>Team reflects on the sprint </li></ul><ul><ul><ul><li>What went well? </li></ul></ul></ul><ul><ul><ul><li>What did not go so well? </li></ul></ul></ul><ul><ul><ul><li>How can we improve? </li></ul></ul></ul>
  16. 16. Who is using Scrum? <ul><li>US Federal Reserve </li></ul><ul><li>SAP </li></ul><ul><li>H P </li></ul><ul><li>Motorola </li></ul><ul><li>TransUnion </li></ul><ul><li>Google </li></ul><ul><li>Microsoft </li></ul><ul><li>Yahoo </li></ul><ul><li>Sun </li></ul><ul><li>Siemens </li></ul><ul><li>Nokia </li></ul><ul><li>Philips </li></ul><ul><li>BBC </li></ul><ul><li>IBM </li></ul>
  17. 17. Scrum Core Ideas <ul><ul><li>Everything is time-boxed. </li></ul></ul><ul><ul><li>Inspect & Adapt. </li></ul></ul><ul><ul><li>You can-not plan everything. </li></ul></ul><ul><ul><li>Fail early. </li></ul></ul><ul><ul><li>Shippable product at the end of every iteration/sprint. </li></ul></ul><ul><ul><li>Iterative development. </li></ul></ul><ul><ul><li>Cross-functional teams. </li></ul></ul><ul><ul><li>Self-organizing teams. </li></ul></ul><ul><ul><li>Team owns the sprint backlog. </li></ul></ul>
  18. 18. Common Problems <ul><li>Creating cross-functional teams. </li></ul><ul><li>Thinking in time-boxed manner – requires discipline. </li></ul><ul><li>Shifting from the paradigm of TL/PM- ownership to team-ownership. </li></ul><ul><li>Making use of Sprint retrospective effectively. </li></ul>
  19. 19. Questions!
  20. 20. Feedback <ul><ul><li>[email_address] </li></ul></ul>
  21. 21. License <ul><ul><li>This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License </li></ul></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×