1. „A‟ is for Agile, the start of something good!

2. Introduction

3. Why change?
BFC

4. History of our world
Waterfall
RAD RUP DSDM
XP Agile AUP
Scrum FDD Crystal

5. Agile
agile |ˈajәl|
adjective
able to move quickly and easily : Ruth was
as agile as a monkey | figurative his vague
manner concealed an agile mind
ORIGIN late Middle English : via French from
Latin agilis, from agere „do.‟

6. The Agile Manifesto
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.
Source: http://www.agilemanifesto.org

7. Agile
Agile is an umbrella term
Social
Practices
for a set of values, principles
and practices
that have been shown to
improve the efficiency, Values
productivity, and quality of
and
software delivery
Technology Principles Management
Practices Practices

8. Key objectives of Agile
business value generation
and
risk mitigation

9. Agile myths

10. Building blocks of Agile
Approach
Practices
Principles
Values

11. Agile values
Innovative Courage &
Trust
Accountability Honesty
Creating trust with To show initiative and Having the courage to
respect, fairness and creativeness in give and receive timely
caring delivering business and honest feedback
value
Creating a „safe to To share and
fail‟ environment Being accountable collaborate with all
parties
and empowering Holding others
teams to show accountable Be transparent with no
initiative and make hidden agendas
decisions

12. Agile principles
Focus on business benefits and risk mitigation
Value
Collaboration Focus on actively working together and leveraging collective knowledge
Focus on time-boxed delivery and sustainable development
Speed
Focus on adapting to business requirements and welcoming change
Flexibility
Focus on keeping things simple
Simplicity
Focus on creating empowered , self-adjusting teams
Teamwork

13. Agile practices
Automated
testing
Co-location
Test driven
development
Continuous
integration
Refactoring Adaptive
Sustainable
planning Stand-
pace
ups
Pair
programming
Continuous Retro- Frequent
feedback spectives small
releases

14. Agile approach
Flexibility does not mean chaos
Simplicity requires discipline and structure

15. The Agile Project Team
Project
Sponsor
Project
Manager Program
Enterprise Manager
Architect
Iteration
A cross
Manager
Tech functional
lead
Business
team
Applicatio
Analyst
Core Infra-
structure
n Owner Lead
Team
Tester
Bus.
SME
Architect Software
Engineer Support
Other key
stakeholde Analyst
rs
Extended
Team

16. Let‟s move!

17. Recap
Approach
Practices
Principles
Values

18. Agile Academy 2010 Course Curriculum
For course overviews go to www.agileacademy.com.au/agile/our_courses
ALD AIP AFL ATB
Agile Leadership Agile Interpersonal Skills Agile Facilitation Agile Team Building
1d 1d 1d 1d
Soft skills
Requirement Definition Delivery Management
SWM Advanced Agile DAT AAT AGV
Agile Design,
Agile Automated Agile Project
Story writing & Architecture &
Expert management 1d
Technical Leadership
Testing
1d
Governance
1d
2d
ABD
Configuration mgt.
ALA Agile for Legacy
AIS Build engineering Applications and BAU
1d
Competent ACS
Story Estimation
Agile Builds 2d
& Planning APT AGT APM
Concept
Phase TDD Test strategy & plans Project Management
Story
Elicitation and Refactoring Agile Testing basics Agile Leadership
Pre-Concept Prioritisation Agile Programming for TDD Agile Testing 2d Agile Project Management
Stage
Contribute 2d 2d
ADS DPA
Initiate Phase
Introduction Story Elaboration Design Patterns
Agile Concept
Phase
Delivery Phase OO Design
Start-me-up 1d AAE
Agile Aligned for
Agile Initiate Phase Introduction Design Patterns for Agile
Start-me-up Agile Experts 1/2d
Development 2d
Prepared 2d
Agile Delivery Phase
Start-me-up
AFI
Agile for Infrastructure 1d
2d
CIA
CBT
Agile Demystification Continuous Improvement AFB
Agile for
TOA
(CBT) Taste of Agile using Agile and Lean 1d the Business 1d
2h 1d
Currently available
Concept & Initiate Deliver (build & test) & Iteration & Project
Currently being built
Future Releases
phases Deploy phases Management
V2 March 2010 Agile Academy Confidential and Copyright

19. Typical estimation work breakdown
OTHER
UI LOGIC DB SYSTEM
100 140 80 60
days days days days
= 380 days

20. A story is a slice through all components
#89 pri: HIGH est: 3
As a retail banking consultant I need to see all
credit card balances for a customer so that I
can have a good conversation with the
customer.
Tests:
when positive balance…
when negative balance….
100
Stories
1 Story
OTHER
UI LOGIC DB SYSTEM
= 100 x 3.8 (avg)
= 380 days

21. Stories in context
- Features are broken into small
“stories” of approximately 1-3
days effort
1 week

22. Build for feedback
Simplicity Speed Success
Lovely woman,
portrait,
landscape in
background

23. What else?

24. What about tracking progress?
Story points
To Do
Done
Iterations /
Time

25. Documentation
- We use documents for communication detail
- To arrive at a shared understanding

26. Shared understanding needs more....
“I want a cup of tea and a slice of cake or a coffee.”

27. Agile values shared understanding first.
✘
✘
✔

28. Risk mitigation
Analysis
Analysis
Design Design
Code
+$ Code
Test
Test
Production
Prod
Return
Burn Rate
-$

29. Risk mitigation and early business value
Analysis
Design
Code
Test
+$
Prod
Return
Burn Rate
-$

30. Agile pitfalls
- Management commitment
- Business involvement
- Leadership
- Resourcing
- Testing challenges
- Lipstick

31. Benefits of Agile
Decrease Increase
Reduce Improve
time to quality
market
Great Maximise
Minimise place to Business
risk work value
Reduce Improve
cost responsiveness
& service

32. Q&A
www.agileacademy.com.au

33. „A‟ is for Agile, the start of something good!