Here we will help you identify Top 4 Mistakes in a Project Plan
Microsoft Project is a project management software product, developed and sold by Microsoft. It is designed to assist a project manager in developing a schedule, assigning resources to tasks, tracking progress, managing the budget, and analyzing workloads.
A detailed Project Plan is the first document of reference and a saviour in managing ambiguity. Unfortunately, this is also an avenue where Project Managers could go wrong easily because of following awfully bad practices.
Projects often wind up taking longer (much longer) than planned and costing more than budgeted.
While no two projects are exactly the same, the issues that can affect — and potentially jeopardize — them are often quite similar. And even good project managers can make mistakes when wrangling a big, complex project — or when being bombarded with change requests.
Top 4 Mistakes in a Project Plan # 1 – Manually scheduled Tasks
This is the Number 1 mistake in a Project Plan.
Even if the duration of one single task is changed then the entire Project Plan should be automatically rebaselined to show you the new end date of a Project. If this is not the case then you may be using a few manually scheduled tasks.
Top 4 Mistakes in a Project Plan # 2 – Not Linking Tasks
Number 2 mistake in a Project Plan: A few Project Manager’s think that they can drive a Project Plan with constraints and relationships are not important.
Again in this case, if there is any change to the duration of one Critical Path Task then the Project Plan would not be updated to reflect the updated end dates
Top 4 Mistakes in a Project Plan # 3 – Indentation –
The number 3 Project Plan Mistake is the most obvious one!!!
In Microsoft Project, a summary task that is also called a parent task is a collection of subtasks that shows their combined information. A well indented Project Plan clearly demarcates the Phases and also Parent Tasks that have been identified by the Project Manager as having other tasks within itself.
Top 4 Mistakes in a Project Plan # 4 – Resources
Number 4 mistake on a Project Plan !!
Did you just notice a Project Plan with departments in the resources section? You need names against each activity!!!
This also means the project manager is not intending to use resource levelling in his Project Plan and no one would actually know if a resource is overbooked!!!
- Link Tasks – Always
- Indent Tasks for better understanding
- Auto Schedule all the Tasks
- Resources Should be assigned for all the Projects
Project creates budgets based on assignment work and resource rates. As resources are assigned to tasks and assignment work estimated, the program calculates the cost, equal to the work times the rate, which rolls up to the task level and then to any summary tasks and finally to the project level. Resource definitions (people, equipment and materials) can be shared between projects using a shared resource pool. Each resource can have its own calendar, which defines what days and shifts a resource is available.
Resource rates are used to calculate resource assignment costs which are rolled up and summarized at the resource level. Each resource can be assigned to multiple tasks in multiple plans and each task can be assigned multiple resources, and the application schedules task work based on the resource availability as defined in the resource calendars.
All resources can be defined in label without limit. Therefore, it cannot determine how many finished products can be produced with a given amount of raw materials. This makes Microsoft Project unsuitable for solving problems of available materials constrained production. Additional software is necessary to manage a complex facility that produces physical goods.