QA. We all know we need it, but quality takes time. How do we squeeze it into two-week sprints? Is a story really done if we haven’t finished QA? Do your Dev teams throw “code over the wall” to be tested in the next sprint? Or are your testers expected to test all your code in the last three Days of your Sprint? These are anti-patterns we see all the time in the Large Enterprise. In this presentation we will discuss how QA is handled - and mishandled when an Enterprises “adopt” Scrum. We will conclude with the best approaches to delivering potentially shippable code, in a quickly changing business world. This presentation will assume a basic understanding of agile principles.
In this presentation we will discuss how QA is handled - and mishandled. We will conclude with the best approaches to delivering production ready code in a lean, agile world. This presentation will assume a basic understanding of agile principles. This talk is not technical in nature. It is intended for those struggling with the transition from traditional QA enterprise teams - silos, testers report to a separate management structure - to QA in an Agile environment. We will discuss QA anti-patterns and how agile addresses them.
John Borys has developed Enterprise Java applications for 16 years in the Chicago Metropolitan area. He has consulted for small start-ups and Fortune 50 companies. Introduced to Agile in 2004 while working on a maintenance system for the F-22 Raptor Engine, he has been an agile Proponent ever since. During that time he has been an Agile Developer, Scrum Master, Technical Lead, Java Architect, and for the last four years, an Agile Coach.
He is currently with Accenture specializing in Agile Transformation in the Large Enterprise and teaching teams XP Fundamentals.
John is a Certified Scrum Professional and a Certified Scrum Master.More About John »