Introduction to Agile Methodologies and Concepts

1
Introduction to Agile Methodologies and Concepts

• Roy Osherove
• Principal, Team Agile
• www.TeamAgile.com
• Blog ISerializable.com

2
Methodology

• Code and fix (long test/debug phase)
• Methodology (more predictable, efficient)
• Detailed process, big on planning
• Engineering methodologies
• Successful? popular? criticized?
• Lightweight methodologies (agile)

Process
Cowboy
Agile
3
Agile properties

• Engineering
• Predictive
• Process-Oriented

• Agile
• Adaptive
• People-Oriented

4
Predictive vs. adaptive

• Separation of Design and Construction
• Comparative cost
• The Unpredictability of Requirements
• Is Predictability Impossible?
• Pretending
• Controlling an unpredictable Process

5
Comparative Cost

6
Predictive vs. adaptive (2)

• The Adaptive Customer
• Different relationship
• Fixed price?
• Needs stable requirements (predictive)
• Customer loses more even if 0 paid
• Success On time on cost
• Can fix time budget, but not scope
• Finer grained control by the customer
• Responsive development
• Visibility (manage risks early)
• Success Customer value gt cost

7
Putting People First

• Plug Compatible Programming Units
• Predictable process requires predictable parts
• Good with machines bad with people
• Careful what you wish for
• Programmers are Responsible Professionals
• Managing a People Oriented Process
• Accepting the process
• Equal part for management and team

8
Putting people first (2)

• The Difficulty of Measurement
• Measurement based management is good for simple
  things
• We cant measure software
• Delegatory management
• The Role of Business Leadership
• Teams need contact with business expertise
  (customer)
• Not occasional communication, but constant
• The self adaptive process

9
The Methodologies

• XP
• The Crystal family
• MSF- Agile
• Highsmith's ASD (Adaptive Software Development)
• Scrum
• Feature Driven Development
• DSDM (Dynamic Systems Development Method)
• Rational Unified Process? (dX)

10
The Agile Manifesto

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
• That is, while there is value in the items on
  the right, we value the items on the left more.

11
Stepping towards Agile Development

• Daily Stand Up Meetings
• Daily Build (CI)
• Unit Testing ( TDD?)
• Customer Testing
• Mixed Teams
• Smaller Iterations

12
What is XP?

• A brief introduction
• Communication, Simplicity
• Feedback, Courage

13
When to use XP

• dynamically changing requirements
• Risky projects
• Small dev groups (up to 100)
• Non-fixed scope(price) contract

14
Simple rules and practices

• Planning
• Release Planning
• Iterations Planning
• User Stories
• Small Releases
• Measure Project Velocity
• Move People around
• Stand up meeting

• Designing
• Simplicity
• System Metaphor
• CRC cards
• Spike solutions
• YAGNI
• Refactor

15
Simple rules and practices

• Coding
• Customer available
• Code standards
• Test-Driven
• Pair Programming
• Sequential change integration
• Integrate often
• Collective code ownership
• Dont optimize early
• No overtime

• Testing
• Unit test everything
• All tests pass before release
• Bug new test
• Acceptance tests

16
The XP lifecycle
17
Questions?
18
Thank You!

• Roy_at_TeamAgile.com
• www.TeamAgile.com