This preview shows page 1. Sign up to view the full content.
Unformatted text preview: se that are fairly likely.
Identify project risks, and develop contingencies to deal with them if they occur.
• Begin by looking at the purpose of doing whatever is to be done. Develop a problem statement. All
actions in an organization should be taken to achieve a result, that is, to solve a problem. Be careful
here to identify what the end user really needs to solve the problem. Sometimes a solution is developed
that the project team thinks is right for the client but that is never used, resulting in significant waste to
“Consider the little mouse, how sagacious an animal it is which never entrusts its life to one hole only.”
—PLAUTUS, 254-184 B.C.
www.erpvn.net • Use the Work Breakdown Structure (discussed in Chapter 4) to divide the work into smaller chunks
for which you can develop accurate estimates of duration, cost, and resource requirements. PROJECT PLANNING STEPS
The basic steps in planning are:
1. Define the problem to be solved by the project.
2. Develop a mission statement, followed by statements of major objectives.
Be sure the project really satisfies the customer’s needs, rather than being what the team thinks the customer
3. Develop a project strategy that will meet all project objectives.
4. Write a scope statement to define project boundaries (what will and will not be done).
5. Develop a Work Breakdown Structure (WBS).
6. Using the WBS, estimate activity durations, resource requirements, and costs (as appropriate for
7. Prepare the project master schedule and budget.
8. Decide on the project organization structure—whether matrix or hierarchical (if you are free to
9. Set up the project notebook.
10. Get the plan signed off by all project stakeholders. QUESTIONS FOR REVIEW
1. If someone tells you there is too little time to plan a project, how would you defend your
conviction that planning is necessary?
d. Tell the person that a project plan will save time in the long run.
Prove that without a plan, there can be no control.
Both a and b.
Only b. 2. What is the difference between strategy and tactics?
a. Strategy is an overall approach to a project. Tactics are specific steps taken to implement
b. Strategy is the political approach taken to manage a project. Tactics are the moves you make
to beat a competitor.
c. Both a and b.
3. Why is it necessary to get people to participate in planning a project? Why can’t the project
manager just do it for them?
a. If the project manager plans the project and anything goes wrong, everyone will blame him
or her for all the problems.
b. Without participation, people are not committed to a plan.
c. Participation in planning helps ensure that things aren’t forgotten and that estimates are
d. All of the above.
e. Only c.
4. Of what value is a project notebook?
www.erpvn.net a. It allows you to protect yourself from people who change their minds about what they want once the project is started....
View Full Document
This document was uploaded on 09/27/2013.
- Fall '13