What agile teams think of agile principles

Communications of the ACM

Volumn 55, Issue 4, 2012, Pages 71-76

  Williams, Laurie ^a  

^a North Carolina State University   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

AGILE DEVELOPMENT; AGILE TEAMS; BUSINESS VALUE; HIGH-QUALITY SOFTWARE; NON-FUNCTIONAL REQUIREMENTS; NORTH CAROLINA STATE UNIVERSITY; SOFTWARE ENGINEERS; SOFTWARE INDUSTRY;

ENGINEERS; SOFTWARE TESTING;

SOFTWARE ENGINEERING;

EID: 84861150197     PISSN: 00010782     EISSN: 15577317     Source Type: Journal    
DOI: 10.1145/2133806.2133823     Document Type: Conference Paper

References (11)

1. Beck, K. Extreme Programming Explained: Embrace Change, Second Edition. Addison-Wesley, Reading, MA, 2005.
2. Boehm, B. and Turner, R. Using risk to balance agile and plan-driven methods. IEEE Computer 36, 6 (June 2003), 57-66.
3. Boehm, B.W. Software Engineering Economics. Prentice-Hall, Inc., Englewood Cliffs, NJ, 1981.
4. Cockburn, A. Agile Software Development. Addison Wesley Longman, 2001.
5. Grenning, J. Planning Poker or How to Avoid Analysis Paralysis while Release Planning, 2002; http://renaissancesoftware. net/files/articles/ PlanningPoker-v1.1.pdf
6. Highsmith, J. Adaptive Software Development. Dorset House, New York, 1999.
7. Kniberg, H. and Skarin, M. Kanban and Scrum: Making the Most of Both. C4Media, Lexington, KY, 2010.
8. Palmer, S.R. and Felsing, J.M. A Practical Guide to Feature-Driven Development. Prentice Hall PTR, Upper Saddle River, NJ, 2002.
9. Poppendieck, M. and Poppendieck, T. Lean Software Development. Addison Wesley, Boston, 2003.
10. Schwaber, K. and Beedle, M. Agile Software Development with SCRUM. Prentice-Hall, Upper Saddle River, NJ, 2002.
11. Stapleton, J. DSDM: The Method in Practice, Second Edition. Addison Wesley Longman, 2003.