Page 0: Page 1: Scrum Agile for Everyone Page 2: Typical Software Development Process Page 3: Requirements Design Implementation Testing Deployment Maintenance Page 4: Requirements Changes Design Implementation Takes too long Testing Skipped Deployment Dreaded Maintenance Page 5: Na lly ra tu Chaos! Page 6: Accept Reality. Page 7: Control Chaos. Page 8: Control Chaos. ^ M ge na a Page 9: How? Page 10: Scrum. Page 11: Page 12: A light-weight agile project management toolkit. Page 13: People Things Behaviors Page 14: People Page 15: Page 16: Product Owner Scrum Master Scrum Team Page 17: Things Page 18: Things we want to do. Page 19: The product. Page 20: The product is described as a list of features: the backlog. Page 21: Backlog Page 22: The features are described in terms of user stories. Page 23: The scrum team estimates the work associated with each story. Page 24: Features in the backlog are ranked in order of importance. Page 25: Result: a ranked and weighted list of product features, a roadmap. Page 26: The product owner owns the product backlog. Page 27: Scrum People ‣ Product Owner ‣ Scrum Master ‣ Scrum Team Things ‣ Product Backlog ‣ Stories ‣ Estimates Page 28: Behaviors Page 29: Requirements Changes Design Implementation Takes too long Testing Skipped Deployment Dreaded Maintenance Page 30: Requirements Design Maintenance Implementation Deployment Testing Page 31: Page 32: Why Iterative? Page 33: Prototype leads to Product. Page 34: Rapid Feedback. Page 35: Reduced Risk. Page 36: Iterations = Sprints 2 - 4 Weeks Page 37: Scrum Sprint Cycle Daily Sprint Meeting Product Backlog Sprint 2 - 4 weeks Deliverable Sprint Backlog Page 38: Each sprint has very specific, measurable, attainable goals. Page 39: Sprints start with a planning meeting. Sprints end with a retrospective. Page 40: At the planning meeting, we commit to an amount of work. Page 41: We make cursory plans and assignments. Page 42: Sprint Runway Take off In Flight Landing Page 43: Sprint Runway Take off In Flight Landing Page 44: Sprint Runway Take off In Flight Landing Page 45: Sprint Runway Take off In Flight Landing Page 46: Each day we have a daily scrum meeting. Page 47: 1. What did you do? 2. Any obstacles? 3. What will you do? Page 48: Behaviors Page 49: Scrum Sprint Cycle Daily Sprint Meeting Product Backlog Sprint 2 - 4 weeks Deliverable Sprint Backlog Page 50: Sprints Planning Meeting Retrospective Daily Meetings Page 51: Why Scrum? Page 52: It's simple. Page 53: It's un-opinionated. Page 54: It provides clear measures. Page 55: Each story is estimated. Page 56: Over time, we can improve estimates and notice trends. Page 57: Burn-down and Velocity. Page 58: Keeps team focused. Page 59: Maintains flexibility. Page 60: How do we start? Page 61: 1. Committed people. 2. Create product backlog. 3. Start iterating. Page 62: It can take several sprints before it feels natural. Page 63: Don't get stuck in process. Page 64: Don't get stuck in meetings. Page 65: Don't thrash the backlog. Page 66: Do keep trying. Page 67: Scrum http://infoq.com/books/scrum-checklists J. Aaron Farr www.cubiclemuses.com farra@apache.org Page 68: