Baby Steps To Agility

Uploaded 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 …

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.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • I love this because my company will start agile development next year. It's great to see this.
    Are you sure you want to
    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

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Baby Steps to Agility
    How to Grow Into Agile
  • 2. Goals
    A little about me
    A little about Agile
    Growing into Agile
  • 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
    Individuals and interactions
    Working Software
    Customer collaboration
    Responding to change
    Processes and tools
    Comprehensive documentation
    Contract negotiation
    Following the plan
  • 5. 12 Agile Principles
    Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software.
    Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
    Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
    Business people and developers must work together daily throughout the project.
    Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
    The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
    Working software is the primary measure of progress.
    Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
    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.
  • 6. 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
  • 7. Define the current state
    Identify the problems
    Write down the reasons for Change
    Sitting Up
  • 8. Product Company
    Patches and Upgrades
    Internal IT
    Point Solutions
    Professional Services
    Working Software Quickly
    How Does “The Business” Work
  • 9. 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
  • 10. We are only going to work on things that are important to our customers.
    We can guarantee delivery of the product on time with known quality.
    We can clearly define what is in a release and what is not in a release.
    We can report the outcome of our testing to a customer.
    We can deliver important customer issues outside of a release.
    How is this going to help us?
  • 11.
    • Build of the system that includes installation packages and automated test.
    • 12. Iterative process for delivering.
    • 13. Complete Tickets
    Starting to Crawl
  • 14. What does the Build look like?
  • 17. What does Iterative Development look like?
  • 18. When is a Ticket Done
    Replication of the issue or Requirements
    Analysis and Review of Solution
    Test Cases
    Unit test
    Code Review
    Release for System Integration.
  • 19. Have the Team Define Solution
    Spend Time in a Dark Room with Power Point
    Close the Feedback Loop
    First Steps
  • 20. Ticket process as defined by Team
  • 21. What is Agile Development?
    Agile is a broad set of principles for delivering software
    Agile is based on the concept of teams delivering software where the business people are part of that team.
    The same principals of ISO Standards and CMM are captured in Agile development practices.
  • 22. What Agile is not.
    Agile is not a rigid set of instructions.
    Agile is not a silver bullet.
    Agile is not anti-documentation.
  • 23. Team Retrospective
    Management Retrospective
    Reporting on Actions
    Circle the Ideas
  • 24. Agile Performance Indicators
    Define a Point
    Speaking in Sentences
  • 25. 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
  • 26. Define a Point
  • 27. Quality Pyramid
  • 28. Patience
  • 29. Questions