10 Tips For Successful Agile Transitions

10 Tips for Successful
Agile Transitions
Joshua Kerievsky
joshua@industriallogic.com
QCON, San Francisco
November, 2007
Copyright 2007, Industrial Logic, Inc.

All Rights Reserved.
Tip #1: Begin All
Transitions with a
Readiness Assessment
Tip #2 – Leverage
The Power Of
Non-Technical AND
Technical Practices

Huh?!?!

Tip #3: Evolve By
Learning A Little Of
Everything
Tip #4
Educate the
Organizational
Antibodies
Educating The Antibodies
Pilot Project
Community
Future Project
Begin The Communities
Education
Right Away!!

How Would You Sell
Pair-Programming?
• Don’t sell it!
• Sell the risks of Solo Programming
– Tunnel Vision (Frog-In-A-Well) Syndrome
– Less Productivity
– Less Knowledge Transfer
– Longer Times Fixing Defects
– Less Code Re-Use
– Poorer testing
– Etc..
Removing Risks

Tip #5 Business Trumps Process
(most, but not all of the time)

Tip # 6 Engage The
Entire Organization
Management Customers
Executives & Board Members, Product and/or Project Manager,
Product & Product Line Domain Experts , Analysts (market,
Management, Sales & Marketing technical, etc.), Testers/QA,
Management, Project & Functional End Users / Beta Sites,
Management, QA Management Sales, Marketing & Service Support,
Usability Experts, Technical
Support, Educational Services
Support
Coaches, Software Services, Development
Facilities, Human Resources,
Legal, Auditors, Finance, Programmers, Technical writers,
3rd party vendors Database Designers &
Administrators, Architects

5.2 Release Plan (X Person Months)
Suite Story (i.e. Sized Headline)
Release Stories
Platform Release (X Person Months) Scheduling Release (X Person Months)

Product Stories
Master Rotations Release Budgeting Release

Platform Stories
Iteration Iteration Iteration

Iteration Stories
Engineering Tasks
Marketing VP Programmers
Subject
Matter
Tester
Expert
Tip # 7
Pick A Big Important Project!

Tip # 8 – Handle The Scaling
Problems

Serialized Knowledge Transfer
Time
Project Project Project Project

Community Community Community Community ...
1 2 3 4
XP/Agile XP/Agile XP/Agile XP/Agile

Knowledge Knowledge Knowledge Knowledge
Repetitive Exhausting
Costly Inconsistent
eLearning To The Rescue

Parallel Knowledge Transfer
Project Project
Community Community
1 2
Quality, Speedy,
Consistent
Knowledge
Transfer
Project Project
Community Community
3 4

Tip # 9
Gather
Metrics!
PI =
SIZE
TIME EFFORT
376,022 SLOC
Condor PI = = 17
24months
* 347person months
PI vs Size
35
PI = measure of process Kronos PIs are equally distributed

above and below the QSM Industry
Norm for 2005 Systems Software. 30
productivity and 25
development complexity 20
PI
15
Larry Putnam: Software 10
Metrics Guru & Pioneer. 5
Author of 5 Core Metrics. 10 100

Effective SLOC (thousands)
0
1,000

Timekeeping Sy stems Scheduling Data Collection Sy stems Utility
HR-Pay roll Engineering S... QSM 2005 Sy stem Softw are Av g. Line Sty le 1 Sigma Line Sty le
XP/Agile Yields Results Faster
PI
X X
1 2 3
Years Copyright 2007, Industrial Logic, Inc.
In-House Workshop:
A Lower Cost Strategy
Some experts
Project Project
Community Community
3–6 Future experts
Months Training &
Coaching
Future experts
In-House
Workshop
Project
Some experts Community

XP/Agile Productivity
Improvement
Previous Current Percentage
Performance Performance Improvement
Cost $2.8 Million $1.1 Million 61%

Schedule 18 Months 13.5 Months 24%
Defects 2,270 381 83%
Staffing 18 11 39%
Thanks to Michael Mah of QSMA and Jim Highsmith of the Cutter Consortium
Tip #10 - Fail Fast!

Failing Fast
FIT brings domain experts, analysts, testers and programmers into a test-driven
development cycle that yields executable specifications.
FIT is a monumental achievement in software development because it utterly succeeds

in uniting the actions of those who analyze, specify, test and program software systems.
FIT is an innovative tool that succeeds wildly in uniting the actions of those who analyze,
specify, test and program software systems.
By guiding how domain experts, analysts, testers and programmers collaborate on the
creation and validation of simple, tabular-based examples of business rules, FIT has
fundamentally changes the way quality software gets built.
By providing a simple, effective method for creating and automating

tabular examples of business rules, FIT has significantly improved
how domain experts, analysts, testers and programmers collaborate to
produce quality software.

THANK YOU!


10 Tips For Successful Agile Transitions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10 Tips For Successful Agile Transitions

Uploaded by

Copyright:

Available Formats

10 Tips for Successful

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Platform Release (X Person Months) Scheduling Release (X Person Months)

Master Rotations Release Budgeting Release

Iteration Iteration Iteration

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Project Project Project Project

XP/Agile XP/Agile XP/Agile XP/Agile

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

PI = measure of process Kronos PIs are equally distributed

Larry Putnam: Software 10

Metrics Guru & Pioneer. 5

Author of 5 Core Metrics. 10 100

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

Cost $2.8 Million $1.1 Million 61%

Copyright 2007, Industrial Logic, Inc.

FIT is a monumental achievement in software development because it utterly succeeds

By providing a simple, effective method for creating and automating

Copyright 2007, Industrial Logic, Inc.

Copyright 2007, Industrial Logic, Inc.

You might also like