10 Myths on software project planning

First Myth
I have a detailed technical requirements document, I don’t think I need anything else, I should create a plan in MS project directly now.

Don’t be in hurry to develop a project plan, there are several other activities which need to be done before you create schedule in MS project.

Once you have a requirements document, you need following steps to be followed before you develop a plan/schedule in MS project:
a. You need to brain storm on the document with your team mates and need to ask right questions from right person to define a detailed scope.
b. Not only concentrate on functional requirements but also consider non-functional requirements while you define your scope.
c. After you defined your scope, prepare a WBS (Work Breakdown Structure) with the help of work packages. Also divide your work packages to the extent (activities) which can be assigned and planned properly. You can either make this WBS and activity list manually or, in MS project.
d. There are also other activities/techniques (Activity Sequencing, Activity Resource Estimating, Resource leveling, etc.) which can be done depending upon the need and kind of project.
e. Don’t forget to review the plan with your team members before you baseline the plan.


Second Myth
Created my plan in MS project, all my responsibilities of project planning have been completed.

Even if you develop a good plan using standard techniques, your duty is continued till the time the project is closed.
a. You need to review your plan frequently for updates, new requirements, risks, dependencies to maintain your plan for better management of your project.
b. Frequent review exercise will not only give you a preventive environment but also give you proper time to plan your corrective actions.
c. Your effort in each process group (Initiation, Planning, Execution, Monitoring & Control and Closing process group) is equally important for you and you can not get success if you skip any or, give small weightage to any process group. You need to review your plan/schedule in each process group and need to take corrective actions in case of any mishappening.
d. Even if you have developed a very good plan, you can not get success if you have not executed and controlled it well.
e. Be open to any change in plan, but review the change(s) properly before you go for change. Also, use your reserves at right places.