3 ms·
Shorter project sprints came about to try to fix the problem of project failure. Failure to create a loop that feeds discoveries in to a project's knowledge, an
by onion2k 11y ago
Shorter project sprints came about to try to fix the problem of project failure. Failure to create a loop that feeds discoveries in to a project's knowledge, and to communicate knowledge between teams is exactly what makes projects come to catastrophic ends, and that's what the shorter cycle time attempts to correct.
The fact the product benefits from faster innovation is a function of more efficiently sharing knowledge and data, not spending less time on individual components.
Designing and testing an engine can be done in an agile style. There's nothing intrinsically "software only" about the methodology.
NB: I ran a startup that made software to manage requirements in big projects. I've spent lots of time thinking about different ways to manage things. Including how not to, but that was after we failed.
- ams6110 11y agoYes it is intrinsically software-only. When a software test fails you fix the bug and run it again. When a jet engine test fails you just blew up a $10M prototype.
- onion2k 11y agoA software test is equivalent to a testing small part in an engine design. The cost of failure is low. The cost of a full production test in an engine design is clear, but it's the equivalent of a product handover and acceptance testing in software. The cost of failing that test could well run to millions of dollars. The only difference for a SaaS startup is that they're their own customer for product development (in the sense that they build and test in-house rather than someone else paying them to build a product). The cost of failure is still there, it's not measured.