Extreme programming and agile software development methodologies

Information Systems Management

Volumn 21, Issue 3, 2004, Pages 41-52

  Lindstrom, Lowell ^a   Jeffries, Ron ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING; INFORMATION SERVICES; PERSONNEL; PROJECT MANAGEMENT; RESOURCE ALLOCATION; RISK MANAGEMENT; TELECOMMUNICATION;

AGILE SOFTWARE DEVELOPMENT; EXTREME PROGRAMMING; PROGRAMMERS;

COMPUTER SOFTWARE;

EID: 3042813738     PISSN: 10580530     EISSN: None     Source Type: Journal    
DOI: 10.1201/1078/44432.21.3.20040601/82476.7     Document Type: Article

References (11)

1. Beck, K., 2000. “ Extreme Programming Explained ”. Addison Wesley Longman.
2. www.agilemanifesto.org
3. Sliwa, C., March 14 2002. “ Agile Programming Techniques Spark Interest ”. March 14, Computerworld.com.
4. Jeffries, R., 2001. “ Extreme Programming Installed ”. 172Addison Wesley Longman.
5. It is likely true that skilled practitioners of most methods are guided by a set of values, perhaps dictated by the culture of the organization, perhaps dictated by the leadership of the team. It is the expression of the values as integral to the practices that makes XP unique
6. Schwaber, K., and Beedle, M., 2002. Agile Software Development with Scrum, Prentice Hall.
7. Poppendieck, Mary. April 2003. Lean Development:A Toolkit for Software Development Managers, April, Addison-Wesley. to be published
8. Thomsett, R., 2002. Radical Project Management, Prentice Hall.
9. Fowler, M., 1999. Refactoring:Improving the Design of Existing Code, Addison-Wesley.
10. Martin, R., 2003. Agile Software Development:Principles, Patterns, and Practices, Pearson Education. For more information on good software design principles and their application on agile software projects, see
11. Kerth, N., 2001. Project Retrospectives, Dorsett House.