About the Presenter
Ken Pugh is a fellow consultant with Net Objectives (www.netobjectives.com). He helps companies transform into lean-agility through training and coaching. His particular interests are in communication (particularly effectively communicating requirements), delivering business value, and using lean principles to deliver high quality quickly. He also trains, mentors, and testifies on technology topics ranging from object-oriented design to Linux/Unix. He has written several programming books, including the 2006 Jolt Award winner, Prefactoring. His latest books are Lean-Agile Acceptance Test Driven Development: Better Software Through Collaboration. and Essential Skills For The Agile Developer. He has helped clients from London to Boston to Sydney to Beijing to Hyderabad. When not computing, he enjoys snowboarding, windsurfing, biking, and hiking the Appalachian Trail.
Defining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, developers and quality assurance experts alike. Many of the items living happily in our defect tracking systems were born of the difficulty we have in performing said activities. Acceptance Testing roots out these defects by reexamining the process we use to define the work to be done and how it is tested.
This session introduces acceptance testing; explains why it works; and outlines the different roles the team members play in the process. We will contrast acceptance testing with unit testing and show examples of how the process clarifies the work to be done.