Software quality assurance in Scrum the need for concrete guidance on SQA strategies in meeting user expectations

Master Thesis

2013

Permanent link to this Item
Authors
Supervisors
Journal Title
Link to Journal
Journal ISSN
Volume Title
Publisher
Publisher

University of Cape Town

License
Series
Abstract
The purpose of this study is to identify and present the concerns of project stakeholders in relation to Software Quality Assurance (SQA) in a Scrum environment. Guided by the tenets of Classic Grounded Theory Methodology, this exploratory and inductive case study presents a broad range of SQA concepts related to the main concern of “Meeting User Expectations”. In trying to resolve the main concern, the Scrum project stakeholders alluded to lack of “Concrete Guidance” on SQA strategies, tools, and techniques in Scrum. The lack of concrete guidance in Scrum requires a development team to devise “Innovations” which may include “Adopting Practices” from other methodologies and carefully designing the “Process Structure” to accommodate the “Adopted Practices”, ensure “Continuous Improvement” of the process, and provide an environment for “Collaborative Ownership”. In addition to the “Need for Concrete Guidance”, the study reveals two other important concepts necessary for “Meeting User Expectations”: the “Need for Solid User Representation” and the “Need for Dedicated Testing”. While some Agile proponents claim that the Agile SQA practices are adequate on their own, the study reveals a number of challenges that impact on a team’s ability to meet user expectations when there is no dedicated tester in a Scrum environment.
Description

Includes abstract.


Includes abstract.

Reference:

Collections