Scrum beyond software
Scrum can structure industrial work when needs evolve, technical unknowns are significant and teams must learn quickly.
What needs adapting
- A backlog focused on technical outcomes
- Sprints compatible with design and test cycles
- A review with industrial stakeholders
- A short, concrete retrospective
- A verifiable increment: prototype, test, package or decision
What must be preserved
The Scrum Guide defines Scrum as a lightweight framework based on transparency, inspection and adaptation. It does not prescribe detailed techniques for every profession: teams adapt their methods to context while retaining the framework's accountabilities, events and commitments.
For mechanical work, an increment may be a tested prototype, a validated function, an usable definition package or a robust technical decision. The Definition of Done makes the expected quality level explicit.