1. Agile Tooling Agile Mëtteg–November the 11th 2010

2. OBJECTIVES & AGENDA Objectives Get a short introduction to agile tooling, and where it sits next to agile methods and practices Agenda Agility and Quality Tools contribution to Agile software development Tools in the Agile IT (Examples) 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 Practitioner Lean/Kanban, Devops

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. AGILITY AND QUALITY 14 October 2010 Agile Mëtteg - The Customer role in agile 7

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

9. Meet the FUD 14 October 2010 9 Agile Mëtteg - The Customer role in agile Fear, Uncertainty and Doubt

10. Quality strikes back! 14 October 2010 10 Agile Mëtteg - The Customer role in agile Quality is the best answer to FUD Deliver quality items faster than before Win trust Easier said than done?

11. 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 11

12. Which quality and how to measure it? 14 October 2010 12 Agile Mëtteg - The Customer role in agile Agile is about adding Value Giving value to a customer for a product Contributing to a value stream Focusing on value Enforces removal of impediments Makes evaluation obvious from clients to I.T. teams to Management Gives shared quality goals for everybody

13. In the meantime… 14 October 2010 13 Agile Mëtteg - The Customer role in agile Many people won’t see things this way Non Agile boundaries exist: Audit constraints Input from non-agile teams Output to non-agile teams And moreover: Agile doesn’t mean messy nor improvised development Agile doesn’t mean costless development Agile means focus on value

14. So where does quality sit? 14 October 2010 14 Agile Mëtteg - The Customer role in agile Delivered features (value) must be target constant and (very) high quality

15. Trust is a key asset to Agility adoption 14 October 2010 15 Agile Mëtteg - The Customer role in agile If people trust Agile teams/initiative, adoption is (of course) easier

16. Tools contribution to Agile SDLC 14 October 2010 Agile Mëtteg - The Customer role in agile 16

17. 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 17 Source: http://www.agilemanifesto.org/

18. 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 18 Source: http://www.agilemanifesto.org/

19. 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 19

20. EXTRACT FROM THE 12 PRINCIPLES Satisfy the customer through early and continuous delivery of valuable software. Deliver working software frequentlywith 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 20

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

22. Tools Everywhere A Whiteboard/KanbanAND a good ticketing system 14 October 2010 Agile Mëtteg - The Customer role in agile 22

23. Tools Everywhere Frequent delivery AND Continuous Integration to enforce and ease this delivery 14 October 2010 Agile Mëtteg - The Customer role in agile 23

24. Tools Everywhere TDD AND Testing frameworks, Collaboration tools for User Acceptance Tests Good IDEs/Editors for Efficient Refactoring Good code analysis for fast error analysis 14 October 2010 Agile Mëtteg - The Customer role in agile 24

25. Tools to improve your process Tools in an Agile project/context are not focused on nor chosen for their compatibility with a predefined process Tools should adapt to your needs and assist you in improvements of your process Development process Testing process Validation process Release process 14 October 2010 Agile Mëtteg - The Customer role in agile 25

26. Tools to augment your focus Tools should help you improve quality, by removing boiler-plate and helping you focus on Value Tools should evolve constantly with your process 14 October 2010 Agile Mëtteg - The Customer role in agile 26

27. TOOLS IN THE AGILE I.T. 14 October 2010 Agile Mëtteg - The Customer role in agile 27

28. More than just projects SDLC (Software Development Life-Cycle) expands to more than a development team How do Agile tools help with customer interaction? How does Agility integrate with (for example) ITIL? How can Agility ease interaction with operations? 14 October 2010 Agile Mëtteg - The Customer role in agile 28

29. 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 29

30. 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 30

31. Customer-focused Agile Tools Transparency and collaboration tools WIKI DSLs (Ubiquitous language) Wallboards or Equivalent virtual Dashboards 14 October 2010 Agile Mëtteg - The Customer role in agile 31

32. ITIL and Agility ITIL, as many frameworks and methods, comes with methods and tools (remember the manifesto?) ITIL should be considered a good grammar, though it doesn’t provide value by itself Value should still be the main goal, and ITIL a shared vocabulary/tool to achieve it This is true for any other (imposed) classic framework or method 14 October 2010 Agile Mëtteg - The Customer role in agile 32

33. Operations and Agility A new trend: Dev/ops Limit between development and operations blurrier every day Cloud and virtualization are helping this frequent releases have their impact End-to-end Delivery quality attempted very early, and therefore achieved very early! Failure is allowed, though quality and tooling ensure easy fixes (reverting to former version in a click…) 14 October 2010 Agile Mëtteg - The Customer role in agile 33

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

35. Tools shouldn’t get in the way Everything that disallows providing more value with more quality faster should be considered an impediment This is also true for tools. 14 October 2010 Agile Mëtteg - The Customer role in agile 35

36. Tools should help improve the process Tools should be there to help and assist the process Tools should adapt to process improvements or be abandoned Tools should not drive the process, people and value (stream) should 14 October 2010 Agile Mëtteg - The Customer role in agile 36

37. TIME-TO-MARKET Sources: Mah 2008. Moutain Goat Software, LLC 14 October 2010 37 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 38 Agile Mëtteg - The Customer role in agile

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

40. QUESTIONS 40 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 41

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 42 Agile Mëtteg - The Customer role in agile

43. NEXT TRAININGS & CERTIFICATIONS 14 October 2010 Agile Mëtteg - The Customer role in agile 43 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 44

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

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

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 47

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 48

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 49

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