In the first two posts of our scrum blog series you already got an insight into agile product management. This final part is about the application of the Scrum framework in the hardware sector.
The key principles which lead to the advantages of the framework remain the same – whether in software or hardware context:
- Progress and obstacles of a project are recorded regularly and are transparent to all.
- Project results and functionalities are delivered and evaluated regularly.
- Requirements are not defined once and for all, but are continuously adapted.
To achieve all of that, Scrum structures tasks into smaller, less complex components: Increments.
Here lies the main difference, because for hardware products the duration of a sprint can often not be sufficient to deliver an (possibly releasable) increment. Without these increments no feedback can be received and thus the principle fails. That’s why it’s important to set reasonable sprint goals, e.g. a CAD sketch or a cardboard prototype can be valuable increments.