ICPM

This email address is being protected from spambots. You need JavaScript enabled to view it. This email address is being protected from spambots. You need JavaScript enabled to view it. The International Community for Project Managers
Brought to you by TenStep, Inc.
2363 St. David's Square
Kennesaw, GA 30152
877-536-8434 or 770-795-9097

This email address is being protected from spambots. You need JavaScript enabled to view it.
You are here: Home Blogs
Error
  • JUser: :_load: Unable to load user with ID: 62
Project Management Blog
Blogs

Blogs (1350)

Thursday, 25 January 2007 19:06

Activity Resource Estimating

Written by
Rate this item
(0 votes)

This is the process of estimating how many resources a project team should use to perform project activities. Before estimating activity durations, the PM must have a good idea of the quantity and type of resources that will be assigned to each activity. Consider important issues in estimating resources:

  • How difficult will it be to complete specific activities on this project?
  • What is the organization’s history in doing similar activities?
  • Are the required resources available?
Last modified on Friday, 11 December 2009 01:28
Thursday, 25 January 2007 18:28

Scope Control

Written by
Rate this item
(0 votes)
The most prominent tool applied with scope change control is the Integrated Change Control System. Because changes are likely to happen within any project, there must be order to process, document, and manage the changes.

This system may include:

Last modified on Friday, 11 December 2009 00:41
Thursday, 25 January 2007 18:27

Scope Verification

Written by
Rate this item
(1 Vote)

Scope verification is the process of formalizing acceptance of the project scope by the stakeholders. It requires reviewing work products and results to ensure that all were completed correctly and satisfactorily. Scope verification occurs at the end of each project phase, and as part of the project closeout process. Scope verification is concerned with stakeholder Acceptance of the work. Work is sometime denied and must be Re-Worked. 

Last modified on Friday, 11 December 2009 00:42
Thursday, 25 January 2007 18:25

Creating a Work Breakdown Structure

Written by
Rate this item
(0 votes)

A WBS identifies all the tasks required to complete the project. The focus of the WBS can be either Product (deliverable) or Project oriented, or both. WBS elements are usually numbered, and the numbering system may be arranged in various manners. If a WBS is extensive and if the category content is not obvious to the project team members, it may be useful to write a WBS Dictionary. This describes what is in each WBS element. It may also say what is not in an element. The primary purpose of the WBS is to develop or create small manageable chunks of work called work packages.

Last modified on Thursday, 10 December 2009 18:49
Thursday, 25 January 2007 18:22

Scope Definition

Written by
Rate this item
(0 votes)

Decomposing the major project deliverables into smaller, more manageable components completes scope Definition. There are a good number of outputs from the Scope Definition phases that you’ll need to be familiar with.

Scope definition is the subdivision of project deliverables into smaller (and more manageable) pieces until you have adequately identified in the work breakdown structure all the work on the project. 

Last modified on Friday, 11 December 2009 00:43

News and Promotions

Keep up to date with the latest happenings by signing up for our newsletter. Subscribe below.

Twitter Update

Who's Online

We have 240 guests and no members online

Got something to say?