Scrum group7 20120213


Published on

Presentation about Scrum Agile software development framework for Group7, Caballero Fabriek Den Haag, 13 February 2012

Published in: Technology, Business

Scrum group7 20120213

  1. 1. SCRUM Agile software development framework Carel Aeijelts Averink Online Project/Program Manager Blue Chip Consulting©
  2. 2. Introduction©
  3. 3. Projects using Scrum Organizations Media & Industries Government Advertising Telecommunications Websites Program Manager Program Manager Roles ScrumMaster Online Marketing Online Content management, eCommerce, online Content, search, SEO, Key elements open standards, sales, conversion high volume traffic accessibility Distributed Scrum team Distributed Scrum In-house Scrum teams (Veenendaal) teams (Denver, Vienna) Scrum Local Product Owner Corporate Product Local Product Owner Owner©
  4. 4. Roots of Scrum Total Quality Control, W.Edwards Deming Scrum Just in Time, Lean, Kanban©
  5. 5. Definition of Scrum • Scrum is not a • Scrum is an open methodology development framework with a simple set of rules • Scrum is not a defined • It has been used to manage process complex product develop- ment since the early 1990s • Scrum is not a set of • Ken Schwaber and Jeff procedures Sutherland developed Scrum The Scrum Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together©
  6. 6. Empirical Process Control The defined process control The empirical process control model requires that every model asserts that knowledge piece of work be completely comes from experience and understood. Given a well- making decisions based on what defined set of inputs, the is known. Scrum employs an same outputs are generated iterative, incremental approach every time. to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, adaptation©
  7. 7. Scrum vs. Waterfall Waterfall Scrum Fixed Scope & Time Fixed Time & Resources Release Planning Central planning, Sprint Planning Gantt Chart Daily Scrum Change Management Backlog Prioritization Centrally coordinated teams Self organizing teams Specialized teams (functional silo’s) Interdisciplinary teams Documentation Communication©
  8. 8. Scrum Static Model 3 Roles 5 Events 3 Artifacts Product Owner The Sprint Product Backlog Development Team Sprint Planning Meeting Sprint Backlog ScrumMaster Daily Scrum (stand-up) Increment Sprint Review (demo) Sprint Retrospective Optional Events Release Planning Backlog Grooming Scrum of Scrums©
  9. 9. Scrum Dynamic Model [1]© BlueChipConsulting.nlSource:
  10. 10. Scrum Dynamic Model [2] This defines what must be completed before and after a sprint • Analysis • Design • Development • Testing READY and DONE • Deployment ©
  11. 11. Requirements Product OwnerSource:©
  12. 12. User Stories As a .… [product user], I want …. [product feature], So that I can …. [benefit/purpose]. • Acceptance criteria • Designs • Story points©
  13. 13. Estimation Estimate on Units Range Precision T-shirt sizes S-XXL Epics Complexity or low Story Points* 40-100* User Stories Complexity Story Points* 0-20* good Tasks Effort Hours 2-6 hours high *Story Points are estimated by the Team in Planning Poker Source:©
  14. 14. Scrum (Task) Board Source: Source:©
  15. 15. Burndown Chart Predict Monitor Improve Learn©
  16. 16. The Team© Source:
  17. 17. ScrumMaster© BlueChipConsulting.nlScrumM movie
  18. 18. Product Owner © BlueChipConsulting.nlSource:
  19. 19. Distributed ScrumSource: ©
  20. 20. Business Cases Case 1: Improve the process Average website development Release cycle: 46 days. Distributed Scrum by 3rd party vendor: 24 days. PRODUCTION SCRUM SPRINTS BAT DEPLOYMENT4 days 18 days 2 days 10 days 12 days Average 18 days contributed to Average 10 days for Average 12 days for software development velocity Business Acceptance Deployment & Stage & Regression Testing Regression TestingREADY DONE Potentially Shippable In Production ©
  21. 21. Points of Attention • Documentation • Management buy-in/commitment • Cultural aspects • Risk Management • Release Planning • Fixed Price©
  22. 22. Release Planning “Any Product Manager that has successfully delivered a product to a customer knows how incredibly important Release Planning is. Despite its importance, the 2011 Scrum Guide, published in July by Ken Schwaber and Jeff Sutherland, removes any discussion about Release Planning and the related Release Burndown chart.” From©
  23. 23. Fixed Price “Money for nothing and your change for free”©
  24. 24. Greenhopper (JIRA/Atlassian)©
  25. 25. Links Scrum training • Jeff Sutherland • Ken Schwaber • Mike Cohn Scrum certification Scrum User Group Netherlands©
  26. 26. Contact @carel©