4. A Brief History
http://www.senseoncents.com/wp-content/uploads/2012/07/Declaration-of-Independence1.jpg
Project Andiamo
On February 11-13, 2001, mountains of Utah,
seventeen people met to talk, ski,. What emerged was the Agile Software Development Manifesto.
Representatives from Extreme Programming,
!
Now, a bigger gathering of organizational anarchists.
!
The only concern with the term agile came from Martin Fowler
most Americans didn’t know how to pronounce the word agile.
6. 12 Principles of Agile
•
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.
Project Andiamo
11. If you’re building something new you’re free climbing
Project Andiamo
We had to persuade the business that they didn’t know where they were going they just broadly knew the destination
12. Types of Agile
•
Adaptive Software Development (ASD)
•
Agile Unified Process (AUP)
•
Crystal Methods (Crystal Clear)
•
Dynamic Systems Development Method (DSDM)
•
Extreme Programming (XP)
•
Feature Driven Development (FDD)
•
Kanban
•
Lean software development
•
Scrum
•
Scrum-ban
Project Andiamo
13. Scrum
"a flexible, holistic product development strategy where a
development team works as a unit to reach a common goal"
as opposed to a "traditional, sequential approach".
Project Andiamo
19. When is it good?
•
Your team works together in the same place at the
same time
•
Multiple development teams
•
Defined roles
•
You need discipline
•
Corporates/Customers: It feels more processey
Project Andiamo
31. When is it good?
•
Your team is in different places and works at
different times
•
Experienced and confident team
•
No politics
Project Andiamo
You can lay Kanban over the top of SCRUM
Kanban itself is not a software development process
33. Principles I’ve Learnt
•
Users first
•
Use cases are mandatory
•
We aim to fail fast
•
We will make mistakes, we accept this and mitigate losses up front
•
Everything we build is
•
Quickly iterative
•
Disposable
•
Doesn't constrain future growth
•
Agnostic
•
We always test (e.g. TDD, BDD) but real world tests are more important
•
The value in the future is context. How we get insights, make better decisions, and tell stories with
that data
Project Andiamo
35. What is the fastest, cheapest,
and best way to screw this up?
Project Andiamo
All these things are just tools they won’t stop you screwing stuff up
