There&#x27;s another hidden aspect:  <i>Be aware of dependencies.</i><p>When you have a series of dependencies (A -&gt; B -&gt; C) stacked against each other, once A is late, B and C are almost guaranteed to be late. If B is late too, C suffers even more and has little chance of being on time.<p>If you can lay out the tasks so that dependencies have slack between them so that lateness can be absorbed without shifting later tasks, you are more likely chance to hit deadlines and potentially complete the project on time. Or in more formal terms, track the Critical Path.<p>In practical terms, I would see this all the time commuting home in DC. I walked to the train to the bus to home. If I timed it perfectly, my commute was ~25 minutes. But if I couldn&#x27;t cross the street in time, I&#x27;d catch a later train which made for a later bus. Or a <i>slightly</i> later train would be a much later bus. When those variances stacked up, it could take an hour.