Thursday, 17 May 2012 06:00

10 Steps to Creating a Project Plan

Written by  Elizabeth and Richard Larson
Rate this item
(98 votes)

Feature May16 40432452 XSOne of the critical factors for project success is having a well-developed project plan. This article provides a 10-step approach to creating the project plan, not only showing how it provides a roadmap for project managers to follow, but also exploring why it is the project manager's premier communications and control tool throughout the project.

Step 1: Explain the project plan to key stakeholders and discuss its key components. One of the most misunderstood terms in project management, the project plan is a set of living documents that can be expected to change over the life of the project. Like a roadmap, it provides the direction for the project. And like the traveler, the project manager needs to set the course for the project, which in project management terms means creating the project plan. Just as a driver may encounter road construction or new routes to the final destination, the project manager may need to correct the project course as well.

A common misconception is that the plan equates to the project timeline, which is only one of the many components of the plan. The project plan is the major work product from the entire planning process, so it contains all the planning documents for the project.

Typically many of the project's key stakeholders, that is those affected by both the project and the project's end result, do not fully understand the nature of the project plan. Since one of the most important and difficult aspects of project management is getting commitment and buying, the first step is to explain the planning process and the project plan to all key stakeholders. It is essential for them to understand the importance of this set of documents and to be familiar with its content, since they will be asked to review and approve the documents that pertain to them.

Components of the Project Plan Include:

Baselines. Baselines are sometimes called performance measures, because the performance of the entire project is measured against them. They are the project's three approved starting points and include the scope, schedule, and cost baselines. These provide the 'stakes in the ground.' That is, they are used to determine whether or not the project is on track, during the execution of the project.

Baseline management plans. These plans include documentation on how variances to the baselines will be handled throughout the project. Each project baseline will need to be reviewed and managed. A result of this process may include the need to do additional planning, with the possibility that the baseline(s) will change. Project management plans document what the project team will do when variances to the baselines occur, including what process will be followed, who will be notified, how the changes will be funded, etc.

Other work products from the planning process. These include a risk management plan, a quality plan, a procurement plan, a staffing plan, and a communications plan.

Step 2: Define roles and responsibilities. Not all key stakeholders will review all documents, so it is necessary to determine who on the project needs to approve which parts of the plan. Some of the key players are:

  • Project sponsor, who owns and funds the entire project. Sponsors need to review and approve all aspects of the plan.
  • Designated business experts, who will define their requirements for the end product. They need to help develop the scope baseline and approve the documents relating to scope. They will be quite interested in the timeline as well.
  • Project manager, who creates, executes, and controls the project plan. Since project managers build the plan, they do not need to approve it.
  • Project team, who build the end product. The team needs to participate in the development of many aspects of the plan, such as identifying risks, quality, and design issues, but the team does not usually approve it.
  • End users, who use the end product. They too, need to participate in the development of the plan, and review the plan, but rarely do they actually need to sign off.
  • Others, such as auditors, quality and risk analysts, procurement specialists, and so on may also participate on the project. They may need to approve the parts that pertain to them, such as the Quality or Procurement plan.

Step 3: Hold a kickoff meeting. The kickoff meeting is an effective way to bring stakeholders together to discuss the project. It is an effective way to initiate the planning process. It can be used to start building trust among the team members and ensure that everyone's idea are taken into account. Kickoff meetings also demonstrate commitment from the sponsor for the project. Here are some of the topics that might be included in a kickoff meeting:

  • Business vision and strategy (from sponsor)
  • Project vision (from sponsor)
  • Roles and responsibilities
  • Team building
  • Team commitments
  • How team makes decisions
  • Ground rules
  • How large the group should be and whether sub-groups are necessary

Step 4: Develop a Scope Statement. The Scope Statement is arguably the most important document in the project plan. It's the foundation for the rest of the project. It describes the project and is used to get common agreement among the stakeholders about the scope. The Scope Statement clearly describes what the outcome of the project will be. It is the basis for getting the buy-in and agreement from the sponsor and other stakeholders and decreases the chances of miscommunication. This document will most likely grow and change with the life of the project. The Scope Statement should include:

  • Business need and business problem
  • Project objectives, stating what will occur within the project to solve the business problem
  • Benefits of completing the project, as well as the project justification
  • Project scope, stated as which deliverables will be included and excluded from the project.
  • Key milestones, the approach, and other components as dictated by the size and nature of the project.

It can be treated like a contract between the project manager and sponsor, one that can only be changed with sponsor approval.

Step 5: Develop scope baseline. Once the deliverables are confirmed in the Scope Statement, they need to be developed into a work breakdown structure (WBS), which is a decomposition of all the deliverables in the project. This deliverable WBS forms the scope baseline and has these elements:

  • Identifies all the deliverables produced on the project, and therefore, identifies all the work to be done.
  • Takes large deliverables and breaks them into a hierarchy of smaller deliverables. That is, each deliverable starts at a high level and is broken into subsequently lower and lower levels of detail.
  • The lowest level is called a "work package" and can be numbered to correspond to activities and tasks.

The WBS is often thought of as a task breakdown, but activities and tasks are a separate breakdown, identified in the next step.

Step 6: Develop the schedule and cost baselines. Here are the steps involved in developing the schedule and cost baselines.

  1. Identify activities and tasks needed to produce each of the work packages, creating a WBS of tasks.
  2. Identify resources for each task, if known.
  3. Estimate how long it will take to complete each task.
  4. Estimate cost of each task, using an average hourly rate for each resource.
  5. Consider resource constraints, or how much time each resource can realistically devoted to this project.
  6. Determine which tasks are dependent on other tasks, and develop critical path.
  7. Develop schedule, which is a calendarization of all the tasks and estimates. It shows by chosen time period (week, month, quarter, or year) which resource is doing which tasks, how much time they are expected to spend on each task, and when each task is scheduled to begin and end.
  8. Develop the cost baseline, which is a time-phased budget, or cost by time period.

This process is not a one-time effort. Throughout the project you will most likely be adding to repeating some or all of these steps.

Step 7: Create baseline management plans. Once the scope, schedule, and cost baselines have been established, you can create the steps the team will take to manage variances to these plans. All these management plans usually include a review and approval process for modifying the baselines. Different approval levels are usually needed for different types of changes. In addition, not all new requests will result in changes to the scope, schedule, or budget, but a process is needed to study all new requests to determine their impact to the project.

Step 8: Develop the staffing plan. The staffing plan is a chart that shows the time periods, usually month, quarter, year, that each resource will come onto and leave the project. It is similar to other project management charts, like a Gantt chart, but does not show tasks, estimates, begin and end dates, or the critical path. It shows only the time period and resource and the length of time that resource is expected to remain on the project.

Step 9: Analyze project quality and risks.
Project Quality: Project quality consists of ensuring that the end product not only meets the customer specifications, but is one that the sponsor and key business experts actually want to use. The emphasis on project quality is on preventing errors, rather than inspecting the product at the end of the project and then eliminating errors. Project quality also recognizes that quality is a management responsibility and needs to be performed throughout the project.

Creating the Quality Plan involves setting the standards, acceptance criteria, and metrics that will be used throughout the project. The plan, then, becomes the foundation for all the quality reviews and inspections performed during the project and is used throughout project execution.

Project Risks: A risk is an event that may or may not happen, but could have a significant effect on the outcome of a project, if it were to occur. For example, there may be a 50% chance of a significant change in sponsorship in the next few months. Analyzing risks includes making a determination of both the probability that a specific event may occur and if it does, assessing its impact. The quantification of both the probability and impact will lead to determining which are the highest risks that need attention. Risk management includes not just assessing the risk, but developing risk management plans to understand and communicate how the team will respond to the high-risk events.

Step 10: Communicate! One important aspect of the project plan is the Communications Plan. This document states such things as:

  • Who on the project wants which reports, how often, in what format, and using what media.
  • How issues will be escalated and when.
  • Where project information will be stored and who can access it.

For complex projects, a formal communications matrix is a tool that can help determine some of the above criteria. It helps document the project team's agreed-on method for communicating various aspects of the project, such as routine status, problem resolution, decisions, etc.

Once the project plan is complete, it is important not just to communicate the importance of the project plan to the sponsor, but also to communicate its contents once it's created. This communication should include such things as:

  • Review and approval of the project plan.
  • Process for changing the contents of the plan.
  • Next steps—executing and controlling the project plan and key stakeholder roles/responsibilities in the upcoming phases.

 Don't forget to leave you comments below.


Elizabeth and Richard Larson are Co-Principals of Watermark Learning, a project management and business analysis training company. They have over 30 years of industry experience each, and have helped thousands of PM and BA practitioners develop new skills.

They have published numerous articles and papers and have co-written two books together on Requirements Management and CBAP Preparation. Both Rich and Elizabeth are CBAP and PMP certified through IIBA and PMI, and are contributors to the BABOK® Guide, Version 2.0 and the PMBOK® Guide – 4th edition.

Read 300029 times Last modified on Wednesday, 30 May 2012 13:10

Comments  

+4 # Finnsven 2009-01-28 21:53
I like the structural approach but didn't find a step for development and approvement of scenarios for different mix of ressources, finish-date and economy.
Reply | Reply with quote | Quote
+4 # Dagwood 2009-02-04 10:13
I liked a lot of what the article had to offer, but I think it missed one critical ingredient. If one followed the 10 steps, one would be courting disaster, I think! Not because of the steps themselves, but because the idea of the project plan seems to be conceived as a 'top down' bit of authoritarianis m imposed on the sponsor, the team and the stakeholders. I n my project environment we plan our projects through team and stakeholder workshops to develop as fully as possible the 'shape' of the project, identify the value it will need to produce and the constraints, dependencies and risks it will be circumscribed by, from as many informed perspectives as possible. This informs the project, gets the whole project community contributing, 'owning' and supporting the project, and takes advantage of a wide spread of experience, interest and capability. It also embeds project commitments into a productive community that gives it firm ground in the corporation's life. If a PM wants to plan a project in isolation, they'd better be able to run it in isolation as well.
Reply | Reply with quote | Quote
+1 # dfurlong 2009-02-25 09:42
There is some value in this article, but it was not well thought out. The article is entitled: "10 Steps to Creating a Project Plan", yet the first step is to explain the project plan to key stakeholders and to discuss its key components. How can you explain a project plan that you haven't gone thru the 10 steps to create? Maybe that first step should be #10?
Reply | Reply with quote | Quote
+3 # Richard_Larson 2009-03-06 08:50
@Dagwood - Thanks for your comments. I think you missed the point, though. Our long-standing philosophy on planning is to involve all relevant stakeholders, and what you describe fits into the theme of the article just fine. We have never advocated a PM planning a project in isolation. A PM is the custodian of the project plan, but that doesn't mean a plan is developed in isolation as you mention.
Reply | Reply with quote | Quote
-1 # Richard_Larson 2009-03-06 08:58
@dfurlong - even though the article is called "steps" we didn't say to follow them in the order presented. To your point about explaining the plan: you are correct: you can't explain a plan before you create it. But, you can certainly explain the planning process and components of a plan to stakeholders up front. Thanks for letting me clarify.
Reply | Reply with quote | Quote
-4 # wowwow12 2009-04-11 23:30
Is good to experience this success in the light of project procurement, But nevertheless. The structure needs nostalgic references quotation.
Reply | Reply with quote | Quote
+5 # Samer HAMO 2011-06-24 18:24
i'm not with your comments "we didn't say to follow them in the order presented" that means the 10 steps could be in any order ! the purpose of PM planning is to create the work schedule systematicly in order to avoid any future mistakes which could cost to much. if you we want to plan we most use organize steps and us them orderly with possibility of some modification during the execution process. as well you didn't mentioned any software to execute the steps properly.
Reply | Reply with quote | Quote
0 # chirag purohit 2011-07-08 17:00
I am very very thank full for helping me in making my project easy
Reply | Reply with quote | Quote
-2 # muhammedashfaq 2011-07-23 17:00
I liked a lot of what the article had to offer, but I think it missed one critical ingredient. If one followed the 10 steps, one would be courting disaster, I think! Not because of the steps themselves, but because the idea of the project plan seems to be conceived as a 'top down' bit of authoritarianis m imposed on the sponsor, the team and the stakeholders. In my project environment we plan our projects through team and stakeholder workshops to develop as fully as possible the 'shape' of the project, identify the value it will need to produce and the constraints, dependencies and risks it will be circumscribed by, from as many informed perspectives as possible. This informs the project, gets the whole project community contributing, 'owning' and supporting the project, and takes advantage of a wide spread of experience, interest and capability. It also embeds project commitments into a productive community that gives it firm ground in the corporation's life. If a PM wants to plan a project in isolation, they'd better be able to run it in isolation as well from mian ashfaq gulf constructors pvt Ltd
Reply | Reply with quote | Quote
-2 # muhammedashfaq 2011-07-23 17:04
I like the structural approach but didn't find a step for development and approvement of scenarios for different mix of ressources, finish-date and economy. from Gulf construcrors pvt ltd mian ashfaq
Reply | Reply with quote | Quote
+2 # sallynam 2011-10-10 19:19
the artical is good but its not very clear- i think there's a missing link
Reply | Reply with quote | Quote
0 # sharif moses shelton 2011-10-13 22:16
the article is well analyzed
Reply | Reply with quote | Quote
0 # val 2011-11-07 15:21
Great idea of how to do project plan., with all comments and suggestions. Ba sed on the above thread of postings, few people knows that the trend now, specially in large and complex, multidisciplne projects, is the approach and the use of total project management software. (one of them is the Primavera P6). By using this type of software, the planning engineer don't need a step by step procedure, because while developing the project master plan, the planning engineer is doing as well, in simultaneous, scope of work with it's work breakdown structure, organizational breakdown structure which defines key personnel and stakeholders, detailed task with corresponding logic which defines sequencing, resource and cost integration that will show budget and manpower needs, develop reports that will track and monitor the project progress. The software provides a very liberal procedure and functionalities for the engineer to do it his "way", risk analysis may be part of it. The engineer, as mentioned, may do all the project plan components at the same time or he may do it in an overlapping start to start lag. The result is one functional "Baseline Master Plan" that defines all project plan components needed to commence a project.
Reply | Reply with quote | Quote
+5 # Elizabeth Larson 2011-11-07 23:57
@all—We appreciate all your comments. We wrote this article some time ago, but we’re glad that you still find it useful. I want to emphasize that these are not sequential steps. They are completed iteratively throughout the project. Adding tasks might well uncover new deliverables. Adding estimates might well uncover new tasks and deliverables, and so forth. Although we have initial discussions with our sponsors and other key stakeholders to understand the business need and benefits, we certainly have many discussions with many stakeholders throughout the project. in my role as a PM I’ve never completed these steps sequentially and only once. Not sure who could.
Reply | Reply with quote | Quote
0 # Elizabeth Larson 2011-11-08 00:08
@Val, Thanks for your comment. Our philosophy is and has always been that tools support processes, in this case the project planning process. I have never found any tool that has eliminated the hardest parts of planning: getting sponsor ownership, agreement on the scope, enough resources, a handle on dependencies, communications and buy-in on the plan, a way to easily change dependencies…I could go on and on. @all, This article does not specifically address planning using Agile methods. I think the nature of these methods, like the Scrum framework, inherently lessens the planning complexity and the use for complex, cumbersome automated tools.
Reply | Reply with quote | Quote
-4 # thirunavukkarasu 2011-12-25 20:14
project creates
Reply | Reply with quote | Quote
+1 # Soumya 2012-02-29 07:37
Thanks for sharing. Nice analysis. I should say.
Reply | Reply with quote | Quote
0 # Gautam 2012-03-04 03:20
Nice analysis on creating a project. Quite useful. Thanks.
Reply | Reply with quote | Quote
-3 # Dodou Njie 2012-04-02 09:51
I am an engineer who wants to apply for job as project manager but no idea or little knowledge on project management and planning. What is your advise ?
Reply | Reply with quote | Quote
+1 # Dennis 2012-05-17 08:49
I believe this is a great article. When reading articles such as yours I always look at it as refresher and confirm what I know. I work in an IT domain where PM methodology although accepted is mostly followed because it is mandated rather than believed in getting stakeholders involved early and educating them is an important step. I suspect that individuals can take what they need from the article. I believe it is good and thought-out.
Reply | Reply with quote | Quote
0 # Max Wideman 2012-05-17 10:36
I have searched the entire text of both Elizabeth's article and all of the comments to date and there is not one single mention of (developing) the project's Business Case – not by anyone.

Does no one do any serious project management any more?
Reply | Reply with quote | Quote
+1 # Elizabeth Larson 2012-05-17 11:16
@Max. Thanks for your comment. The business case is input to the Project Charter (PMBOK section 4.1.2), and therefore is developed prior to the initiation of a-project. The business case is developed by the requesting organization (4.1.2), not the project manager for a very good reason. Those requesting the project need to define the business need and benefit and take ownership of them. The business analyst (BA) plays a significant role in advising the requesting organization. Although the BABOK suggests that BAs develop the business case (BABOK section 5.5), the ownership is always (and needs to be) with the business.
Reply | Reply with quote | Quote
0 # Dennis 2012-05-17 11:29
Sounds about right.
Reply | Reply with quote | Quote
+1 # Max Wideman 2012-05-18 00:05
Dear Elizabeth,

Thank you for your quick response. Yes, I know what the PMBoK says, but just because it says such and such does not mean that it is right. The Business Case is a justification for the project. Exactly when it is prepared, by whom, or even by whom it is owned is not the issue. The issue is that if the project does not have a clear Business Case that justifies its existence, then you don't know whether it is worth doing in the first place. And if you don't know that, you cannot judge whether the outcome will be successful. And if you don't know the measures of success then I can guarantee that it will not be.

Therefore, it is incumbent on the project manager as the first order of business, to ensure that there is a viable Business Case and that he or she knows what is in it. That is the beginning of the project, aka "Initiation".

Fobbing off the Business Case as "someone else's responsibility" and not taking ownership is the cause of many project failures, especially in IT.

Cheers, Max Wideman
Reply | Reply with quote | Quote
-1 # Elizabeth Larson 2012-05-18 09:29
@Max. What a fun discussion! Thanks for your thoughts. The intent of the article is to provide guidance and focus on the project management plan, not the project charter. Having said that, feel free to add another step, #1: Review project charter to ensure business case and business need have been defined. As someone who spent over 20 years in IT, and as BA and PM having had too many systems called “Elizabeth’s system,” I learned that they who define project benefits end up owning the end product. I have too many battle scars to advise others that developing the business case is a PM function. It takes more courage, I would say, to ensure that the business has developed a strong business case, than to do that work ourselves. But that’s another discussion for another day.
Reply | Reply with quote | Quote
+3 # Max Wideman 2012-05-18 11:09
Dear Elizabeth,

Good! Let us consider that a new Step #1 has now been added.
And now that I have your attention, I can also reveal my "hidden agenda". I understand that you are currently being instrumental in developing the next PMBOK update? If that is the case, then perhaps you can fix it along the lines we've been discussing?

Of course there are other things I'd like to fix but they are too heady for this exchange.

Cheers, Max
Reply | Reply with quote | Quote
0 # Elizabeth Larson 2012-05-18 11:55
@Max. On the PMBOK there were lots of things we wanted to change--even fought for tooth & nail. I only worked on Scope Management concentrating on Collect Requirements. The draft has been through public comment and adjudication and I have no idea which comments were accepted. Even if I don't agree with everything that's in the BOK (and I don't) it does seem to me a very excellent, even exceptional framework that works really well. I wish it had been around for most of the 15 years I was a PM. Cheers to you, too, and maybe we'll meet in person sometime.
Reply | Reply with quote | Quote
-1 # Max Wideman 2012-05-21 00:45
Elizabeth. Now its getting really interesting. Are you allowed to tell me the "lots of things we wanted to change--even fought for tooth & nail"? (Either publicly or privately?)

Yes, it is a very good framework, but the "new and improved" brigade have over reached themselves. The 2008 Section II - Chapter 3 is a disastrous attempt to diagram a very complex subject. I wouldn't mind so much if it was not claimed to be "The Standard for Management of a Project" (My emphasis) One day, some lawyer will sue an unsuspecting project manager on a failed project for failing to follow Chapter 3 to the letter!

If you happen to attend the PMI Congress in Vancouver this year then, yes, we might just meet. :-)
Reply | Reply with quote | Quote
-1 # Dmitry 2012-05-29 08:10
It seems, the steps are messed up. The first step explains the rest of the steps... I think the author should re-write this post and make necessary corrections.
Reply | Reply with quote | Quote
0 # jemberu 2012-06-07 07:03
even if the idea of ten steps to create a project plan is somewhat important as a beginner it is not easily understandable. ...
Reply | Reply with quote | Quote
+1 # R. Max Wideman 2012-06-07 10:21
jemberu, you said [the] ten steps to . . . create a project plan . . . is not easily understandable . . . May I suggest that's because for "a beginner" there is a better way. Use my "Scope-Pak" approach, tried and true for the past 25 years. You will find it here: http://www.maxwideman.com/papers/scopepak/intro.htm — and there are only eight steps!
R. Max Wideman
Reply | Reply with quote | Quote
0 # suniel 2012-06-09 06:05
very2 fantastic ans
Reply | Reply with quote | Quote
+1 # okelo 2012-06-22 06:08
good work
Reply | Reply with quote | Quote
+2 # mrafique 2012-08-04 16:13
I like the article. To everyone please keep in mind when you are involved in multimillion dollar projects ....you should follow and perform multiple tasks ....its an article and take it as an article ....otherwise i suggest take detail courses on Project Management...Th anks to Larsons !
Reply | Reply with quote | Quote
+2 # Mangesh Jadhav 2012-08-07 05:54
Hi,

These are very clear and structured way of managing the project. Even PMI PMP also tells us the same approach. I liked the way it is put with precise langauage.

Can you please also provide information on how to manage a project in agile model?

Thanks,
Mangesh Jadhav
Reply | Reply with quote | Quote
+2 # Elizabeth 2012-08-07 13:51
My favorite reference is the book the Software Project Manager's Bridge to Agility by Michele Sliger and Stacia Broderick. http://www.amazon.com/Software-Project-Managers-Bridge-Agility/dp/0321502752/ref=sr_1_1?s=books&ie=UTF8&qid=1344364951&sr=1-1&keywords=stacia+broderick
It's details how to take the PMBOK and use the concepts in an Agile environment.
Reply | Reply with quote | Quote
+4 # Mike 2012-08-13 12:52
Personally, I appreciate this condensed version of the project management plan. It provides a fluid description of different steps involved in the process. It also helps to prepare someone with limited experience how to prepare an initial document.

I agree with many representatives here that this document is not followed sequentially, which is true, but it provides many of the basic needs to write a plan.

I will tailor the document according to the needs of my business plan.
Reply | Reply with quote | Quote
+1 # wonder 2012-09-11 04:55
[quote name="Elizabeth "]My favorite reference is the book the Software Project Manager's Bridge to Agility by Michele Sliger and Stacia Broderick. http://www.amazon.com/Software-Project-Managers-Bridge-Agility/dp/0321502752/ref=sr_1_1?s=books&ie=UTF8&qid=1344364951&sr=1-1&keywords=stacia+broderick
It's details how to take the PMBOK and use the concepts in an Agile environment.
Reply | Reply with quote | Quote
+1 # guru 2012-09-15 13:29
This is Good and Essential. Success of the Project depends upon the Technical Expertise of the team members and how well they apply it. Also, Planning, Priporitization , coordination are key ingredients.
Reply | Reply with quote | Quote
+2 # Danladi A 2012-11-26 17:12
Very concise. I find the 10 steps illuminating my way forward like a torch light. As I read, I easily visualize my project taking a structured way of taking off and becoming reality. Thanks.
Reply | Reply with quote | Quote
+1 # rohith 2013-01-04 10:52
great work and it is well analyzed sir.
Reply | Reply with quote | Quote
+2 # BYABAGABO 2013-04-19 05:48
I'm so glad to know about you and your organization activities which considering as the answer for realising my dream of becoming a project manager, so it is after knowing that you are a project and busines analusis training company with over 30 years of industry experience each that helped thousands of PM and BA practioners devevop new skills.Therefor e the scenario I would to send my request on geting opportunity and benefit to be trained asd I'm BA practioners who need to develop ne skills.Thanks and kind regards .
Reply | Reply with quote | Quote
+2 # Darcy 2013-04-19 08:15
# BYABAGABO - thank you for your interest in training from Watermark Learning! Please contact me directly for more information: , 952-921-0900 ext. 209

Please also visit us at www.watermarklearning.com
Reply | Reply with quote | Quote
0 # Mike 2013-04-27 16:19
Great article - thanks! One way I've learned to increase the chances of successful project planning is to start with a decent project plan template. I created a template that features a gantt chart and some other features found only in microsoft project... feel free to check it out and download it for free at http://www.mlynn.org/2012/05/excel-project-planning-spreadsheet/
Reply | Reply with quote | Quote
0 # katya 2013-04-29 04:06
A nice article....
Reply | Reply with quote | Quote
+2 # umasankar k 2013-05-09 13:44
It is very useful for me because of the exam will soon and i can under stand my answer through your web site.

thanks a lot.

Umasankar K.
Reply | Reply with quote | Quote
0 # Peter Omondi Akelo 2013-05-22 08:10
Elizabeth and Richard I thank you for taking time to decode for the many practitioners the theories of management planning by creating the 10 steps. Like binoculors, these on;y help us to see deeper, forward and backwards so that we get to grasp the bits of information to help us come up with a good plan that anyone can use to navigate their way in our absence. Not many of us would look at a project plan as being a tool made for someone else and I think, funny as this may sound, the effectiveness of any plan is its ability to make other staff to visualize things just as they are in our minds. This approach is great.
Akelo
Reply | Reply with quote | Quote
+1 # meeNu 2013-06-26 02:39
Hi
It's really very usefull for me to do my FIRST PROJECT i'm very Thankfull for U....
Reply | Reply with quote | Quote
+1 # Elizabeth 2013-06-26 10:03
Thank you all for your continued wonderful feedback! We really appreciate your writing and letting us know that you find the content useful. @meeNu I hope your first project goes better than mine did ( among other things I didn't get buy-in). @Peter, thanks for emphasizing the importance of using the plan as a communication tool. @Mike, Katya, Umasankar, thanks for letting us know that the article was useful!!
Reply | Reply with quote | Quote
+1 # geetha 2013-06-27 04:34
this is very good and essential its very use full for me .even if idea ten steps to create a project plan ......
okay thank you for the best information for me..........
Reply | Reply with quote | Quote
+1 # geofrey mbote 2013-07-30 05:22
the most important to the planners is to know the steps on how to create project plan, well thanks 4 the above 10 steps to create project planning. insist u keep teaching the nus!!
Reply | Reply with quote | Quote
+1 # geofrey mbote 2013-07-30 05:22
the most important to the planners is to know the steps on how to create project plan, well thanks 4 the above 10 steps to create project planning. insist u keep teaching the nus!!
Reply | Reply with quote | Quote
+1 # Prince Joe 2013-09-10 13:05
this is one of the best simplified steps I have come across. It is plainly good stuff to use by most all sector and sort of project.
Thanks
Reply | Reply with quote | Quote
+1 # Zandile 2013-09-18 03:41
Hi Elizabeth

This is the best explanation of Project Planning. Much appreciated

Thank you very much
Reply | Reply with quote | Quote
0 # Kalaluka 2013-10-21 09:14
I find this very helpful and objectivity. Surely it is a very friendly way and thank you for adding value to my understanding of Project Planing.
Reply | Reply with quote | Quote
0 # julianah 2013-12-06 16:05
Wonderful work u have here thanks
Reply | Reply with quote | Quote
-1 # Raphael Amofa-Baah 2013-12-11 02:58
wonderful explanation, thank you.
Reply | Reply with quote | Quote
+1 # Mirza Baig 2014-02-04 13:44
Thanks Elizabeth,
this is really great article. i really liked it.
i hope you will write something more about the project managements.
we all really appreciate that.

thanks
Reply | Reply with quote | Quote
0 # Charl 2014-03-06 02:32
Hi Everyone

I am using the above article as a point of reference for a project i am doing for my final year BSc Computer Science.

My question is: "Does all the different plans mesh in to the project plan?"
I see a lot of work ahead and need some guidance.
Reply | Reply with quote | Quote
0 # maxwideman@shaw.ca 2014-03-06 10:36
Charl, essentially the project plan is the composite of all the detailed plans listed in the original article. However, you have to start somewhere, so you start with a "high-level" project plan out of which flow the other more detailed plans. When you do that, inevitably there will be necessary adjustments to integrate them all (i.e. roll-up) into the overall project plan. Until you finally have an effective working document.
The only quarrel I have with the original article is that "quality" is one of the core variables in a project and therefore should be associated with scope, time and cost. Quality is not a risk associated item as suggested in Step 9. The author was probably trying to force fit everything into 10 steps, when there are actually a lot more than ten.
Get the quality level (grade) wrong and the product of the project will be a failure.
Hope that helps,
R. Max Wideman
Reply | Reply with quote | Quote
0 # Elizabeth Larson 2014-03-06 10:56
Yes, all the plans are combined into what's called a Project Management Plan. Each plan is a separate subsidiary plan. All the plans together comprise the Project Management Plan. The reason they are combined is that one affects others. For example, if we add to the scope (WBS), we need to change the activity list, think about additional risks, etc.
Having said that, for smaller projects (small being less risk, fewer stakeholders, collocated, less complexity, etc.) some of the plans can be combined. If you’re unsure, I would create separate plans, even if they’re short, and keep them under the umbrella of a Project Management Plan.
Reply | Reply with quote | Quote
0 # Sourabh 2014-06-26 11:36
Absolutely right. Thats what PMBOK says. But, nevertheless, a very nice and concise article containing perfect summary of process required to make a project plan.
Reply | Reply with quote | Quote
0 # Getu 2014-07-14 03:04
it is very nice, but it lacks tabular formats that help to simplifies the above steeps.
Reply | Reply with quote | Quote

Add comment


Security code
Refresh