Scrum
•
28 likes•6,697 views
Scrum is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to complete user stories from a prioritized backlog. Daily stand-up meetings help coordinate work. At the end of each sprint, teams demonstrate completed work to stakeholders for feedback to improve subsequent sprints. Periodic retrospectives help teams improve their processes. Compared to traditional "waterfall" models, Scrum aims to handle changing requirements better through rapid iteration and continuous customer input.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Scrum
Similar to Scrum (20)
Recently uploaded
Recently uploaded (20)
Scrum
- 4. here
- 5. !! and
- 6. here
- 7. too
- 8. !! change
- 9. here
- 10. ?
- 11. Waterfail Pros: • Very logical • Think before you build • Follow a plan • Keep things organized Cons: Humans are involved !!
- 13. Good ideas come along the way
- 14. First time you touch the product, You immediately think of 20 ways to make it better
- 15. We are bad at predicting future
- 16. Use documents as main communication channel
- 18. Agile
- 19. • Get hands on quickly • cross-functional team empowered to make decision • rapid iteration / incremental • continuous customer input • Just do it ? ...not exactly Agile
- 20. Scrum
- 22. Scrum Roles
- 23. Product Owner
- 24. Product Owner • One person • Define features • Prioritizing list • Provide feedback • Accept/Reject results • ≈ Customer
- 25. The Team
- 26. The Team • provide ideas to PO on how to make product great • 7 ± 2 people • Cross-functional • Self-organizing
- 27. Scrum Master
- 28. Scrum Master • Help Team learn and apply Scrum • Does whatever to help Team PO • Should be full-time • Team member is ok but not PO
- 29. Product Owner Team Members Scrum Master Managers Users Marketing
- 30. Starting Scrum
- 31. Product Backlog • Value / Feature of product (High level) • describe as User Story • Owned by Product Owner • Estimated by Team • not perfect (expected to change)
- 32. Product Backlog
- 33. As a user I want functionality ( So that benefit )
- 34. As a librarian I want to be able to search for books by publication year So that I can keep track of books of certain year Search books byYear 8
- 35. Sprints
- 36. Sprints • Cycles of work • time-boxed • 1 - 4 weeks • never extended
- 37. Sprint Planning
- 38. Sprint Planning pt.1 • PO + Team + (SM) • High priority items on Product Backlog • Context + Def. of done • What PO wants
- 39. Sprint Planning pt.2 • Team + (PO + SM) • focus on the How • How much effort we have? • How many items we could do? • Sprint Backlog • Volunteer for one task at a time
- 40. Definition of Done • Introduce earlier • To avoid 90% syndrome • Usually physical / tangible • Works great with ex. TDD
- 41. Sprint Backlog
- 43. Daily Scrum
- 44. Daily Scrum What I did since last meeting? What I will do until next meeting? What things are in my way?
- 45. Daily Scrum • Only Team talks ( to coordinate only) • No problem solving ! • Max 15 mins .. so .. standup !
- 48. Low-tech / High touch
- 49. Product Backlog Refinement • lesser known but valuable • 5% of sprint time (Team + PO) • Req. analysis / Splitting items / (re)Estimation • Workshop near end of sprint • if not? Sprint Planning = confusion, discovery..
- 50. Ending Sprint
- 51. Sprint Review
- 52. Sprint Review • Needs preparation but informal • No slides • 1-2 hours/sprint/week • Show complete features • Accept or Reject
- 54. Sprint Retrospective What to Start doing What to Stop doing What to Continue doing
- 57. Sources • The Scrum Primer v1.2 (pdf) • The Zen of Scrum (Slideshare) Link: http://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10