Mujeebur rahmansaher introduction-to-scrum_v2

386 views

Published on

introduction-to-scrum

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

  • Be the first to like this

No Downloads
Views
Total views
386
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Mujeebur rahmansaher introduction-to-scrum_v2

  1. 1. IT Lunch and Learn – September 2013 TOPIC :Introduction to Scrum By: Mujeebur Rahmansaher
  2. 2. Agenda • Agile Manifesto • Scrum Alliance Survey • What is Scrum • Waterfall vs Scrum • Scrum Framework • Scrum Roles and Ceremonies • Ball Point game • Summary
  3. 3. Dilbert goes agile
  4. 4. Agile Manifesto Individuals and Interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan. That is, while there is value in the items on the right, we value the items on the left more.
  5. 5. Scrum Alliance Survey - 2007 • Seventy-five percent of those who responded report that Scrum is meeting or exceeding their organizations’ needs. • Forty-five percent of respondents report their organizations are either very pleased with Scrum or believe it exceeds their organizations’ expectations. • Nearly 90 percent (87%) of respondents report personal satisfaction with Scrum.
  6. 6. What is Scrum? • Scrum is agile software development framework. • A wrapper for engineering practices • A simple approach to effectively manage complex problems • A process to maximize and maintain productivity • A process to improve collaboration, meaningful communication and maximize cooperation
  7. 7. Waterfall vs. Scrum Waterfall Scrum / Agile Requirements docs Just-in-time, informal requirements Occasional “customer” involvement Frequent “customer” involvement Start-to-finish Project Plan Product Backlog. Plan for Sprint. Sketchy beyond that. Tasks are assigned Assigned tasks are a bottleneck Potentially large team size Teams of 3 – 9 people Multiple phases, eventual delivery Working software each Sprint Resistant to change Change is expected Contract says what we build, deliver Contract is a lot closer to Time & Estimate
  8. 8. Project Results by style. The CHAOS Manifesto, Copyright 2011
  9. 9. WATERFALL TEAM SCRUM TEAM
  10. 10. Scrum Framework Roles: Product Owner, Scrum Master, Team Ceremonies: Spring planning, Spring review, Sprint retrospective, Daily Scrum Meeting Artifacts: Product backlog, Spring backlog, Burndown Chart
  11. 11. Scrum Framework x-Week Sprint
  12. 12. How scrum works
  13. 13. How scrum works Potentially shippable product after each sprint
  14. 14. Product Owner • Voice of actual customer • Owns the prioritized list of requirements (Product Backlog) • Available to the team at all times • Participates in sprint planning and review meetings • Responsible for product vision, ROI and release management
  15. 15. Scrum Team • Teams of 7 +/- 2 participants (max • • • 15) Cross functional Best experts in the domain area Self-organizing • • Team decides who shall do what They inspect and adapt as the sprint goes along • Have most of the powers during a sprint
  16. 16. Scrum Master • Facilitator • Protects the team • Removes impediments to the ability of the team • Not the leader of team (Team is self organizing) • Ensures the Scrum process is used as intended • Responsible for Daily Scrum • Coaches the team Does everything to help the team achieve the sprint deliverables
  17. 17. Product Backlog • An ordered list of prioritized items • Items: Stories, features, defects, tasks • Used for release planning and Iteration planning • Highest priority Items are picked first
  18. 18. Sprint Planning Meeting 1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization. 2. Team determines how much time it has available to commit during the Sprint 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 Validates commitment by breaking down into tasks with time estimates − Team decides who will do what, when; thinks through sequencing, dependencies, possible task trades, and so forth. −
  19. 19. Daily Scrum Meeting • Must not last more than 15 minutes • Held same place, same time, every working day • Anybody can come, but only the team can speak 3 questions: −What did I do yesterday? −What am I going to do today? −What are my impediments?
  20. 20. Review/Sprint Demo Team presents the working demo.  What have we achieved?  Should show finished functionality.  What is missing.  Maximum of 2 hours for presentation.
  21. 21. Retrospective • Facilitated by Scrum Master • To increase productivity and • Team reflects on sprint experience and comes up with suggestions.  What went well?  What did not go so well?  How can we improve?
  22. 22. Burndown chart • A graphical representation of work left to • • do vs. time Work remaining is the Y axis and time is the X axis. Useful to predict when all of the work would complete  Release burndown chart  Sprint burndown chart
  23. 23. Ball Point game A quick way to learn and experience agile/scrum
  24. 24. Rules of the game… 1. Everyone is on the same team Estimate throughput (#balls) prior to each sprint 2. Each person must contact each object during each round 3. Each world must have “air time” 4. No passes to your direct neighbor 5. Start point = End point Defects (balls dropped) do not count towards DONE unless reworked 5 iterations/sprints • Duration = 60 seconds • 3 minute retrospectives • Chart estimates vs. actuals Start in this formation:
  25. 25. Why we might fail using scrum? • Hard! • Scrum does not fix everything • Scrum makes problems visible - early • Ready for a change? • It makes Products to be delivered faster • Customized/partial Scrum
  26. 26. Summary • • • • • Everything is time-boxed. • • • • Iterative incremental development. Inspect & Adapt. You can-not plan everything. Fail early. Shippable product at the end of every iteration/sprint. Cross-functional teams. Self-organizing teams. Team owns the sprint backlog.
  27. 27. Where Scrum is used? Yahoo US Federal Reserve Sun SAP Siemens HP Nokia Motorola Philips TransUnion BBC Google IBM Microsoft
  28. 28. Thank You Questions?

×