Agile Software Development Quality Assurance: Agile Project Management, Quality Metrics, and Methodologies

Agile Software Development Quality Assurance: Agile Project Management, Quality Metrics, and Methodologies

J. Kile (IBM Corporation, USA)
Copyright: © 2007 |Pages: 20
DOI: 10.4018/978-1-59904-216-9.ch010
OnDemand PDF Download:
$37.50

Abstract

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

Complete Chapter List

Search this Book:
Reset