{"id":{"repo_id":"cape-town","oai_identifier":"oai:open.uct.ac.za:11427/5670"},"canonical_url":"https://search.dev.ndltd.org/etd/cape-town/oai:open.uct.ac.za:11427/5670","repository":{"repo_id":"cape-town","name":"University of Cape Town","base_url":"https://open.uct.ac.za/oai/request"},"display":{"title":"Software quality assurance in Scrum the need for concrete guidance on SQA strategies in meeting user expectations","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.","abstract_html":"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.","abstract_has_math":false,"creators":["Khalane, Tiisetso"],"institution":"Department of Information Systems","degree_name":null,"degree_level":null,"degree_discipline":null,"degree_department":null,"school":null,"contributors":[],"advisors":["Tanner, Maureen"],"committee_chairs":[],"committee_members":[],"year":2013,"date_issued":"2013","date_published":"2013","updated_at":"2026-07-22T22:22:49Z","subjects":[],"languages":["eng"],"rights":[],"rights_urls":[],"identifier_entries":[]},"links":{"outbound_url":"http://hdl.handle.net/11427/5670","outbound_label":"Handle","outbound_source":"dc:identifier.uri"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor.advisor","label":"Advisor","values":["Tanner, Maureen"]},{"key":"dc:creator","label":"Author","values":["Khalane, Tiisetso"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.accessioned","label":"Dc Date Accessioned","values":["2014-07-31T12:19:05Z"]},{"key":"dc:date.available","label":"Dc Date Available","values":["2014-07-31T12:19:05Z"]},{"key":"dc:date.issued","label":"Date","values":["2013"]},{"key":"dc:publisher.department","label":"Dc Publisher Department","values":["Department of Information Systems"]},{"key":"dc:publisher.institution","label":"Dc Publisher Institution","values":["University of Cape Town"]},{"key":"dc:type","label":"Dc Type","values":["Master Thesis"]},{"key":"dc:type.qualificationlevel","label":"Dc Type Qualificationlevel","values":["Masters"]},{"key":"dc:type.qualificationname","label":"Dc Type Qualificationname","values":["MCom"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language.iso","label":"Language (ISO)","values":["eng"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier.uri","label":"Identifier URI","values":["http://hdl.handle.net/11427/5670"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description","label":"Description","values":["Includes abstract."]},{"key":"dc:description.abstract","label":"Abstract","values":["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."]},{"key":"dc:title","label":"Title","values":["Software quality assurance in Scrum the need for concrete guidance on SQA strategies in meeting user expectations"]}]}],"canonical_facts":{"dc:contributor.advisor":["Tanner, Maureen"],"dc:creator":["Khalane, Tiisetso"],"dc:date.accessioned":["2014-07-31T12:19:05Z"],"dc:date.available":["2014-07-31T12:19:05Z"],"dc:date.issued":["2013"],"dc:description":["Includes abstract."],"dc:description.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."],"dc:identifier.uri":["http://hdl.handle.net/11427/5670"],"dc:language.iso":["eng"],"dc:publisher.department":["Department of Information Systems"],"dc:publisher.institution":["University of Cape Town"],"dc:title":["Software quality assurance in Scrum the need for concrete guidance on SQA strategies in meeting user expectations"],"dc:type":["Master Thesis"],"dc:type.qualificationlevel":["Masters"],"dc:type.qualificationname":["MCom"]},"updated_at":"2026-07-22T22:22:49Z"}