And to add a note here, when you have a table of tasks and dependencies you can make a critical path. Once you have a critical path, then you most likely be able to parallelize tasks and start naturally getting floats or slack times that you can use to avoid having to do crunching
Reposted from
David Gaider
What conflicts could there be, you ask? Dependencies, for one. "I can't do X until Y is done, but Y is someone else's job". Or scope. "We need 20 doodads but the sub-lead said they only have time to make 10, what now?". Even outright differences in vision. Big projects means room for a LOT of egos.
Comments