Agile for Hardware, Engineering, Manufacturing, Product Development, or however you call it. It is time to do it better.

  • Trying to move from temporary project teams to stable teams? 
  • Trouble with finding your approach to incremental development? 
  • Is your team unable to deliver anything of value in a short learning cycle?
 
Sign up for practical and pragmatic approaches to contextualize Agile principles for your own context . Don't miss out!

 

The name and email address shared via this form will only be used to inform you about webinars, articles, and information regarding the book about the use of Agile in hardware contexts.

Previous newsletters

Frequently asked questions

What is the book about?

As we have had the opportunity to collaborate with various teams, departments, and organizations in 'finding' their Agile way of working, we have noticed there is very limited information shared on the use of Agile in the context of hardware development. We thought, we need to change this, and perform our part in sharing the tips and tricks from our experiences and mistakes. 

Is the use of Agile in hardware companies common?

As a matter of fact, quite a considerable amount of organizations developing physical products have been experimenting with or are using their interpretation of Agile. We have noticed that the companies we have been working with, or people from these companies we have been talking to, have been careful with sharing their experiences. 

We therefore thought; how about sharing our experiences, examples, and the published material which deserves to help a larger audience. 

Why focussing on engineers?

We believe that real change starts with the person who does the work. We focused on the engineer searching for ways to contextualize an alternative way of working using the proven principles written out in the Agile Manifesto. And after talking with hundreds engineers, we noticed their appetite for pragmatic and practical tips and tricks, ready to try out. 

Does the book explain a framework?

No. The book does not contain a framework, as we believe we have insufficient data which proves the applicability of a single framework in the myriad of context we now call 'hardware'. The contextual constraints amongst an established automotive company are so much different than the constraints of a company developing high volume electrical supplies for domestic use. Let alone industries such as maritime machinery, telecommunication, medical devices, and semiconductors. However, considerations to contextualize an Agile principle might be reusable, and hence; the book is focussing on the application of Agile principles in the context of physical product design.

What are you going to use our details for?

As mentioned, your name and email address will only be used to inform you about webinars, articles, and information regarding the book. No spam. No upselling. No annoyance. Promise!