The Customer role in agile projects 14 October 2010

1. The Customer role in agile projects Agile Mëtteg – 14 October 2010

2. OBJECTIVES & AGENDA Objectives Get a short introduction to agile and the implications and benefits of an agile transition from the customer point of view. Agenda Introduction Main issues Agile Project management overview Agile management of requirements Guidelines for success The Product Owner role To conclude 14 October 2010 2 Agile Mëtteg - The Customer role in agile

3. Let’s get to know each other 14 October 2010 Agile Mëtteg - The Customer role in agile 3

4. AGILE PARTNER SERVICES Custom Software Development & Maintenance Our core business to answer customer needs IS services Thanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…) IS Solutions Take benefit from commercial or Open Source platform to answer as quick as possible to specific needs IS users services We can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…) 14 October 2010 Agile Mëtteg - The Customer role in agile 4 IS users Services 1 4 Software Development & SoftwareMaintenance 2 ISSolutions IS Services Agility Agility 3 1 2 3 4 Agility

5. SPEAKERS 14 October 2010 Agile Mëtteg - The Customer role in agile 5 Agile Evangelists

6. PARTICIPANTS Who are you? What is your role? What do you know about agility? What are your expectations? 14 October 2010 6 Agile Mëtteg - The Customer role in agile

7. MAIN ISSUES 14 October 2010 Agile Mëtteg - The Customer role in agile 7

8. COMPLETE UPFRONT SPECIFICATIONS 14 October 2010 Agile Mëtteg - The Customer role in agile 8 Sources : J.Johnson, Keynote speech, XP 2002 Italie

10. AGILE PROJECT MANAGEMENTTHE PRINCIPLES 14 October 2010 Agile Mëtteg - The Customer role in agile 10

11. ADAPTATION vs. ANTICIPATION Source: Succeeding with Agile: Software Development using Scrum, Mike Cohn , Addison-Wesley, 2009 14 October 2010 11 Agile Mëtteg - The Customer role in agile

12. THE 4 VALUES Extract from Manifesto for Agile Software Development: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 14 October 2010 Agile Mëtteg - The Customer role in agile 12 Source: http://www.agilemanifesto.org/

13. EXTRACT FROM THE 12 PRINCIPLES Satisfy the customer through early and continuous delivery of valuable software. Deliver working software frequently with a preference to the shorter timescale. Simplicity--the art of maximizing the amount of work not done--is essential. Business people and developers must work together daily throughout the project. Face-to-face conversation for conveying information to and within a development team. 14 October 2010 Agile Mëtteg - The Customer role in agile 13

14. AGILE PROCESS 14 October 2010 Agile Mëtteg - The Customer role in agile 14 Needs System in progress Iterations Priority Iterative and incremental process Adaptive planning Iterations time-boxed

15. AGILE Management OF the requirements 14 October 2010 Agile Mëtteg - The Customer role in agile 15

16. PRINCIPLE Just-In-Time, Just-enough Requirements 14 October 2010 Agile Mëtteg - The Customer role in agile 16

17. GUIDELINES FOR SUCCESS 14 October 2010 Agile Mëtteg - The Customer role in agile 17

18. PRINCIPLE Team-Customer Collaboration 14 October 2010 Agile Mëtteg - The Customer role in agile 18

19. OBJECTIVES Build knowledge Build a solution that fits the real needs Optimize delivered value Build trust relationship 14 October 2010 Agile Mëtteg - The Customer role in agile 19

20. BUILDING KNOWLEDGE Create a short feedback loop with users Deliver working software frequently Planning as a knowledge building activity Agree on a “Definition of done” Decompose, clarify and validate requirements for reaching a common understanding and allowing the team estimating the effort Iterations as Learning cycles Learn about the product expected features Learn about the best way to build it 14 October 2010 Agile Mëtteg - The Customer role in agile 20

21. THE CUSTOMER IS EXPECTED TO Evolve from Project to Product Management Elaborate and share a vision Manage product lifecycle with Releases Understand and communicate the requirements Evaluate business value Have the power and responsibility to decide Be available to collaborate with the team continuously Respect team capacity limit 14 October 2010 Agile Mëtteg - The Customer role in agile 21

22. THE CUSTOMER CAN EXPECT THE TEAM TO Estimate effort (on a relative scale) Commit for achieving short-term goals Build quality in Accept changes in requirements Improve continuously 14 October 2010 Agile Mëtteg - The Customer role in agile 22

23. BENEFITS Drive the development effort to optimize value under time and budget constraints 14 October 2010 Agile Mëtteg - The Customer role in agile 23

24. The Product Owner Role in SCRUM 14 October 2010 Agile Mëtteg - The Customer role in agile 24

25. SCRUM 14 October 2010 25 Agile Mëtteg - The Customer role in agile Team Scrum Master Review Sprint Planning Retrospective Product Owner

26. PRODUCT OWNER – ROLE SUMMARY Responsible for the Product Defines product vision and features Plans releases (dates and content) Prioritizes features according to market value Can change features and priority before every iteration Accepts or rejects work results Is responsible for the profitability of the product (ROI) 14 October 2010 Agile Mëtteg - The Customer role in agile 26

28. Update the Release plan

31. Collaborate with the team to communicate and clarify requirements

32. Groom the product backlog

34. USER STORY… A mean The 3 Cs 14 October 2010 Agile Mëtteg - The Customer role in agile 29 <Title> Card As a <role> I want to <do something> So that <goal> Confirmation Conversation Priority Effort estimation + acceptance criteria

35. OTHER MEANS & TOOLS 14 October 2010 Agile Mëtteg - The Customer role in agile 30 Indicators based on criteria Profitability (Cost, Revenue, Margin…) Market share Client satisfaction Enterprise image Innovation … Examples of values model KANO model Cost of delay model …

36. CONCLUSION 14 October 2010 Agile Mëtteg - The Customer role in agile 31

37. TIME-TO-MARKET Sources: Mah 2008. Moutain Goat Software, LLC 14 October 2010 32 Agile Mëtteg - The Customer role in agile

38. SALESFORCE.COM 568% more value delivered in the first year of being agile. Source: Greene and Fry 2008.Moutain Goat Software, LLC 14 October 2010 33 Agile Mëtteg - The Customer role in agile

39. SATISFACTION Source: VersionOne, 2008 State of Agile Development Survey 14 October 2010 34 Agile Mëtteg - The Customer role in agile

40. QUESTIONS 35 Agile Mëtteg - The Customer role in agile 14 October 2010 READY to TRY

41. TRAINING PATH Introduction (1 day) Agile Software Development Methods Scrum basics (2 days) Agile Project Management with Scrum Product Owner focus (2 days) Become a Scrum Product Owner In depth (3 days) Scrum in practice 14 October 2010 Agile Mëtteg - The Customer role in agile 36

42. CERTIFICATIONS Certifications are delivered by the Scrum Alliance. You need to attend a course and pass a test to be certified. 14 October 2010 37 Agile Mëtteg - The Customer role in agile

43. NEXT TRAININGS & CERTIFICATIONS 14 October 2010 Agile Mëtteg - The Customer role in agile 38 Complete calendar on: http://www.agilepartner.net/training/focus-on/

44. RESOURCES Agile Partner: www.agilepartner.net NEW!blog.agilepartner.net Agile Interest Group Luxembourg:www.aiglu.org Agile Alliance: www.agilealliance.org Scrum alliance: www.scrumalliance.org Scrum.org 14 October 2010 Agile Mëtteg - The Customer role in agile 39

45. CONTACTS Thank You 14 October 2010 Agile Mëtteg - The Customer role in agile 40

46. Resources 14 October 2010 Agile Mëtteg - The Customer role in agile 41

47. THE 12 PRINCIPLES (1/3) Satisfy the customer through early and continuous delivery of valuable software. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently with a preference to the shorter timescale. Working software is the primary measure of progress. 14 October 2010 Agile Mëtteg - The Customer role in agile 42

48. THE 12 PRINCIPLES (2/3) Business people and developers must work together daily throughout the project. Face-to-face conversation for conveying information to and within a development team. Build projects around motivated individuals. Sustainable pace for the sponsors, developers, and users. 14 October 2010 Agile Mëtteg - The Customer role in agile 43

49. THE 12 PRINCIPLES (3/3) Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 14 October 2010 Agile Mëtteg - The Customer role in agile 44

50. VARIOUS METHODS & PRACTICES 14 October 2010 Agile Mëtteg - The Customer role in agile 45