Agile is a set of principles for iterative software development that values collaboration, adaptability, and delivering working software frequently. It aims to address shortcomings of traditional "waterfall" approaches which were inflexible, took too long, and did not provide value until late in the project. Key principles of Agile include satisfying customers through early delivery, welcoming changing requirements, frequent delivery of working software, daily collaboration between developers and business teams, and trusting self-organizing teams. Agile methods have benefits like increased productivity, faster time to market, and improved quality, but require constant business involvement and greater testing discipline.

1. Agile Principles & Culture

2. > “Hello, I’m Agile”

3. “and I‟m not alone”

4. A [very] short history of
Software development processes

5. Traditional Approaches
REQUIREMENTS
DESIGN
DEVELOPMENT
Waterfall Development is
another name for the more
TESTING
traditional approach
to software development
MAINTENANCE

6. Waterfall Development
You rarely aim to re-visit a „phase‟ once
You complete one phase (e.g. design) before
it‟s completed.
moving on to the
That means, you next phase (e.g. development)
better get whatever
you‟re doing right the first
time!

7. Downside of Traditional Approaches
Changes
REQUIREMENTS
 You don’t realize any value
until the end of the project
 You leave the testing until the
end
 You don’t seek approval from
the stakeholders until late in
the day
DESIGN
DEVELOPMENT
Takes too long
Skipped
TESTING
MAINTENANCE
This approach is highly risky, often more costly and
generally less efficient than Agile approaches

8. 18%
of projects failed
43%
challenged
2012 Chaos Report
(Standish Group)

9. 45%
of features
are never
used
2012 Chaos Report
(Standish Group)

10. why projects fail:
user input
incomplete requirements
changing requirements
lack of
2012 Chaos Report
(Standish Group)

11. What
Agile is Agile?
An umbrella term covering
Software development methodologies that adhere to the
Agile Manifesto
Most Agile teams use a hybrid of multiple approaches

14. #1- Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software

15. #2 – Welcome changing requirements even late in development.
Agile processes harness change for the customer’s competitive advantage

16. #3 – Deliver working software frequently, from a couple of weeks to a
couple of months, with preference to the shorter timescale.

17. #4 – Business people and developers must work together daily
throughout the project.

18. #5 – Build projects around motivated individuals. Give them the environment
and support they need and trust them to get the job done.

19. #6 – The most efficient and effective method of conveying information
to and within a development team is face-to-face conversation.

20. #7 – Working software is the primary measure of progress.

21. #8 – Agile processes promote sustainable development. The sponsors,
developers and users should be able to maintain a constant pace
indefinitely.

22. #9 – Continuous attention to technical excellence and good design
enhances agility.

23. #10 – Simplicity – the art of maximizing the amount of work not done – is
essential

24. #11 – The best architectures, requirements and designs emerge from
self-organizing teams

25. #12 – At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts it’s behavior accordingly.

26. Myths: Agile is NOT…
A specific methodology or process
•
•
Agile is a collection of best practices and principles for software
development
Agile is a philosophy, or a set of values
A “One Size Fits All” cookbook
•
Every project and team adjusts the application of Agile to fit the
circumstances, environment, and business problem to be solved
Simply iterations
•
Software is developed incrementally, in time-boxed iterations
“Glorified hacking”
•
Agile is a set of highly disciplined practices

27. benefits from Agile implementation
manage changing
priorities
increased
productivity
Faster time to
market
enhance product
quality
improved project
visibility
90%
85%
79%
81%
84%
2012 State of Agile Development Survey Results

28. Benefits of Agile
But, with this capability comes:
Constant business involvement
A need for more discipline
Greater emphasis on testing
An approach which sometimes clashes with some
organizational cultures

29. Agile is about
change
project
product
culture
people
organization

30. Credits
Pictures downloaded from internet
Agile with Guts – A Pragmatic Guide to Value-Driven
Development by Nicholas Gouy
Overview of Agile Methodology by Haresh Karkar
http://www.slideshare.net/hareshkarkar/overview-of-agilemethodology
Agile Principles, Agile People by Gaetano Mazzanti
http://www.slideshare.net/mgaewsj/agile-principles-agilepeople

31. Questions?