3 ms·
How about in a cyclical project start -> project release process? I am not referring to "crunch time" where you realize everything is broken and your schedule
by sliverstorm 15y ago
How about in a cyclical project start -> project release process?
I am not referring to "crunch time" where you realize everything is broken and your schedule was unrealistic; rather, many projects I have participated in have an escalating work load as you near release, because a lot of the work simply cannot be done before previous stages are completed.
Unless you are a large entity that can heavily "pipeline" by running 10 or 20 projects at once, and shuffle people around as a project's workload changes, to avoid ever working overtime you'd need to either have to hire too many employees, or hire/fire regularly. Not entirely dissimilar to trying to balance a server cluster with load spikes.
- danielharan 15y agoWork that can't be done because of dependencies, long release cycles instead of incremental delivery, planned escalating work load... What part of that do you think is NOT broken?
- sliverstorm 15y agoIt may not be the romantic ideal, but I don't see the fix. Try as you might, some work has dependency trees. About all I can think of is over-hiring, or release cycles could be extended, but for us TTM is pretty sensitive.