A disciplined approach to adopting agile practices: The agile adoption framework

Innovations in Systems and Software Engineering

Volumn 3, Issue 3, 2007, Pages 203-216

  Sidky, Ahmed ^a   Arthur, James ^a   Bohner, Shawn ^a  

^a VIRGINIA POLYTECHNIC INSTITUTE AND STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

AGILE MANUFACTURING SYSTEMS; COMPUTER SOFTWARE; INNOVATION; INVESTMENTS;

INNOVATIVE APPROACH; SOFTWARE QUALITY;

PROCESS ENGINEERING;

EID: 34548695919     PISSN: 16145046     EISSN: 16145054     Source Type: Journal    
DOI: 10.1007/s11334-007-0026-z     Document Type: Article

References (45)

1. Declaration of Interdependence, http://pmdoi.org/ (2005)
2. Manifesto for Agile Software Devleopment, www.agilemanifesto.org, Utah, Feb 2001
3. Abrahamsson P, Outi S, Ronkainen J, Warsta J (2002) Agile software development methods-review and analysis. VTT Electronics, Finland, pp 112
4. Ambler S (2002). Agile modeling: Effective practices for extreme programming and the unified process. Wiley, New York
5. Ambler SW and Sadalage PJ (2006). Refactoring databases: Evolutionary database design. Addison-Wesley Professional, Reading
6. Amy L and Raylene C (2005). Effects of agile practices on social factors. ACM Press, St. Louis
7. Arthur J and Nance R (2002). Managing software quality: A measurement framework for assessment and prediction. Springer, Heidelberg
8. Barnett L (2006) Agile survey results: Solid experience and real results Agile Journal
9. Barnett L, Schwaber C (2004) Adopting agile development processes; improve time-to-benefits for software projects forrester research
10. Basili V (1992) Software modeling and measurement: The Goal/Question/ Metric paradigm. University of Maryland, College Park, pp 24
11. Beck (2002). Test driven development: By example. Addison- Wesley Longman Publishing Co., Inc., Reading
12. Beck K (2000). Extreme programming explained: Embrace change. Addison-Wesley, Reading
13. Beck K, Martin RC, Cockburn A, Fowler M, Highsmith J (2001) Manifesto for agile software development, www.agilemanifesto.org, Utah
14. Boehm B and Turner R (2005). Management challenges to implementing agile processes in traditional development organizations. Softw IEEE 22: 30-39
15. Boehm BW and Turner R (2003). Balancing agility and discipline. Addison-Wesley Professional, Boston
16. Cockburn A (2001). Agile software development. Pearson Education, Indianapolis
17. Cockburn A and Highsmith J (2001). Agile software development: The people factor. Computer 34: 131-133
18. Cohn M (2005). Agile estimating and planning. Prentice Hall PTR, New Jersey
19. Cohn M (2004). User stories applied. Addison-Wesley, Boston
20. Elssamadisy A (2006) Getting Beyond "It Depends!" being specific but not presiptive about agile practice adoption agile journal
21. Fowler M, Beck K, Brant J, Opdyke W and Roberts D (1999). Refactoring: improving the design of existing code. Addison Wesley, Reading
22. Grady RB (1997). Successful software process improvement. Prentice-Hall Inc., Englewood Cliffs
23. Highsmith J (2002). Agile software development ecosystems. Pearson Education, Indianapolis
24. Highsmith J (2006) Agile: From rogue teams to enterprise acceptance cutter consortium: Business technology trends and impacts
25. Hunt A, Thomas D (2004) Pragmatic unit testing in C# with NUnit, The Pragmatic Programmers
26. Hunt J (2006). Agile software construction. Springer, London
27. Jan P-H, Jorn J (2005) AIM-ability improvement model
28. Koch AS (2005). Agile software development: Evaluating the methods for your organization. Artech House, Boston
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
30. Larman C (2004). Agile and iterative development. Pearson Education, Boston
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
32. Martin RC (2002). Agile software development, principles, patterns and practices. Prentice Hall, Englewood Cliffs
33. Newkirk JW and Martin RC (2001). Extreme programming in practice. Prentice Hall, Englewood Cliffs
34. Park R, Goethert W, Florac W (1996) Goal-driven software measurement-a guidebook, Software Engineering Institute, Carnegie Mellon
35. Pukinskis A (2005) 5 stumbling blocks for new corporate agile projects, the agile blog
36. Rosenberg D, Stephens M and Collins-Cope M (2005). Agile development with ICONIX process: People, process, and pragmatism. Apress, Berkeley
37. Rueping A (2003). Agile documentation: A pattern guide to producing lightweight documents for software projects. Wiley, New York
38. Schatz B and Abdelshafi I (2005). Primavera gets agile: A successful transition to agile development. Softw IEEE 22: 36-42
39. Schwaber K and Beedle M (2002). Agile Software Development with SUM. Prentice Hall, Englewood Cliffs
40. Sidky A, Arthur J (2006) Agile adoption process framework - indicators document, CORR - cs.SE/0612092
41. Spayd MK (2003) Evolving agile in the enterprise: Implementing XP on a grand scale, pp 60-70
42. Tabaka J (2005). Collaboration explained; facilitation skills for software project leaders. Addison-Wesley, Reading
43. Wake WC (2001). Extreme programming explored. Addison- Wesley Professional, Reading
44. Williams L and Kessler R (2002). Pair programming illuminated. Addison-Wesley Longman Publishing Co., Inc., Reading
45. Williams L, Kessler RR, Cunningham W and Jeffries R (2000). Strengthening the case for pair programming. Softw IEEE 17: 19-25