Sie sind auf Seite 1von 25

IGA Disciplined Agile Development Workshop North American Office

James S. Bergamini
+1 (630) 590-5526
jb@daitanlabs.com
Brazil Office
Augusto Savio Cavalcanti
+55 (19) 3707-9600 (BR)
ac@daitanlabs.com

Agile Introduction

Presentation

Diogo Saad Cruz

01/2009/1.0

1
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Waterfall Lifecycle

What’s
What’swrong?
wrong?
2
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Cost of fixing errors

3
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Waterfall

4 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Process Control Model

The defined process control model


The defined process control model requires that every piece
of work be completely understood. Given a well-defined set of
inputs, the same outputs are generated every time. A defined
process can be started and allowed to run until completion,
with the same results every time.

The empirical process control model


Provides and exercises control through frequent inspection
and adaptation for processes that are imperfectly defined and
generate unpredictable and unrepeatable outputs

5
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Inspect and Adapt

Zone of success
Planned Completion

Planned Path
Start
Actual Path

As Knowledge
increases Leaders use
Actual Completion
iterations to guide
project towards
enhanced goal

6 June 2008 IBM Internal Use Only : With Thanks to Mary and Tom Poppendieck
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Agile

7 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Agile Defined (Industry)

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.
© 2001 www.agilemanifesto.org
8 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Myths

“The Agile methodology movement is not anti-methodology; in fact,


many of us want to restore credibility to the word. We also want to
restore a balance: We embrace modeling, but not merely to file
some diagram in a dusty corporate repository. We embrace
documentation, but not to waste reams of paper in never-
maintained and rarely-used tomes. We plan, but recognize the limits
of planning in a turbulent environment.”

Martin Fowler and Jim Highsmith

See http://www.drdobbs.com/linux-open-source/184414755

9 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop

Key Characteristics of Successful Agile Projects

• Stable,Time-Boxed,Short Iterations
• Stakeholder Feedback
• Self-Directed Teams
• Sustainable Pace

10 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop

Agile Framework

Extreme Programming SCRUM: Crystal: Dynamic Systems


(XP): • Small teams of 6-8 people
Development Method
• Frequent delivery (DSDM):
• Based on values of
• “Backlog” defined • Reflective improvement
simplicity, communication, •3 primary phases: Pre-
feedback, courage, and requirements that will be
addressed in each Sprint Adaptive: Project, Project Life-Cycle ,
respect Post-Project
• Start with simple solution, • Daily 15 min.Scrum • Repeating Speculate,
add complexity through meeting to discuss work for Collaborate, Learn cycles
the day Feature Driven Dev.:
refactoring • Provides for continuous
learning and adaptation • Develop feature list
•Unified Process: to changing project state • Plan, Design, Build by
• Simplified version of Feature
Rational Unified Process –
reduced number of
disciplines
Agile Techniques: The above methods involve a number of different techniques including

Test-driven development Continuous integration Static Analysis


Planning game Design improvement Coding standard
Pair Programming Small releases Sustainable pace
Refactoring Simple design Whole team

11 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
What is Scrum ?

Scrum is an agile software


development framework.
o Empirical management and control process
o Inspect and adapt feedback loops
o Used to manage complex projects since 1990
o Delivers business functionality in 30 (20) days
o Scalable to distributed, large and long projects
o Extreme simple but very hard

12 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Origins of Scrum …

The New, New Product


Development Game*
IID
Lean Management

13 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Scrum Flow…

14 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Scrum Process

15 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
No changes during a sprint

Change

 Plan sprint durations around how long you can commit to keeping
change out of the sprint

16
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Scrum is lightweight
Roles

•Product owner
•ScrumMaster
•Team
Ceremonies

•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts

•Product backlog
•Sprint backlog
•Burndown charts
17
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop

18 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
User Stories

A User Story takes the form of:


As a <Role>, I want to <Goal> so I can <Business
value>.

Examples:
As a DBA at Wal*Mart, I want to be able to reduce
storage consumption so that I manage fewer storage
devices.

As an administrator, I want to prove that only


approved clients are allowed to use specific services
so that I can control data security/costs/etc.

19 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
User Stories to tasks

During
Duringiteration
iterationplanning
planningbreak
breakthe
thestories
storiesdown
downinto
intotasks
tasks
• Task #1 (X hours)
User Story
•Task #2 (Y hours)
•Task #3 (Z hours)

• Identify common upgrade scenarios (16 hours)


As a Wal*Mart sys
• Implement (16 hours)
admin, I want to
upgrade WAS on • Test (8 hours)
AIX so I can take • Update documentation to include upgrade
advantage of new instructions (8 hours)
features

20 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Stand up meetings

21 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Burn down chart

22
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Scrum Flow

23 June 2008
Brazil Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Agile

 In summary:
 Build Software that really works (your only progress metric is working
–tested- software).
 Agile produces information that can be used for better management.
 Scope is variable, not quality;
 Analysis, test, design and implementation occurs in tiny pieces;
 Agile frameworks is not the silver bullet. I will not solve your
problems, they will just make them visible to you.
 Product remains in steady/stable status during the whole lifecycle;
 Focused on business success;

 Embrace changes;

24
Daitan Labs Proprietary
IGA Disciplined Agile Development Workshop
Questions

25 June 2008
Brazil Daitan Labs Proprietary

Das könnte Ihnen auch gefallen