Intro
What is agile software development anyway?
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.
Agile principles
We follow these principles:
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development.
- The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity -the art of maximizing the amount of work not done- is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Key characteristics
De karakteristieken van agile software development:
- Een kleine eenheid van werk
- Prioriteren
- Korte iteraties
- Nauwe samenwerking
- Vroeg en vaak opleveren
- Testen vanaf de start
- Samenwerken met de klant
- Verdeelde verantwoordelijkheden
- Vaststellen scope
- Het maximaliseren van niet gedaan werk
Iterations
Deliver fast and frequent
Test driven
Small unit of work
Best practices
Stand ups
Continuous integration
Test driven
etc.
Benefits
Wat betekent agile voor mij als klant?
- Flexibiliteit
- Meer onzekerheid?
- Nauwe samenwerking
- Meer betrokkenheid en interactie
- Meer verantwoordelijkheid voor welslagen project
- Regelmatig werk
- Op tijd en binnen budget?
Allow for change
Choosing between agile and plan-driven software development¶
Richard Turner suggest that risk analysis be used to choose between adaptive ("agile") and predictive ("plan-driven") methods.
8 The authors suggest that each side of the continuum has its own home ground:
Agile home ground:
- Low criticality
- Senior developers
- Requirements change very often
- Small number of developers
- Culture that thrives on chaos
Plan-driven home ground:
- High criticality
- Junior developers
- Low requirements change
- Large number of developers
- Culture that demands order
Agile methods are a family of development processes, not a single approach to software development. In 2001, 17 prominent figures
2 in the field of agile development (then called "light- weight methodologies") came together at the Snowbird ski resort in Utah to discuss ways of creating software in a lighter, faster, more people-centric way. They created the Agile Manifesto, widely regarded as the canonical definition of agile development, and accompanying agile principles.