AGILE = lightweight process
origin: software development » countermovement to regulated methods like Waterfall or V-Model
methods: eg Pair Programming, Story Cards
focus: support complex SW environment with many individual requirements
LEAN = slim approaches
origin: production » Lean Thinking / Lean Production
methods: eg 3 “M”s (Muda, Mura, & Muri), Lead Time (reduce throughput time / cycle time)
focus: Lean philosophy (TPS: JIT, Kaizen, …) » question Taylorism
Mindset = point of view, philosophy, orientation » experiences from the past, environment, education
Agile Mindset = set of POVs » value, principles, practices from the agile world, to adapt, to learn, to face challenges and to inspect
Manifest = a written statement declaring publicly the intentions, motives or views of its issuer
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
That is, while there is value in the items on the right (bottom), we value the items on the left (top) more.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity – the art of maximizing the amount of work not done – is essential.
11. The best architectures, requirements and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.