Nancy van Schooenderwoert
Nancy Van Schooenderwoert is an Agile Enterprise coach and founder of Lean-Agile Partners, Inc. She was one of the first to apply Agile methods to embedded systems development, as an engineer, manager, and consultant. She has led Agile change initiatives beyond software development in safety-critical, highly regulated industries, and coached clients in the art of Agile technical and management leadership. Nancy's experience spans embedded software and hardware development for applications in aerospace, factory automation, medical devices, defense systems, and financial services. She holds a bachelor's degree in Computer Engineering from Rochester Institute of Technology and is a contributor of articles and advisories for the Cutter IT Journal. Nancy has edited a column for the Agile Times, and served on the IEEE 1648 committee to define a standard for customers of agile teams. She has been a regular presenter at various Agile-related conferences since 2003, and also at the Embedded Systems conference. Her work in applying Agile methods to embedded systems has been referenced by Jim Shore, James Grenning, and Mary Poppendieck in their books. She speaks at numerous software professional gatherings worldwide, and is currently president of Greater Boston's premier Agile user group, Agile New England.
Track abstract - Keynote
No Bugs
This is a 12 minute "lightning talk"
Track abstract - Product Owners - G3
Embedded Storycrafting: Key to controlling Risk and Schedule
The game will be for 6 to 9 players, and up to 4 copies of the game will be run in parallel. Players move stories through work states (Design, Develop, Test for software, and Design, Layout, Fabrication, Test for hardware), followed by integration, QA, and Deployment states. Event cards are drawn to simulate realistic issues such as a defect in a custom chip, or a bottleneck in the Test group, etc. WIP limits are used to establish a "pull system", and teams create policies to alter the flows in order to optimize cycle time.
Players will make control charts, cumulative flow diagrams, and a financial cumulative revenue report as the game progresses. They will see in detail how to work all the key mechanisms of Kanban, plus these useful charting techniques.
