DAVID G. ULLMAN
Design Process Videos
Short presentations on engineering design best practices.
Thirteen Reasons Why Designing Hardware Using Agile/Scrum is More Challenging then Designing Software
The Scrum framework is widely used to develop software, but not so with hardware. It can be, should be, and is beginning to be done with success similar to that seen with software. But, scrum for hardware design is more challenging than designing software. This video discusses thirteen reasons why it is more difficult. (7:52)
Planned and Agile Hardware Requirements Development
Good product planning demands requirements set up-front while scrum, an agile framework tells us to develop requirements on the fly. Which is best? Is a mix the right way? If so, how do you determine how much to plan and how much to lease? This series of four short videos answers these questions.
In traditional product planning, requirements are set at the beginning of the project, while with scrum, an agile framework, requirements develop concurrently during the project. Which is best? Does a mix of planned and agile requirements development work well? If so, how do you determine how much to plan and how much to develop during design? (7:12)
The second video focuses on how to develop requirements upfront as part of traditional product planning. AIn this video I will introduce Quality Function Deployment often called QFD or house of quality, a widely used and mature tool that supports the conversations in a structured manner during product planning. (7:10)
Can users’ stories, a scrum framework tool widely used in software design to develop requirements on the fly, agilely, be used to help develop hardware requirements? In this video, I will answer this question.(7:54)
What is best, developing hardware design requirements upfront as part of planning, agilely during the design process, or a hybrid of them both? This video explores how and when to develop hardware requirements. (6:52)