Agile Insights

Lesson #6: Hardware teams may initially struggle with Story writing because they tend to express non-functional requirements where Scrum expects Stories to describe deliverables.

Lesson #7: In hardware development, Product Owners often write only a minority of the Stories. Story-writing responsibility is distributed much more evenly across the Product

Lesson #8: Hardware organizations generally do not have a direct equivalent to the software Quality Assurance specialist who independently tests most Story deliverables. In many cases, the engineer who creates the deliverable is also the person best qualified to test it.