The quest for system testing in Scrum

The Scrum theory teaches us that after each sprint “a potentially shippable product/system” needs to be delivered to the business. Personal experience has shown that this is scarcely possible or even not possible at all in the case of newly built products or systems, especially in projects which include hardware. Usually the hardware is not available at the start of the software project and changes in the hardware are not realized within a single sprint. Adjusting hardware usually takes longer than one sprint because it requires, for example, trial runs and engineering samples before the final hardware becomes available.