Don't be too hard for agile; How to go lean with hardware

We are at the beginning of the re-rise of tangible products, when the problem of unifying development lifecycles is fast becoming the biggest impediment of innovation. On one hand, speed can kill, and one should remember the importance of process for hardware- At the top of the list of challenges often faced by hardware Scrum teams is a demand for time. For one thing, delivering a functional piece of hardware to the customer after each iteration and then adapting the design to the customer’s changing specifications increases the cost of a project dramatically. When traditional methodologies often involve much less financial risk. A lack of modularity also makes it difficult to use Scrum: hardware often doesn’t have the modularity that makes dividing projects into small increments possible. But on the other hand - faster iteration flows to accelerate hardware development. Agile methodology makes it possible to improve upon an original hardware design without significantly increasing spending and time required. Agile’s positive, team-focused values create freedom to make mistakes, fostering more healthy risk-taking, less blame-shifting, and more reward in the long run. Are you up for this hard(ware) challenge? This talk will be all about rapid iteration with hardware: the Dos and the Don’ts, on how to do a series of hardware build-test-feedback-revise iterations and then continuing the cycle once again.