Baby Steps To Agility


Published on

Agile software development methodology is sweeping the IT Industry. Many organizations are experimenting with Agility and there are many “brands” of Agile including Scrum, XP, Lean, Crystal Clear and DSDM. Adoption of one of these methodologies could be wholesale in the case of a small well defined project that has no dependencies on other projects and can be completely delivered by a trained and motivated team. As these types of adoptions are rare organizations are looking for ways to ease into Agile practices without losing productivity.

This session is designed to discuss and identify ways that agile enablers can facilitate the transition to Agile practices. Participants learn basic Agile practices as well as techniques for introducing them to the software delivery team. This session will present common software delivery problems and the Agile path to solutions.

Published in: Technology, Business
1 Comment
  • I love this because my company will start agile development next year. It's great to see this.
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Baby Steps To Agility

  1. 1. Baby Steps to Agility<br />How to Grow Into Agile <br />
  2. 2. Goals<br />A little about me<br />A little about Agile<br />Growing into Agile<br />Questions<br />
  3. 3. About me<br />I want to deliver great software.<br />Almost 20 years experience in software<br />Experience managing a 200+ person program<br />Using Agile Methods since 2000.<br />Agile is a better way.<br />
  4. 4. The Agile Manifesto<br />Agile Prefers<br />Individuals and interactions<br />Working Software<br />Customer collaboration<br />Responding to change<br />Over<br />Processes and tools<br />Comprehensive documentation<br />Contract negotiation<br />Following the plan<br />
  5. 5. 12 Agile Principles<br />Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer&apos;s competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Business people and developers must work together daily throughout the project.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />Working software is the primary measure of progress.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Continuous attention to technical excellence and good design enhances agility.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  6. 6. Sitting up – Why Change?<br />Starting to Crawl - Pick Change<br />First Steps - Team focus and “buy-in”<br />Speaking in Sentences - Agile Reporting<br />Patience – Continuing to Change<br />Practice Development Milestones<br />
  7. 7. Define the current state<br />Identify the problems<br />Write down the reasons for Change<br />Sitting Up<br />
  8. 8. Product Company<br />Patches and Upgrades<br />Internal IT<br />Point Solutions<br />Professional Services<br />Working Software Quickly<br />How Does “The Business” Work<br />
  9. 9. We don’t know when we are done.<br />We test functionality and it is not working in the build we give to the customer.<br />Our customer is constantly changing his mind.<br />How is this software supporting “the business”?<br />Some Problems<br />
  10. 10. We are only going to work on things that are important to our customers.<br />We can guarantee delivery of the product on time with known quality.<br />We can clearly define what is in a release and what is not in a release.<br />We can report the outcome of our testing to a customer.<br />We can deliver important customer issues outside of a release.<br />How is this going to help us?<br />
  11. 11. <ul><li>Build of the system that includes installation packages and automated test.
  12. 12. Iterative process for delivering.
  13. 13. Complete Tickets</li></ul>Starting to Crawl<br />
  14. 14. <ul><li>Build
  15. 15. Test
  16. 16. Report</li></ul>What does the Build look like? <br />
  17. 17. What does Iterative Development look like?<br />
  18. 18. When is a Ticket Done<br />Replication of the issue or Requirements<br />Analysis and Review of Solution<br />Test Cases<br />Unit test<br />Implementation<br />Code Review<br />Verification<br />Documentation<br />Release for System Integration.<br />
  19. 19. Have the Team Define Solution<br />Spend Time in a Dark Room with Power Point<br />Close the Feedback Loop<br />First Steps<br />
  20. 20. Ticket process as defined by Team<br />
  21. 21. What is Agile Development?<br />Agile is a broad set of principles for delivering software<br />Agile is based on the concept of teams delivering software where the business people are part of that team.<br />The same principals of ISO Standards and CMM are captured in Agile development practices.<br />
  22. 22. What Agile is not.<br />Agile is not a rigid set of instructions.<br />Agile is not a silver bullet.<br />Agile is not anti-documentation.<br />
  23. 23. Team Retrospective<br />Management Retrospective<br />Reporting on Actions<br />Circle the Ideas<br />
  24. 24. Agile Performance Indicators<br />Define a Point<br />Quality<br />Speaking in Sentences<br />
  25. 25. Velocity – How fast are we going?<br />Capacity – How much can we do?<br />Burn up / down - When are we going to finish?<br />Backlog – How much is there to do?<br />Burn rate – How much does it cost?<br />Progress – How are we doing on initiatives?<br />Agile Performance Indicators<br />
  26. 26. Define a Point<br />
  27. 27. Quality Pyramid<br />
  28. 28. Patience<br />
  29. 29. Questions<br />