Before learning and adopting best practices for project management, developing a project schedule was a pain. I used to grab the project proposal and other available documents and then spent several hours (days) behind my computer working on the MS Project. No matter how much time I dedicated or how focused I was, the outcome was never detailed or comprehensive enough.
PMD Pro made me understand that there are many steps prior to the scheduled development, such as the Logframe review, WBS development, sequencing activities, estimating resources and duration, and establishing the critical path, to finally develop the project schedule.However, I still struggled to understand why I needed to follow all these steps, one by one, instead of simply applying their techniques at once. After all, when thinking on a task or set of activities, our mind naturally assembles all aspects at the same time: when task will start and end, the required resources, who will be responsible for it, etc.
Here are a few reasons why following these five steps is crucial to develop a more accurate and comprehensive project schedule: