Managing vs. Reporting

Is the project plan thorough enough and the project schedule detailed enough that they can be actively used to keep the project headed in the right direction?  Are the plan and schedule developed in such a way that they can flex with contigencies that materialize?

Small projects can succeed through sheer force of will and a little luck. Medium and large projects require effective planning and scheduling.

That means the project schedule has to be used actively, not just as a progress reporting tool. 

Often unanticipated slippages result from project schedules that are not sufficiently broken down into sub-tasks. Tasks bog down waiting for undocumented steps to be completed and the project slips.

Usually the problem gets compounded because there is not enough detail in the project schedule and plan to allow mitigating steps to be taken quickly enough to offset the delays.

A good project schedule is a tool not just for reporting, but for actively maintaining maximum control of the project.

Are there enough "early warning" tasks in the project schedule at points where sub-task slippages can be offset by compensating actions?

Are the project high-risk tasks identified in the plan and schedule? 

Does the planning include alternate schedule and work options for high-risk tasks and for task estimates that are not truly firm? 

Have schedule check-points been set at points in the project where project recalibration can be most effectively done if there are significant problems?

These are some of the many questions that must be asked in examining project schedules and plans.

People usually don't plan to fail, they simply fail to plan well enough.

To find out more about how RBCS can help you with security project plans and schedules, call us today at 949-831-6788!