12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

A disciplined approach to adopting agile

practices: the agile adoption framework
Innovations in Systems and Software Engineering

September 2007, Volume 3, Issue 3, pp 203–216 | Cite as

Ahmed Sidky (1)

James Arthur (1)
Shawn Bohner (1) Email author (sbohner@vt.edu)

1. Virginia Tech, Blacksburg, USA

State of the Art

First Online: 24 July 2007
Received: 06 March 2007
Accepted: 08 May 2007

1 Shares
1.1k Downloads
31 Citations

Abstract

Many organizations aspire to adopt agile processes to take advantage of the numerous
benefits that they offer to an organization. Those benefits include, but are not limited to,
quicker return on investment, better software quality, and higher customer satisfaction.
To date, however, there is no structured process (at least that is published in the public
domain) that guides organizations in adopting agile practices. To address this situation,
we present the agile adoption framework and the innovative approach we have used to
implement it. The framework consists of two components: an agile measurement index,
and a four-stage process, that together guide and assist the agile adoption efforts of
organizations. More specifically, the Sidky Agile Measurement Index (SAMI)
encompasses five agile levels that are used to identify the agile potential of projects and
organizations. The four-stage process, on the other hand, helps determine (a) whether or
not organizations are ready for agile adoption, and (b) guided by their potential, what set
of agile practices can and should be introduced. To help substantiate the “goodness” of
the Agile Adoption Framework, we presented it to various members of the agile
community, and elicited responses through questionnaires. The results of that
substantiation effort are encouraging, and are also presented in this paper.

https://link.springer.com/article/10.1007/s11334-007-0026-z 1/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

Preview

Unable to display preview. Download preview PDF.

References

1. Declaration of Interdependence, http://pmdoi.org/ (2005)

Google Scholar (https://scholar.google.com/scholar?
q=Declaration%20of%20Interdependence%2C%20http%3A%2F%2Fpmdoi.org%
2F%20%282005%29)
2. Manifesto for Agile Software Devleopment, www.agilemanifesto.org, Utah, Feb
2001
Google Scholar (https://scholar.google.com/scholar?
q=Manifesto%20for%20Agile%20Software%20Devleopment%2C%20www.agilem
anifesto.org%2C%20Utah%2C%20Feb%202001)
3. Abrahamsson P, Outi S, Ronkainen J, Warsta J (2002) Agile software
development methods—review and analysis. VTT Electronics, Finland, pp 112
Google Scholar (https://scholar.google.com/scholar?
q=Abrahamsson%20P%2C%20Outi%20S%2C%20Ronkainen%20J%2C%20Wars
ta%20J%20%282002%29%20Agile%20software%20development%20methods%
E2%80%94review%20and%20analysis.%20VTT%20Electronics%2C%20Finland
%2C%20pp%20112)
4. Ambler S (2002). Agile modeling: effective practices for extreme programming
and the unified process. Wiley, New York
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20modeling%3A%20effective%20practices%20for%20extreme%20pr
ogramming%20and%20the%20unified%20process&author=S.%20Ambler&publi
cation_year=2002)
5. Ambler SW and Sadalage PJ (2006). Refactoring databases: evolutionary database
design. Addison-Wesley Professional, Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Refactoring%20databases%3A%20evolutionary%20database%20design&aut
hor=SW.%20Ambler&author=PJ.%20Sadalage&publication_year=2006)
6. Amy L and Raylene C (2005). Effects of agile practices on social factors. ACM
Press, St. Louis

https://link.springer.com/article/10.1007/s11334-007-0026-z 2/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

Google Scholar (http://scholar.google.com/scholar_lookup?

title=Effects%20of%20agile%20practices%20on%20social%20factors&author=L.
%20Amy&author=C.%20Raylene&publication_year=2005)
7. Arthur J and Nance R (2002). Managing software quality: a measurement
framework for assessment and prediction. Springer, Heidelberg
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Managing%20software%20quality%3A%20a%20measurement%20framewo
rk%20for%20assessment%20and%20prediction&author=J.%20Arthur&author=
R.%20Nance&publication_year=2002)
8. Barnett L (2006) Agile survey results: solid experience and real results Agile
Journal
Google Scholar (https://scholar.google.com/scholar?
q=Barnett%20L%20%282006%29%20Agile%20survey%20results%3A%20solid
%20experience%20and%20real%20results%20Agile%20Journal)
9. Barnett L, Schwaber C (2004) Adopting agile development processes; improve
time-to-benefits for software projects forrester research
Google Scholar (https://scholar.google.com/scholar?
q=Barnett%20L%2C%20Schwaber%20C%20%282004%29%20Adopting%20agil
e%20development%20processes%3B%20improve%20time-to-
benefits%20for%20software%20projects%20forrester%20research)
10. Basili V (1992) Software modeling and measurement: the Goal/Question/Metric
paradigm. University of Maryland, College Park, pp 24
Google Scholar (https://scholar.google.com/scholar?
q=Basili%20V%20%281992%29%20Software%20modeling%20and%20measure
ment%3A%20the%20Goal%2FQuestion%2FMetric%20paradigm.%20University
%20of%20Maryland%2C%20College%20Park%2C%20pp%2024)
11. Beck (2002). Test driven development: by example. Addison- Wesley Longman
Publishing Co., Inc., Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Test%20driven%20development%3A%20by%20example&author=.%20Beck
&publication_year=2002)
12. Beck K (2000). Extreme programming explained: embrace change. Addison-
Wesley, Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Extreme%20programming%20explained%3A%20embrace%20change&auth
or=K.%20Beck&publication_year=2000)
13. Beck K, Martin RC, Cockburn A, Fowler M, Highsmith J (2001) Manifesto for
agile software development, www.agilemanifesto.org, Utah
Google Scholar (https://scholar.google.com/scholar?
q=Beck%20K%2C%20Martin%20RC%2C%20Cockburn%20A%2C%20Fowler%2
0M%2C%20Highsmith%20J%20%282001%29%20Manifesto%20for%20agile%2
0software%20development%2C%20www.agilemanifesto.org%2C%20Utah)
14. Boehm B and Turner R (2005). Management challenges to implementing agile
processes in traditional development organizations. Softw IEEE 22: 30–39
CrossRef (https://doi.org/10.1109/MS.2005.129)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Management%20challenges%20to%20implementing%20agile%20processes

https://link.springer.com/article/10.1007/s11334-007-0026-z 3/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

%20in%20traditional%20development%20organizations&author=B.%20Boehm&
author=R.%20Turner&journal=Softw%20IEEE&volume=22&pages=30-
39&publication_year=2005)
15. Boehm BW and Turner R (2003). Balancing agility and discipline. Addison-
Wesley Professional, Boston
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Balancing%20agility%20and%20discipline&author=BW.%20Boehm&autho
r=R.%20Turner&publication_year=2003)
16. Cockburn A (2001). Agile software development. Pearson Education, Indianapolis
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20software%20development&author=A.%20Cockburn&publication_
year=2001)
17. Cockburn A and Highsmith J (2001). Agile software development: the people
factor. Computer 34: 131–133
CrossRef (https://doi.org/10.1109/2.963450)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20software%20development%3A%20the%20people%20factor&autho
r=A.%20Cockburn&author=J.%20Highsmith&journal=Computer&volume=34&p
ages=131-133&publication_year=2001)
18. Cohn M (2005). Agile estimating and planning. Prentice Hall PTR, New Jersey
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20estimating%20and%20planning&author=M.%20Cohn&publicatio
n_year=2005)
19. Cohn M (2004). User stories applied. Addison-Wesley, Boston
Google Scholar (http://scholar.google.com/scholar_lookup?
title=User%20stories%20applied&author=M.%20Cohn&publication_year=2004)
20. Elssamadisy A (2006) Getting Beyond “It Depends!” being specific but not
presiptive about agile practice adoption agile journal
Google Scholar (https://scholar.google.com/scholar?
q=Elssamadisy%20A%20%282006%29%20Getting%20Beyond%20%E2%80%9C
It%20Depends%21%E2%80%9D%20being%20specific%20but%20not%20presipt
ive%20about%20agile%20practice%20adoption%20agile%20journal)
21. Fowler M, Beck K, Brant J, Opdyke W and Roberts D (1999). Refactoring:
improving the design of existing code. Addison Wesley, Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Refactoring%3A%20improving%20the%20design%20of%20existing%20cod
e&author=M.%20Fowler&author=K.%20Beck&author=J.%20Brant&author=W.%
20Opdyke&author=D.%20Roberts&publication_year=1999)
22. Grady RB (1997). Successful software process improvement. Prentice-Hall Inc.,
Englewood Cliffs
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Successful%20software%20process%20improvement&author=RB.%20Grad
y&publication_year=1997)
23. Highsmith J (2002). Agile software development ecosystems. Pearson Education,
Indianapolis

https://link.springer.com/article/10.1007/s11334-007-0026-z 4/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

Google Scholar (http://scholar.google.com/scholar_lookup?

title=Agile%20software%20development%20ecosystems&author=J.%20Highsmit
h&publication_year=2002)
24. Highsmith J (2006) Agile: from rogue teams to enterprise acceptance cutter
consortium: business technology trends and impacts
Google Scholar (https://scholar.google.com/scholar?
q=Highsmith%20J%20%282006%29%20Agile%3A%20from%20rogue%20teams
%20to%20enterprise%20acceptance%20cutter%20consortium%3A%20business
%20technology%20trends%20and%20impacts)
25. Hunt A, Thomas D (2004) Pragmatic unit testing in C\# with NUnit, The
Pragmatic Programmers
Google Scholar (https://scholar.google.com/scholar?
q=Hunt%20A%2C%20Thomas%20D%20%282004%29%20Pragmatic%20unit%
20testing%20in%20C%5C%23%20with%20NUnit%2C%20The%20Pragmatic%2
0Programmers)
26. Hunt J (2006). Agile software construction. Springer, London
MATH (http://www.emis.de/MATH-item?1095.68019)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20software%20construction&author=J.%20Hunt&publication_year=
2006)
27. Jan P-H, Jorn J (2005) AIM—ability improvement model
Google Scholar (https://scholar.google.com/scholar?q=Jan%20P-
H%2C%20Jorn%20J%20%282005%29%20AIM%E2%80%94ability%20improve
ment%20model)
28. Koch AS (2005). Agile software development: evaluating the methods for your
organization. Artech House, Boston
MATH (http://www.emis.de/MATH-item?1075.68571)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20software%20development%3A%20evaluating%20the%20methods
%20for%20your%20organization&author=AS.%20Koch&publication_year=2005
)
29. Kuppuswami S, Vivekanandan K, Ramaswamy P and Rodrigues P (2003). The
effects of individual XP practices on software development effort. SIGSOFT Softw
Eng Notes 28: 6–6
CrossRef (https://doi.org/10.1145/966221.966239)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=The%20effects%20of%20individual%20XP%20practices%20on%20software
%20development%20effort&author=S.%20Kuppuswami&author=K.%20Vivekan
andan&author=P.%20Ramaswamy&author=P.%20Rodrigues&journal=SIGSOFT
%20Softw%20Eng%20Notes&volume=28&pages=6-6&publication_year=2003)
30. Larman C (2004). Agile and iterative development. Pearson Education, Boston
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20and%20iterative%20development&author=C.%20Larman&publica
tion_year=2004)
31. Law A and Charron R (2005). Effects of agile practices on social factors,
Proceedings of the 2005 workshop on Human and social factors of software
engineering. ACM Press, St. Louis

https://link.springer.com/article/10.1007/s11334-007-0026-z 5/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

Google Scholar (http://scholar.google.com/scholar_lookup?

title=Effects%20of%20agile%20practices%20on%20social%20factors%2C%20Pr
oceedings%20of%20the%202005%20workshop%20on%20Human%20and%20so
cial%20factors%20of%20software%20engineering&author=A.%20Law&author=
R.%20Charron&publication_year=2005)
32. Martin RC (2002). Agile software development, principles, patterns and practices.
Prentice Hall, Englewood Cliffs
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20software%20development%2C%20principles%2C%20patterns%2C
%20and%20practices&author=RC.%20Martin&publication_year=2002)
33. Newkirk JW and Martin RC (2001). Extreme programming in practice. Prentice
Hall, Englewood Cliffs
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Extreme%20programming%20in%20practice&author=JW.%20Newkirk&au
thor=RC.%20Martin&publication_year=2001)
34. Park R, Goethert W, Florac W (1996) Goal-driven software measurement–a
guidebook, Software Engineering Institute, Carnegie Mellon
Google Scholar (https://scholar.google.com/scholar?
q=Park%20R%2C%20Goethert%20W%2C%20Florac%20W%20%281996%29%2
0Goal-
driven%20software%20measurement%E2%80%93a%20guidebook%2C%20Softw
are%20Engineering%20Institute%2C%20Carnegie%20Mellon)
35. Pukinskis A (2005) 5 stumbling blocks for new corporate agile projects, the agile
blog
Google Scholar (https://scholar.google.com/scholar?
q=Pukinskis%20A%20%282005%29%205%20stumbling%20blocks%20for%20n
ew%20corporate%20agile%20projects%2C%20the%20agile%20blog)
36. Rosenberg D, Stephens M and Collins-Cope M (2005). Agile development with
ICONIX process : people, process, and pragmatism. Apress, Berkeley
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20development%20with%20ICONIX%20process%20%3A%20people
%2C%20process%2C%20and%20pragmatism&author=D.%20Rosenberg&author
=M.%20Stephens&author=M.%20Collins-Cope&publication_year=2005)
37. Rueping A (2003). Agile documentation: a pattern guide to producing lightweight
documents for software projects. Wiley, New York
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20documentation%3A%20a%20pattern%20guide%20to%20produci
ng%20lightweight%20documents%20for%20software%20projects&author=A.%2
0Rueping&publication_year=2003)
38. Schatz B and Abdelshafi I (2005). Primavera gets agile: a successful transition to
agile development. Softw IEEE 22: 36–42
CrossRef (https://doi.org/10.1109/MS.2005.74)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Primavera%20gets%20agile%3A%20a%20successful%20transition%20to%2
0agile%20development&author=B.%20Schatz&author=I.%20Abdelshafi&journal
=Softw%20IEEE&volume=22&pages=36-42&publication_year=2005)

https://link.springer.com/article/10.1007/s11334-007-0026-z 6/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

39. Schwaber K and Beedle M (2002). Agile Software Development with SUM.
Prentice Hall, Englewood Cliffs
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Agile%20Software%20Development%20with%20SUM&author=K.%20Schw
aber&author=M.%20Beedle&publication_year=2002)
40. Sidky A, Arthur J (2006) Agile adoption process framework—indicators
document, CORR - cs.SE/0612092
Google Scholar (https://scholar.google.com/scholar?
q=Sidky%20A%2C%20Arthur%20J%20%282006%29%20Agile%20adoption%20
process%20framework%E2%80%94indicators%20document%2C%20CORR%20-
%20cs.SE%2F0612092)
41. Spayd MK (2003) Evolving agile in the enterprise: implementing XP on a grand
scale, pp 60–70
Google Scholar (https://scholar.google.com/scholar?
q=Spayd%20MK%20%282003%29%20Evolving%20agile%20in%20the%20enter
prise%3A%20implementing%20XP%20on%20a%20grand%20scale%2C%20pp%
2060%E2%80%9370)
42. Tabaka J (2005). Collaboration explained; facilitation skills for software project
leaders. Addison-Wesley, Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Collaboration%20explained%3B%20facilitation%20skills%20for%20softwar
e%20project%20leaders&author=J.%20Tabaka&publication_year=2005)
43. Wake WC (2001). Extreme programming explored. Addison- Wesley Professional,
Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Extreme%20programming%20explored&author=WC.%20Wake&publicatio
n_year=2001)
44. Williams L and Kessler R (2002). Pair programming illuminated. Addison-Wesley
Longman Publishing Co., Inc., Reading
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Pair%20programming%20illuminated&author=L.%20Williams&author=R.
%20Kessler&publication_year=2002)
45. Williams L, Kessler RR, Cunningham W and Jeffries R (2000). Strengthening the
case for pair programming. Softw IEEE 17: 19–25
CrossRef (https://doi.org/10.1109/52.854064)
Google Scholar (http://scholar.google.com/scholar_lookup?
title=Strengthening%20the%20case%20for%20pair%20programming&author=L.
%20Williams&author=RR.%20Kessler&author=W.%20Cunningham&author=R.
%20Jeffries&journal=Softw%20IEEE&volume=17&pages=19-
25&publication_year=2000)

Copyright information
© Springer-Verlag London Limited 2007

https://link.springer.com/article/10.1007/s11334-007-0026-z 7/8
12/26/2017 A disciplined approach to adopting agile practices: the agile adoption framework | SpringerLink

About this article

Cite this article as:
Sidky, A., Arthur, J. & Bohner, S. Innovations Syst Softw Eng (2007) 3: 203. https://doi.org/10.1007/s11334-
007-0026-z

DOI (Digital Object Identifier) https://doi.org/10.1007/s11334-007-0026-z

Publisher Name Springer-Verlag
Print ISSN 1614-5046
Online ISSN 1614-5054

About this journal

Reprints and Permissions

Personalised recommendations

© 2017 Springer International Publishing AG. Part of Springer Nature.

Not logged in Not affiliated 138.68.98.52

https://link.springer.com/article/10.1007/s11334-007-0026-z 8/8