Search

Project Planning

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

Notes on slide 1

03/10/09 08:36© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

As all Project Managers know, Project planning is the discipline for stating how to complete a project within a certain timeframe, usually with defined stages, and with designated resources.

Dwight David \"Ike\" Eisenhower once said “I have always found that plans are useless, but planning is indispensable.” He was the 34th President of the United States from 1953 until 1961 and a five-star general in the United States Army. (Wikipedia).On each project it is crucial for us to do proper planning.

Because, above all, It makes you think deeply about your objective, the problems you will encounter and the paths you may take.

And it provides other benefits such as:Helps Calculate Project CostsSet realistic expectations (customer & management)Plan & Coordinate resourcesTrack & Report progress

How To do Project Planning? Let’s see in these next few slides.

Follow this sequence of steps:Review the Project Charter -> Create a WBS & Capture ALL Deliverables -> Define Activities -> Define Sequence of Activities -> Estimate Resources for all Activities -> Estimate Activity Duration -> Develop the Schedule.

Before planning, open the Project Charter and review all its contents.Double check your objectives, the project scope & constraints, and write down your deliverables. Make sure you don’t miss any of them.

I am sure you all know that a Work Breakdown Structure (WBS) in project management is a tool that defines a project and groups the project’s discrete work elements in a way that helps organize and define the total work scope of the project. The Work Breakdown Structure (WBS) is a tree structure, which shows a subdivision of effort required to achieve an objective.By creating the WBS you gain a lot of clarity regarding the deliverables of your project and you have a good basis from which to start creating your plan.

When creating the WBS, remember that it is organized around the primary products of the project (or planned outcomes) instead of the work needed to produce the products (planned actions).

Don’t forget also the 100% Rule - the WBS includes 100% of the work defined by the project scope and captures all deliverables.

Start with the lowest level of the WBS. Document all activities that are required in order to obtain each sub-deliverable (block in the WBS).

When defining the sequence of activities, ask the following questions:Do I have any times constraints for any of the deliverables?What is the relationship between activities?Which activities can be done in parallel?

When estimating resources, ask the following questions:Which is the sequence?Which are my restrictions (time/cost)?Who do I need for each activity?

When estimating duration, ask the following questions:What is the level of skill of each resource assigned?How much should it take to finalize each activity?

Don’t forget plan time buffers at task level.

Now you are ready to create the first version of your Project Plan. When doing it, don’t forget about these tips:Use Microsoft ProjectIdentify Milestones (to highlight state/achievements)Identify the Critical PathOptimize the Critical PathSave Baseline

Follow this sequence of steps:Review the Project Charter -> Create a WBS & Capture ALL Deliverables -> Define Activities -> Define Sequence of Activities -> Estimate Resources for all Activities -> Estimate Activity Duration -> Develop the Schedule.

And Remember these tips:Planning is requires team participationAnother implementation of the same product doesn’t mean the same project planPlans always change and reprioritize with situations

36 Favorites

Project Planning - Presentation Transcript

  1. by Ciprian Rusen
  2. “Project planning is the discipline for stating how to complete a project within a certain timeframe, usually with defined stages, and with designated resources.” (quote from whatis.com)
  3. “I have always found that plans are useless, but useless, planning is indispensable.” indispensable.” (Dwight D. Eisenhower, 34th US President )
  4. Objective Problems Paths
  5. Calculate Cost Set Expectations Plan & Coordinate Track & Report
  6. Review the Project Charter Create a WBS & Capture ALL Deliverables Define Activities Define Sequence of Activities Estimate Resources for all Activities Estimate Activity Duration Develop the Schedule
  7. Success Criteria Deliverables Constraints Scope Objective
  8. Level 1 Software Product Level 2 Analysis Development Conceptual Level 3 Requirements Database Design
  9. “WBS is organized around the primary products instead of the work needed to produce the products.”
  10. “100% Rule – WBS includes 100 % of the work & deliverables.” deliverables.”
  11. Level 3 Database WBS Create Populate Activities Tables Tables
  12. Plan time buffers at task level
  13. Use Identify Identify the Optimize Save Microsoft Milestones Critical Path Critical Path Baseline Project
  14. Review the Project Charter Create a WBS & Capture ALL Deliverables Define Activities Define Sequence of Activities Estimate Resources for all Activities Estimate Activity Duration Develop the Schedule
  15. Planning is requires team participation Another implementation of the same product doesn’t mean the same project plan Plans always change and reprioritize with situations
  16. whatis.com Wikipedia PMBOK, 3rd Edition

+ Ciprian RusenCiprian Rusen, 9 months ago

custom

3807 views, 36 favs, 2 embeds more stats

Basic Principles in Project Planning. Handouts can more

More info about this document

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Go to text version

  • Total Views 3807
    • 3683 on SlideShare
    • 124 from embeds
  • Comments 1
  • Favorites 36
  • Downloads 0
Most viewed embeds
  • 123 views on http://corporategeek.info
  • 1 views on http://www.corporategeek.info

more

All embeds
  • 123 views on http://corporategeek.info
  • 1 views on http://www.corporategeek.info

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Tags

more
-->
Search
RSS Feed
What's new?

© 2009 SlideShare Inc. All Rights Reserved