eXtreme Programming Development

Adrian WilliamsonPeople, Technology and People and

Technology Consultant

• Why?• What?• Who?• When?• So what …• Summary

Real eXtreme Programming

• GT-X7 started in 1999

• 500,000 lines of Java by 2005

• Modular but not re-factored

• Tested but not TDD

Why? (1 of 2)

Neil decided to do something about it …

Why? (2 of 2)

Support 2004

Support 2005

Transformation required!

Stop the world I want to get off!

What? (1 of 9)

Read the books, browse the web

What? (2 of 9)

XP Practices

What? (3 of 9)

The Planning Process (Planning Game)XP "customer” defines business value of features, cost estimates from programmers.

MetaphorA common "system of names" and description that guides development.

Simple Design The simplest program for current requirements. Little building "for the future”.

TestingConstant Software Validation: Test Driven development; Customer acceptance tests.

Refactoring Keep software clean: without duplication, high communication, simple, yet complete.

Pair ProgrammingTwo programmers working together at one machine.

XP Practices

What? (4 of 9)

Collective OwnershipAll the code belongs to all the programmers. Changes without delay.

Continuous IntegrationXP teams integrate and build the software system multiple times per day.

40-hour Week Tired programmers make more mistakes. Stay fresh, healthy, and effective.

On-site CustomerThe dedicated individual empowered to set requirements, priorities, and answer questions.

Coding StandardAll the programmers need to write the code in the same way.

XP Principles - Fundamental

What? (5 of 9)

•Rapid Feedback

•Assume Simplicity

•Incremental Change

•Embracing Change

•Quality Work

XP Principles - Further

What? (6 of 9)

•Teach Learning•Small Initial Investment•Play to Win•Concrete Experiments•Open, honest Communication•Work with people's instincts•Accepted Responsibility•Local Adaptation•Travel Light•Honest Measurement

Phone the consultants

What? (7 of 9)

• Support costs• Lost development

opportunity• Product Quality• Company and Product image• Staff• Predictability• Method

Build a business case

What? (8 of 9)

Pilot.NET ciboodle Mobile Client

PrepareTrain team leadsWorkshops for team leads

Choose a dateTrain developers

Start!

Implementation Plan

What? (9 of 9)

• Business Quiet• Projects Quiet and Within

Envelope• Team Building Complete• Team Stable• Test Team Established• Support team LEAN Kaizen

September 2005!

Happenstance

When

eXtreme Programming

So What? (1 of 5)

September 2005!

So What? (2 of 5)

Planning6 week cycles

TeamsSupport, Core, Point, New Features, Strategic, Test, Docs

ReportingVelocities, test coverage, defect rates

Balanced ScorecardWaiting …

Operation

So What? (3 of 5)

BCS Awards 2006

• Best young developer medal– Mobile team

• Project medal – BASCO mobile livestock tracking

Prizes !!

So What? (4 of 5)

eXtreme Ironing!

So What? (5 of 5)

Thank You! - Any Questions?

Adrian Williamson