4 ms·
If you’re doing software product work I’m totally with you on small impactful iterations. When you’re delivering a hardware product this is a lot more difficult
by jon-wood 6y ago
If you’re doing software product work I’m totally with you on small impactful iterations. When you’re delivering a hardware product this is a lot more difficult to pull off.
There are definitely ways to take an agile approach to hardware development, even if you’re working with an OEM, but the outcomes look a lot more like waterfall than your typical Agile with a big A people are comfortable with. The outcome of your iterations are long specification documents (which you’ve already got feedback on from your OEM), and a lot more detail than you’d typically go into development for on the software side since it has to integrate with the actual hardware.
- anotheryou 6y agoRight, I also like waterfall for bigger projects with fix requirements at the end. In fact I also mix agile with waterfall. So much easier to keep adjusting your requirements for a few milestones ahead than to scramble together stories to fill the next sprint every other week.