Saturday 22nd February, 2014
10:00am to 10:45am
In most organizations, developers may review each other's code, product managers may review each other's stories and quality teams may review each other's test plans. But what if the extended team reviewed these materials cross-functionally so that quality teams reviewed (or at least had visibility into) user stories â€“ and testers saw user stories? In today's fast-paced Agile world, teams have to collaborate in order to be successful. Mark Hammer describes how peer review practices can succeed where more cumbersome methods fail. He uses concrete examples of teams that have embraced cross-functional peer review of user stories, code and test plans in an Agile environment, and how this has resulted in higher quality products developed faster. Mark offers tips on the mechanics of tool-based code reviews and compares five common styles of review, presenting research from Karl Wiegers, Frank W. Blakely, Mark E. Boles and others. He also looks at real-world examples including that of a customer who made the changes the research suggests, and reveals results, which are impressive. Attendees leave with an understanding of how cross-functional peer review can improve the performance of individual members of the extended product development team, including product management and testing team as well as their teams.
Interested in dev quality @SmartBear. Also, ed tech, cycling, Irish poetry, German soccer, and any country's beer. bio from Twitter
Sign in to add slides, notes or videos to this session