Learn how to combine Agile User Stories, Out Side-in Development, and Innovation Games to get the right product built for your customers. Presented to the IIBA 7/8/2007.

2. That’s not what I wanted! projectcartoon.com

4. Sound Familiar? Customers want it yesterday We spend more time fixing bugs than adding new features! They changed their mind! It wasn’t what they expected We planned, but were surprised

5. Our Goals Time to Market Quality Flexibility Customer Sat Risk Reduction

6. Aspects of Agile Leverage Change Scrum Optimize Lean Build the Right Thing User Stories, Innovation Games Bake in Quality Agile tech

7. Process, Specs, Plans?

15. A User Story As an online shopper, I can ship to a friend Ron Jefferies 3 ‘C’s Card Talk with Bob, my stakeholder We know we’re done when: [x] Can retrieve friend’s address [ ] Can specify ship date and carrier [ ] Can track order Conversation Confirmation 

16. R G B - Card details Role Goal (Benefit) As a student I can view the course materials online after class So I can review any points I missed As a teacher I can get feedback from students So I know if I should speed up, slow down, or repeat

19. Examples Front Back What’s missing? Hint: 3 Cs As an teacher, I want to be able to setup a learning management system So students can study outside of class Priority 5. Estimate 8 points [x] Students can register [ ] Students can chat on a message board [ ] Teachers can collect exercises [ ] Teachers can organize learning modules

20. Reinforce your learning Question Answer What are some of the three parts of a user story? What are the 3 parts of the ‘card’? (hint – think colors) A story is a _____ to future conversation What do we do with stories? (hint – think planning) Why don’t we give much space to write?

21. Answers! Question Answer What are some of the three parts of a user story? C ard C onversation C onfirmation What are the 3 parts of the ‘card’? (hint – think colors) Role , Goal , Benefit A story is a _____ to future conversation What do we do with stories? (hint – think planning) Prioritize, size Why don’t we give much space to write? To make you break them down into small stories So you focus on the acceptance test

26. Relationship to Agile Project Management

27. Scrum via Mike Cohn

29. The Product Backlog Continuous Flow of new Reqs Product Backlog Sorted by Product Owner Estimated by Team Sprint Backlog

31. Release Plan: an ordered pile of stories In Stretch Out Conservative Velocity * number of iterations At our best velocity Not in this release. Good to know now. Hot

32. Release Plan: an ordered pile of stories In Stretch Out Conservative Velocity * number of iterations At our best velocity Not in this release. Good to know now. Hot Continuous Prioritization of new stories

34. A day in the life of an Agile team Full Build Evening Afternoon Morning Task 10 Task 9 Task 8 Task 7 Task 6 Task 5 Task 4 Task 3 Task 2 Task 1 Scrum meeting (everyone)

35. A Two Week Sprint Fri Thu Wed Tue ‘ Mon’ Demo Retro Daily Daily Daily Daily Daily Daily Daily Daily Plan

36. A Release Glance at product vision to help in release planning Release Planning Sprint 6 Sprint 5 Mar June May Apr Sprint 6 Sprint 4 Sprint 2 Sprint 5 Sprint 3 Sprint 1

38. Shodan Retrospective Actions, not a score card Outer range shows high use Note diverse opinions in team

39. When do we know our true velocity?

40. A _____ A _ A _____ 1 3 5 __, __, __, 40 100 As a ______ I can _______ so that _______ C___ C______ C_____ P_______ I_______ P_______ E__ ____ by AgileBill Krebs. @AgileBill4d http://bit.ly/amagile Fist of _____ Agile in one page reference card (Quiz until you fill it out)  Done ____ Minutes I … I … My _____ Are … ‘ M’ T W T F ____ . . . . . . . . ____ ____