1. Baby Steps to Agility How to Grow Into Agile

2. A little about me A little about Agile Growing into Agile Questions Goals

3. About me I want to deliver great software. Almost 20 years experience in software Experience managing a 200+ person program Using Agile Methods since 2000. Agile is a better way.

4. The Agile Manifesto Agile Prefers 1.Individuals and interactions 2.Working Software 3.Customer collaboration 4.Responding to change Over 1.Processes and tools 2.Comprehensive documentation 3.Contract negotiation 4.Following the plan

5. 12 Agile Principles - The first 6 1.Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2.Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3.Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4.Business people and developers must work together daily throughout the project. 5.Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

6. 1.Working software is the primary measure of progress. 2.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 3.Continuous attention to technical excellence and good design enhances agility. 4.Simplicity--the art of maximizing the amount of work not done--is essential. 5.The best architectures, requirements, and designs emerge from self-organizing teams. 6.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The other 6 Agile Principals

7. Sitting up – Why Change? Starting to Crawl - Pick Change First Steps - Team focus and “buy-in” Speaking in Sentences - Agile Reporting Patience – Continuing to Change Practice Development Milestones

8. Define the current state Identify the problems Write down the reasons for Change Sitting Up

9. Product Company –Patches and Upgrades Internal IT –Point Solutions Professional Services –Working Software Quickly How Does “The Business” Work

10. We don’t know when we are done. We test functionality and it is not working in the build we give to the customer. Our customer is constantly changing his mind. How is this software supporting “the business”? Some Problems

11. 1.We are only going to work on things that are important to our customers. 2.We can guarantee delivery of the product on time with known quality. 3.We can clearly define what is in a release and what is not in a release. 4.We can report the outcome of our testing to a customer. 5.We can deliver important customer issues outside of a release. How is Agile going to help us?

12. 1.Write the statement of your company’s goals in relation to software development. 2.Define problems in development 3.Using the 12 principles of Agile write 5 statements of how Agile will help achieve your goals and/or solve the development problems. (Great start for your slides for management) Exercise

13. Build of the system that includes installation packages and automated test. Iterative process for delivering. Complete Tickets Starting to Crawl

14. Build Test Report What does the Automated Build look like?

15. What does Iterative Development look like?

16. When is a Ticket Done Replication of the issue or Requirements Analysis and Review of Solution Test Cases Unit test Implementation Code Review Verification Documentation Release for System Integration.

17. Have the Team Define Solution Spend Time in a Dark Room with Power Point Close the Feedback Loop First Steps

18. Ticket process as defined by Team

19. What is Agile Development? 1.Agile is a broad set of principles for delivering software 2.Agile is based on the concept of teams delivering software where the business people are part of that team. 3.The same principals of ISO Standards and CMM are captured in Agile development practices.

20. What Agile is not. 1.Agile is not a rigid set of instructions. 2.Agile is not a silver bullet. 3.Agile is not anti-documentation.

21. Team Retrospective Management Retrospective Reporting on Actions Circle the Ideas

22. Retrospective Technique –Hot Air Balloon –Did Well, Did not so well, Do better next time –Start doing, stop doing, keep doing, more of, less of –Top 3 concerns (works well for management). Exercise

23. Agile Performance Indicators Define a Point Quality Speaking in Sentences

24. Velocity – How fast are we going? Capacity – How much can we do? Burn up / down - When are we going to finish? Backlog – How much is there to do? Burn rate – How much does it cost? Progress – How are we doing on initiatives? Agile Performance Indicators

25. Define a Point

26. Scope Tracking in Points Project Reference Baseline Last Week CurrentVarianceCompletedRemainingDeferredDeleted AG-458 123126.25 0124.25229111.5 AG- 216105116.5 0115.51421 AG - 487.2935961.75964.753486.754782193 AG - 487.3 670611.5617.56582.53514118.5 AG - 487.4398369.25 0311.25589102.5 Total22312185.252194.2591620.25574––

27. Quality Pyramid

28. Quality Statistics –What Bugs do WE have? –Can we catch them earlier? Exercise

29. Patience

30. Questions