Agile Paradigm Shift

1
Agile Paradigm Shift

• Rachel Davies
• Chair_at_agilealliance.org

2
Methodologists United!
I kicked off "The Lightweight Process Summit"
with a 10 minute plea for a manifesto, and then
watched with awe and glee as these people, with
some deep philosophical differences, found
themselves in fundamental agreement with the
notion that what we shared in common was more
important than our differences. BobMartin
3
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 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. www.agilemanifesto.org
4
Agile Camps Remain
crystal
scrum
XP
DSDM
LEAN
5
Methodologists and the Agile Elephant
6
Do Method Books Help?

• Use as source of ideas
• Not religious texts
• Read more than one!

7
Methodology Assumptions

• One method for all project contexts
• Common approach to agile transitions
• write the process down
• get training
• allocate roles
• follow the process.
• This doesnt usually work!
• Agile methods also include guiding principles and
  values, where do they come in?

8
My Agile Journeyas an avid reader of methodology
books!

• 1990s large projects cancelled. OO led me to
  incremental development and process patterns via
  RUP
• 2000 sought out XTC and joined an XP team
• 2001 brought in Scrum techniques to my XP team.
  XP2001 XPDay.
• 2002 learned about DSDM and Lean
• 2003 started coaching agile teams and got
  certified in Scrum. Joined Agile Alliance.
• 2006 still coaching agile teams and still
  blending method approaches.

9
Whats the problem?
10
Heres where we need to understand the Agile
Paradigm shift ..
11
Process following steps?
12
The Dream
Developers
Customer
The Product
13
The Reality
14
What about unexpected situations?
We need to improvise for current context
15
Skill Trained to use Tools?
16
Skill requires experience
17
Too big to solve alone Teams
18
Environment Matters!
19
Agile Transitions
People and projects are different so not one
process for all Need to address teamwork and
workspace not just process!
20
My Advice

• Agile is an adjective not a noun!
• Dont get hung up too much by the methodology -)
• Use the principles of the manifesto of agile
  software development to guide your team.
• Conways Law
• Pay attention to communication and everything
  else will follow

21
Grassroots Fusion

• Agile Alliance
• a non-profit organization that supports
  individuals and organizations who use agile
  approaches to develop software.
• Agile200x conference series
• Agile-neutral forum
• http//forum.agilesoftwaredevelopment.org/

22
News from the Method Camps
23
Scrum

• Scrum is a good place to start
• Not many practices simple incremental development
  cycle, many Scrum teams go on to adopt XP
  practices
• Scrum Alliance a for-profit organisation geared
  up to train scrum masters
• 6000 certified scrum masters?!

24
Extreme Programming

• The current spin is "Responsible Development -
  emphasis on accountability.

Value
Estimation
Clarification
Integration
Testing
Design
Implementation
25
Crystal

• Crystal gives advice on scaling based on
  Alistair's observations of what works.
• It's not widely practiced by the book but people
  are adapting their agile approach to context so
  its happening as a movement not a method

26
DSDM

• DSDM has good advice but appears old school.
• Newsflash has just put DSDM v4.2 on-line for
  public access, includes advice on wrapping XP.
• Agile Business Conference is including a
  leadership summit this year.
• DSDM are also linking up with Association of
  Project Management

27
Declaration of Interdependence

• We increase return on investment by making
  continuous flow of value our focus.
• We deliver reliable results by engaging customers
  in frequent interactions and shared ownership.
• We expect uncertainty and manage for it through
  iterations, anticipation, and adaptation.
• We unleash creativity and innovation by
  recognizing that individuals are the ultimate
  source of value, and creating an environment
  where they can make a difference.
• We boost performance through group accountability
  for results and shared responsibility for team
  effectiveness.
• We improve effectiveness and reliability through
  situationally specific strategies, processes and
  practices.?

28
Lean Software Development

• Lean Software Development is all about shortening
  information feedback loops and removing waste in
  the software development process in order to
  increase flow of value.
• Was heavy on principles and light on practice
  (mainly referring to XP and Scrum).
• New book on implementation just published.

29
Any Questions?