Project managers that are not as familiar with using tools like MS Project to create a project schedule often “dive in head first” creating their project schedule. These project managers open a new file, start furiously loading project tasks, and the project schedule evolves as project planning progresses. After the project schedule baseline is established, and project execution begins, these project managers begin the weekly battle to maintain the project schedule in a manner that keeps it close to reflecting reality. Some of the telltale signs that your schedule is difficult to maintain include: You change the dependency on a task and the dates do not change You extend the duration and the work hours do not change You add a new resource and the dates change unexpectedly Your schedule shows people working on Thanksgiving and Christmas Durations are displayed in hours, and work is displayed in minutes I was working with a project manager whose schedule had become so difficult to maintain that he declared that his “tool had become compromised”. This created much frustration for the project manager, but the even worse result was that he was not sure that the milestone commitments established in the schedule were correct or achievable (and he did not know how to fix it). Obviously, how well the WBS is organized has a significant impact on the ability to effectively and efficiently maintain the schedule throughout the project life cycle.