Peak Effort
- Question every requirement; have the name of the person who made it.
- Delete any part or process you can do without. Restore 10% back later if necessary.
- Simplify & optimize the remaining parts/processes.
- Accelerate the cycle time.
- Automate only after doing all the above, and the bugs have been shaken out.
Elon Musk’s Business Development Algorithm (essentially unquestioned)
I learned from a week-long class in quality assurance that the largest inefficiency in software development is in unclear requirements. Dr Gaussman said that it takes 100 times more manpower to find and fix a bug than to prevent it in the first place by rigorously analyzing requirements. Yet from my experience, there were so much pressure to hurry through the requirements phase.
Yes, awareness of the intention should always come first, no matter how long it takes.