Agile + DevOps West 2020 Tutorial: Friction Lab


Tuesday, June 9, 2020 - 8:30am to 4:30pm

Friction Lab

Add to calendar

You have great software engineers. They work on autonomous product teams that deliver frequently. The products are doing well. But—there is always a But. Things could be better. Something is frustrating team members or disappointing customers or slowing things down. What is it? Friction. No matter how well things are going, there will always be friction. Consumers experience friction when using your product. Friction delays a team's response to a product request. Friction makes the code difficult to change. Differing expectations create friction among team members. Competing goals create friction between teams. Learn to identify the largest source of friction for those who attend—the biggest thing that keeps team members from doing their best work—and come up with a plan for reducing that source of friction. Focus on patterns for reducing friction that can be used again—and again—to identify and address points of friction on an on-going basis.

Mary Poppendieck
Poppendieck, LLC

Mary Poppendieck’s first job was programming the #2 Electronic Switching System at Bell Labs in 1967. She has worked on systems that control roll-goods processes, interpret digitized images, and support statistical process control. She spearheaded the implementation of a just-in-time production system and led new product development teams, commercializing products ranging from digital controllers to lighting systems. Mary is a popular writer and speaker and co-author of the book Lean Software Development: An Agile Toolkit, which was awarded the Software Development Productivity Award in 2004. A sequel, Implementing Lean Software Development: From Concept to Cash, was published in 2006. A third book, Leading Lean Software Development: Results are Not the Point, was published in November 2009, and a fourth book, The Lean Mindset: Ask the Right Questions, was published in 2013.

Tom Poppendieck

Tom Poppendieck has 25 years of experience in computing including eight years of work with object technology. His modeling and mentoring skills are rooted in his experience as a physics professor. His early work was in IT infrastructure, product development, and manufacturing support, and evolved to consulting project assignments in healthcare, logistics, mortgage banking, and travel services. Tom holds a Ph.D. in Physics and has taught physics for ten years. He is the co-author of four books: Lean Software Development, 2003, Implementing Lean Software Development, 2006, Leading Lean Software Development, 2009, and Lean Mindset, 2013.