XP a-real-case

eXtreme Programming: a real case.

Alessandro Chiarini

CINECA, Bologna, 24 giugno 2010

Copyright © SCS srl.

Alessandro [email protected]

Technical ManagerSCS

eXtreme Programming

� XP artisan

Team size: up to 20 members, 9 programmers� Team size: up to 20 members, 9 programmers

� Twofold development

� Visualization framework for biomedical application (MAF, C++)

� Community and collaborative services based on plone/zope software stack (python)


plone/zope software stack (python)

Development Methodologies

� A methodology is a formalized process or set of practices for creating softwarepractices for creating software

� A set of rules you have to follow

� A set of conventions the organization decides to follow

� A systematic, engineering approach for organizing software projects


software projects

Agile Manifesto

“Our highest priority is to satisfy the customer through early and continuous delivery of through early and continuous delivery of valuable software”

(taken from agilemanifesto.org)


The agile spirit

� Incremental

Working software ever comprehensive � Working software ever comprehensive documentation

� Cooperative

� Customer cooperation over contract negotiation

� Straightforward


� Individuals and interaction over processes and tools

� Adaptive

� Responding to change over following a plan

The team

� Customers

Application / Domain Experts� Application / Domain Experts

� Product manager

� Programmers

� Software architects

� Software developers


Software developers

� Testers

� Steerer

The XP cycle


(taken from extremeprogramming.org)

XP practices

� XP is about:

Team working� Team working

� Releasing

� Planning

� Developing


Team working

� Pair programming

Trust� Trust

� Customer Involvement

� Coding Standards

� Collective code ownership


Releasing

� “Done Done”

Version control� Version control

� Ten minutes build

� Continuous integration


Planning

� Release Planning

Iteration Planning� Iteration Planning

� Stories

� Estimating

� Velocity


Developing

� Simple design

Spike solutions� Spike solutions

� Incremental requirements

� Test Driven Development

� Customer tests

� Refactoring


Refactoring

Key values

� Communication

Simplicity� Simplicity

� Feedback

� Courage

� Respect


The Bug Life cycle

� Even if we adopt XP our code is not our code is not exempted by bugs

� Bugs should be fixedaccording the refactoring


refactoringpractice, where possible

(taken from mozilla.org)

SCS development infrastructure

� Project managing

Version control system (CVS, SVN)� Version control system (CVS, SVN)

� Distributed continuous build (parabuild)

� Automated testing

� Automated QA

Bug tracker


� Bug tracker

� Plone based web space for documentation/forums

Project management


Code repository


Continuous build


Automated testing

� Cppunit

Acceptance tests� Acceptance tests

� QA dashboard

� Memory leaks

� Coverage

� Coding style


� Coding style

� Automated GUI testing

Bug tracking


A success story

� Customer: imaging manufacturer who needed to present its new product at a fairto present its new product at a fair

� Time constraints (once-a-year event)

� Customer used to waterfall methods

� Many and complex functionalities

� XP helped us to:


� XP helped us to:

� respond promptly to customer's request changes

� release early valuable software

� Involve the customer in the development process

Conclusions

“Brilliant process management is our strategy. We get brilliant results from average people get brilliant results from average people managing brilliant processes. We observe that our competitors often get average (or worse) results from brilliant people managing broken processes.”

S. Toyoda


S. Toyoda

References

� Beck, Extreme Programming explained

Shore & Warden, The art of Agile Development� Shore & Warden, The art of Agile Development

� agilemanifesto.org

� extremeprogramming.org


Technology

XP a-real-case