ABSTRACT
Objectives ◾ Discuss the three aspects of quality in the context of Agility-quality management, quality
assurance, and quality control (testing) ◾ Describe in detail the three aspects of quality in the corresponding process map within
Composite Agile Method and Strategy (CAMS) ◾ Discuss the application of formal quality techniques (walk-throughs, inspections, reviews,
and audits) together with relevant Agile practices (showcases, test harnesses, stand-up meetings) in composite Agile projects
◾ Outline the syntax, semantics, and aesthetic aspects of quality checks and the corresponding levels at which they are applied (artifacts, diagrams, models)
◾ Address the use of verification and validation (V&V) in the context of two Agile methodsExtreme programming (XP) and Scrum
◾ Outline the challenges of testing in an Agile project ◾ Discuss organization of testing (test plan, test design, and test cases) in projects ◾ Differentiate between functional (based on user stories) and technical (based on classes) test cases ◾ Highlight relevant testing standards such as International Software Testing Qualifications
Board (ISTQB) in the context of Agile ◾ Describe Agile metrics and measurements in Agile projects and their relationship to quality ◾ Highlight approaches to estimation based on metrics in Agile projects ◾ Present CAMS-based metrics corresponding to areas of work and roles within projects
Introduction is chapter discusses the quality aspect of composite Agile at both project and organizational levels. Agility, particularly through its values of collaboration and communication, makes a major contribution to the overall quality of a product. Agile values enable the users of the product to closely participate in its development. is, in turn, also results in enhanced expectation management. e quality discussion in this chapter provides a Composite Agile Method and Strategy (CAMS)-based perspective on quality. is CAMS perspective includes management of the quality function across the organization as a whole, application of quality assurance techniques within projects, estimation of effort and output through metrics, and testing the product as it is being developed. Quality is crucial to the success of any initiative-irrespective of the methodology being used. Quality is also not piecemeal-a small part of a product or, for that matter, of an organization cannot claim to be of high quality if the rest is not. erefore, quality can only be holistic in the way it gets applied in an organization.
