You Can’t Scrum Hardware
Taking On An Assumption
“The rules of the game in new product development are changing. Many companies have discovered that it takes more than the accepted basics of high quality, low cost, and differentiation to excel in today’s competitive market. It also takes speed and flexibility.”
Takeuchi and Nonaka wrote this paragraph back in 1986, and within software development it inspired people to develop Scrum as a way to develop software faster, better and cheaper. Over the last 15 years the Scrum approach has proven to work in many different projects. And it is proven that Scrum is “simple, not easy”.
Hardware (like cars, photo copiers and combine harvesters) cannot be developed with Scrum, that is the general opinion. The plan-do-inspect cycle of just 2 weeks is considered too short, teams cannot deliver an inspectable next version of the product under development that quickly. Experience proves this assumption wrong.
In my webinar, I will explain the core of Scrum4HW™ and give real life examples of how these components can be implemented. Examples are taken from small (Wikispeed cars) and large (Saab Gripen) deliveries. I will also show how suppliers have changed and can accommodate fast turn-around needs. Regulatory requirements in car manufacturing fit in the Scrum framework.
Fifteen years ago I had discussions with many people who were convinced that big software projects, or high risk software projects, or software package implementations wouldn’t fit in a Scrum framework. Nowadays projects with 1,500 participants have shown to be successful. Government agencies are firm believers in Scrum. Just like critics in software were proven wrong, so will critics in Scrum for hardware be prove wrong! Join me on June 2nd for the webinar.