The key to successful adoption of any development methodology is a clear understanding of the roles and responsibilities of each team member. As agile continues its rapid adoption, it’s essential to define the role of QA in Scrum as concretely as we’ve defined the other team roles. Agile gives QA an opportunity for broader and deeper involvement in the software development lifecycle, enabling us better to ensure quality not only by finding defects, but also by preventing the introduction of defects in the first place. We can drive defect prevention by asking key questions during requirements definition, and building comprehensive acceptance criteria before implementation begins. This results in high quality development, testing, and story acceptance. Finally, to prevent the steady growth of technical debt, QA can help the team plan story points for fixing both known and unknown defects as part of every sprint. Join Karen to discuss prevention vs. detection in action…


Speaker:

Karen Wysopal, Hewlett Packard

Karen Ascheim Wysopal has been in software QA for over 20 years, as a tester, release manager, automation engineer, and 8 years as QA manager. She currently heads Quality & PMO for Hewlett Packard’s Software and Web Services organization, where she was a leader in the organization’s transition to Agile last year. Karen has presented at the Pacific Northwest Software Quality Conference. Her professional passions include building high functioning innovative teams from the ground up, and defining organizational processes that encompass a holistic approach to quality. She can’t seem to stop breaking software.