Agile Software Development
How to build a Death Star without being
squished by Darth Vader
Reinhart De Lille
• Something short about Adifo
• Prelude (to pain)
• Classical software development
• Going Agile with Scrum
Adifo in figures
75 employees, 700 customers
Turnover: + 8 million EUR
Export (world-wide): 80%
Customers in more than 60 countries
Turnover Adifo 2011
NL, D, Fr
• Software development is more than coding
• And always involves a lot of people
It is a team effort
To build a software product
That effectively solves a customer’s problem
And gives value to his business
Have a real world problem and make your
computer deal with it
Product Managers / consultants :
Get requirements from customer and market
Make requirements consistent
Architects / Developers
Code the requirements
Write unit tests
Testers / System engineers / etc ...
A real world example
• Failure and a typical customer response
How to deal with this?
• Introducing SW development methodologies
– And we call it Project Management !
• 2 approaches
– Classical : try to make sure we know everything in
– Agile : build the software incrementally and evolve
with the customer specs.
Try to make sure we know everything in advance!
Interview customer till you know last details
Analyse and estimate it from top to bottom
Fix the budget together with customer
And then build the bugger
– Waterfall / CODIS / Rational Unified Process
• Typically used
– Large engineering projects, NASA, government projects, etc ...
– Or building a death star ...
Reality check ! There is a dark side to every project!
What does the customer need?
I want more whistles & bells !
... And now you do what they told ya !
no responsibilities ...
Very very expensive? Out of budget and
out of time?
The world changes faster than the
• How to deal with such crisis ?
• Take the project management challenges for
• Embrace the ever-changing nature of
• Take responsibility for what you can manage
• And deal with issues as they come
Aka Incremental software development
Don’t do a big bang, but
Do iterations of ‘small bangs’
Be deliverable after each iteration
In a self-organising, cross functional team
• Many methodologies
Feature driven Development
• Some very simple concepts
• Self managing Team
• Keep it visual !
• Keep learning !
Scrum 15 minute daily meeting
Teams member respond to basics:
What did you do since last
Do you have any obstacles?
What will you do before
New functionality is
end of sprint
Prioritized product features desired by the customer
The Product Backlog Iceberg