3 ms·
If you're going to analyze a process you have to look at all of the steps involved, including waiting time, re-work or going backwards in the process/iterating,
by mattbrewsbytes 1y ago
If you're going to analyze a process you have to look at all of the steps involved, including waiting time, re-work or going backwards in the process/iterating, as well as the time to do the tasks. They all matter in the economics of delivery of working software.
The slowest part is going to be the parts involving humans communicating things to each other and iterating on the requirements and designs and the waiting times in between. The technical coding or generation of assets does not take that much time in the overall process.
- breckenedge 1y agoYea, it shouldn't. However many PMs I've worked with over the last decade seem to think that development is the slowest part of the process -- that requirements need to be completely understood and designs completely buttoned up -- before major software work begins, because of this misconception that it's a slow and risky process. Now there's even less evidence to back up that misconception since GenAI can be writing the code in parallel to all the communication.