Scrum for Hardware
Scrum inventor Jeff Sutherland and WikiSpeed founder Joe Justice discuss eXtreme Manufacturing and how you can implement test-driven hardware development using the Scrum framework. Learn how WIKISPEED invented a new manufacturing process that can shorten time-to-market, reduce labor costs and spur innovation.
Upon completion you will:
- Be able to define Scrum for Hardware
- Understand the 3 underpinnings of Scrum for Hardware
- Understand Component parts of a Scrum Organization
- Understand the basic principles of XP Engineering that are used in Scrum for Hardware
- How object-oriented architecture (OOA) is leveraged in Scrum for Hardware
- Be able to articulate the benefits of XM
- Have a basic understanding of how to improve your development process
- Qualify for Scrum Alliance SEUs and PMI PDUs. See FAQ for details
eXtreme Manufacturing Overview:
The term eXtreme Manufacturing (XM) was coined by Team WIKISPEED, a non-profit car manufacturer, to describe how it manufactures automobiles combining the Scrum framework, Object-Oriented architecture and eXtreme Programming (XP). Blending these three practices, WIKISPEED invented a new manufacturing process that can shorten time-to-market, reduce labor costs and spur innovation. eXtreme Manufacturing borrows the basic Agile principles from Scrum. First and foremost, it leverages small, cross-functional Teams, which have a Product Owner and Scrum Master. XM is structured around Sprints to help develop functionality in vertical slices that build overtime. Like Scrum, XM makes development transparent through tools like a Scrum board and a product backlog. It also borrows the concept of tracking process improvements by using Velocity. And, most importantly, it relies on the Lean concept of continuous improvement by employing Sprint Retrospectives and the Happiness Metric. Scrum provides the basic structure for XM.
View and Download Class Slides
Read more on XP
XM also borrows pairing from XP: two people work together on every job. This allows a small team to swarm on a particular task, while cross-training employees and building quality control into the manufacturing process. Pairing also reduces dependency on different skill sets.
XM uses Test Driven Development, or TDD, to dramatically speed up time-to-market and lower development costs. Team WIKISPEED for example used real-time crash test data to build a computer program that simulates an actual crash test. They were able to save millions of dollars in crash tests by simulating them each Sprint. After a number of Sprints accumulating data, WIKISPEED pays for another physical test. The new information is then used to up-date the computer simulation. This lowers material costs since WIKISPEED doesn’t have to destroy a car each time they want to test it and it reduces production costs because crash tests are expensive.
Read more on OOA
Explore ScrumLab Prime
Are you ready to advance your Scrum knowledge? Prime members enjoy unrestricted access to all our webinars and advanced Scrum topics.