The document discusses migrating to an agile approach for software development. It outlines characteristics of software and heuristics for building software, such as automating repetitive tasks and getting feedback through use. It recommends starting small with agile practices to address pain points and evolving practices over time. Core agile values include communication, simplicity, feedback, and courage. Specific agile practices mentioned include planning games, small releases, testing, refactoring, pair programming, collective ownership, continuous integration, and on-site customers. The document argues that an agile approach leverages the nature of software development and aligns with development realities.

1. Migration to Agile
Anand Joglekar
ThoughtWorks

2. Software Characteristics
• Intangible
• Mutable
• Very difficult to define and design
• Easy to construct
• Extensively testable
• Can be deployed with partial functionality

3. Heuristics for building software
• Automate everything that is repetitive
• Avoid duplication – functionality / process
• Test aggressively
• Get feedback from actual use
• implement in a minimal, simple way
• Evolve as per needs, as seen at runtime
• Build in small increments

4. How to go agile
1. Start small, watch benefit
2. Spot the pain
3. Bring in practices to relieve the pain
4. When it is not the biggest pain, repeat 2

5. Agile values
• Communication
• Simplicity
• Feedback
• Courage

6. Agile practices - i
• The planning game
• Small releases
• Metaphor
• Simple design
• Testing
• Refactoring

7. Agile practices - ii
• Pair programming
• Collective ownership
• Continuous integration
• 40-hour week
• On-site customer
• Coding standards

8. Frequent
Releases Enables
Enables
Allows
Allows
Produces
Produces
Customer
Continuous
Refactoring Involvement
Integration Simple Design
Triggers Allows Allows Enables
Triggers Allows Allows Enables
TDD
Enables
Enables
Adaptive Planning
Methods
Empowered Collective
Automated
Teams Ownership
Testing
Allows
Allows
Requires
Requires
Allows
Allows
Minimal
Documentation

9. Recap
• A good way of leveraging the special
characteristics of software.
• Aligns with the reality of development.
• Agile way of implementing agile.

10. Questions