Date post: | 14-Sep-2014 |
Category: |
Technology |
View: | 5 times |
Download: | 0 times |
„A‟ is for Agile, the start of something good!
Introduction
BFC
Why change?
History of our world
Crystal
XP
Scrum FDD
AUP
RUP DSDM
Agile
RAD
Waterfall
agile | a̍jә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.‟
Agile
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
Agile
Agile is an umbrella term
for a set of values, principles
and practices
that have been shown to
improve the efficiency,
productivity, and quality of
software delivery
Values
and
Principles
Social
Practices
Technology
PracticesManagement
Practices
business value generation
and
risk mitigation
Key objectives of Agile
Agile myths
Building blocks of Agile
Practices
Principles
Values
Approach
Agile values
Courage &
Honesty
Having the courage to
give and receive timely
and honest feedback
To share and
collaborate with all
parties
Be transparent with no
hidden agendas
Innovative
Accountability
To show initiative and
creativeness in
delivering business
value
Being accountable
Holding others
accountable
Trust
Creating trust with
respect, fairness and
caring
Creating a „safe to
fail‟ environment
and empowering
teams to show
initiative and make
decisions
Agile principles
ValueFocus on business benefits and risk mitigation
Focus on actively working together and leveraging collective knowledgeCollaboration
Focus on time-boxed delivery and sustainable developmentSpeed
Focus on adapting to business requirements and welcoming changeFlexibility
Focus on keeping things simpleSimplicity
Focus on creating empowered , self-adjusting teamsTeamwork
Agile practices
Stand-
ups
Frequent
small
releases
Retro-
spectives
Sustainable
pace
Test driven
development
Automated
testing
Continuous
integration
Pair
programming
Co-location
Refactoring Adaptive
planning
Continuous
feedback
Agile approach
Flexibility does not mean chaos
Simplicity requires discipline and structure
The Agile Project Team
Core
Team
Extended
Team
Project
Manager
Support
AnalystOther key
stakeholde
rs
Applicatio
n Owner
Enterprise
Architect
Iteration
ManagerTech
lead
Infra-
structure
Lead
Bus.
SME
Software
Engineer
Architect
Tester
Business
Analyst
Program
Manager
Project
Sponsor
A cross
functional
team
Let‟s move!
Recap
Practices
Principles
Values
Approach
Prepared
Contribute
Expert
Competent
Agile Academy 2010 Course CurriculumFor course overviews go to www.agileacademy.com.au/agile/our_courses
Concept & Initiate
phases
V2 March 2010
Deliver (build & test) &
Deploy phases
Iteration & Project
Management
Requirement Definition Delivery Management
Project Management
Agile Leadership
Agile Project Management
Soft skills
Agile Leadership
Currently available
Currently being built
Agile Academy Confidential and Copyright
APM
ALD
Advanced Agile
Story writing &
management
SWM
1d
Agile Aligned for
Agile Experts
AAE
1/2d
Agile Design,
Architecture &
Technical Leadership
2d
Agile Automated
Testing
AAT
1d
Agile Project
Governance
AGV
1d
Configuration mgt.
Build engineering
Agile Builds 2d
ABD
Agile Initiate Phase
Start-me-up
Story Estimation
& Planning
Story
Elicitation and
Prioritisation
Initiate Phase
Introduction
AIS
2dAgile Delivery Phase
Start-me-up
Story Elaboration
Delivery Phase
Introduction
ADS
2d
Agile Programming for TDD
TDD
Refactoring
APT
2d
Test strategy & plans
Agile Testing basics
Agile Testing
AGT
2d2d
Design Patterns
OO Design
Design Patterns for Agile
Development
DPA
2d
Taste of AgileTOA
1d
Agile for InfrastructureAFI
1d
Agile for
the Business
AFB
1d
Agile Demystification
(CBT)
CBT
2h
Agile for Legacy
Applications and BAU1d
ALA
1d
Future Releases
DAT
Agile Interpersonal SkillsAIP
1dAgile Facilitation
AFL
1dAgile Team Building
ATB
1d
Continuous Improvement
using Agile and Lean 1d
CIA
Agile Concept
Phase
Start-me-up
Concept
Phase
Pre-Concept
Stage
ACS
1d
OTHER
SYSTEMUI LOGIC DB
80
days
60
days
= 380 days
Typical estimation work breakdown
140
days
100
days
OTHER
SYSTEMUI LOGIC DB
#89
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….
est: 3pri: HIGH
= 100 x 3.8 (avg)
= 380 days
100
Stories
1 Story
A story is a slice through all components
1 week
- Features are broken into small
“stories” of approximately 1-3
days effort
Stories in context
Build for feedback
Lovely woman, portrait,
landscape in background
Simplicity Speed Success
What else?
What about tracking progress?
Iterations /
Time
Story points
To Do
Done
Documentation
- We use documents for communication detail
- To arrive at a shared understanding
Shared understanding needs more....
“I want a cup of tea and a slice of cake or a coffee.”
Agile values shared understanding first.
✔
✘
✘
Risk mitigation
Burn Rate
Return
+$
-$
Design
Analysis
Code
Test
Production
Analysis
Design
Code
Test
Prod
Risk mitigation and early business value
Analysis
Design
Code
Test
Prod
Burn Rate
Return
+$
-$
Agile pitfalls
- Management commitment
- Business involvement
- Leadership
- Resourcing
- Testing challenges
- Lipstick
Benefits of Agile
Maximise
Business
value
Improve
quality
Reduce
cost
Great
place to
workMinimise
risk
Reduce
time to
market
Improve
responsiveness
& service
Decrease Increase
Q & A
www.agileacademy.com.au
„A‟ is for Agile, the start of something good!