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 Displaying items by tag: stakeholders
Project Management Blog
Thursday, 25 January 2007 21:27

Organization charts

An Organizational Chart represents the structure of an organization in terms of rank. The chart usually shows the managers and sub-workers who make up an organization. The chart also shows relationships between staff in the organization, which can be:

Published in Blogs
Thursday, 25 January 2007 19:16

Activity Duration Estimating

Duration includes the actual amount of time worked on an activity plus the elapsed time.

Effort is the number of workdays or work hours required to complete a task. Effort does not normally equal duration. People doing the work should help create estimates, and the PM should review them. Duration estimating is assessing the number of work periods (hours, days, weeks,) likely to be needed to complete each activity. Duration estimates always include some indication of the range of possible results, for example, 2 weeks + or – 2 days or 85% probability that the activity will take less than 3 weeks. Activity Duration Estimating:

Published in Blogs
Thursday, 25 January 2007 18:27

Scope Verification

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. 

Published in Blogs
Thursday, 25 January 2007 18:22

Scope Definition

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. 

Published in Blogs
Thursday, 25 January 2007 18:20

Scope Planning

Scope planning is the process of creating a project scope management plan that documents how the project scope will be defined, verified, controlled, and how the work breakdown structure (WBS) will be created and defined. The goal of scope planning is to create the output of the scope planning process the Project Scope Management Plan. To be successful creating the scope statement and the scope management plan, the project manager and the project team must have a full understanding of the project requirements, business need of the project, and stakeholder expectations. 

Published in Blogs
Thursday, 25 January 2007 17:56

Closing a Project

In multi-phase projects, the Close Project process closes out the portion of the project scope and associated activities applicable to a given phase. The two procedures necessary to perform the closure activities across the entire project or for a project phase:

Published in Blogs
Thursday, 25 January 2007 17:50

Integrated Change Control

The purpose of overall change control is to influence factors that create change so the change is beneficial, determine when a change has occurred, and manage actual changes when they do occur. This process is concerned with coordinating changes across the entire project. Performed from project Inception through Completion. A Change Control System is used to evaluate and approve or kickback change requests for the project. Changes requests stem from suggestions of the stakeholders. The PM must be careful; certain changes may lead to additional Time and Cost. The PM uses Integrated Change Control to:

Published in Blogs
Thursday, 25 January 2007 17:41

Configuration Management

Configuration management is the term given to the identification, tracking and managing of all the assets of a project; it focuses on controlling the characteristics of a product or service (also referred to as deliverables). In a general sense, configuration management consists of the following:

 

  • The documentation of the features, characteristics, and functions of a product or service
  • The applied control to restrict changes to the features, characteristics, and function of the product or service
  • The process of documenting any changes to the product or service
  • The ongoing auditing of products and services to ensure their conformance to documented requirements
  • Establishes a method to consistently identify and request changes to established baselines
  • To assess the value and effectiveness of changes
  • Provides opportunities to continuously validate and improve the project by considering the impact of each change
  • Provides the mechanism for the project management team to consistently communicate all changes to the stakeholders.

 

Configuration management activities included in the integrated change control process are:

  • Configuration Identification - Providing the basis from which the configuration of products is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
  • Configuration Status Accounting - Capturing, storing, and accessing configuration information needed to manage products and product information effectively.
  • Configuration Verification and Auditing - Establishing that the performance and functional requirements defined in the configuration documentation have been met.

When it comes to configuration management, think paperwork. Think about all the paperwork that is involved in documenting every single component of a system deliverable and making sure that there are no changes to that deliverable, or if there are changes, that they are thoroughly documented. Configuration management is traceable. For the exam, know that all change must be screened, tracked, accepted, approved, and the development process updated thereafter.

 

Published in Blogs
Thursday, 25 January 2007 17:37

Project Management Plan

The project plan is a key integrative document that uses the outputs of the other planning processes to create a consistent, coherent document that is the guide to both project execution and project control. Be familiar with what the project plan is used for and what items are often included in a project plan. The PM uses it to guide project execution, to document our planning assumptions, to document planning decisions regarding some of the alternatives that we have chosen. We use it to facilitate communication among the stakeholders and define key management reviews as to content, expense, and timing. It is a baseline for progress measurement and project control.

The project management plan can be either summary level or detailed, and can be composed of one or more subsidiary plans and other components. Each of the subsidiary plans and components is detailed to the extent required by the specific project.

The Develop Project Management Plan process includes the actions necessary to define, integrate, and coordinate all subsidiary plans into a project management plan. The project management plan content will vary depending upon the application area and complexity of the project. This process results in a project management plan that is updated and revised through the Integrated Change Control process. It also defines how the project is executed, monitored and controlled, and closed. The purpose of planning is to develop a Project Plan.


Subsidiary plans

  • Project scope management plan
  • Schedule management plan
  • Cost management plan
  • Quality management plan
  • Process improvement plan
  • Staffing management plan
  • Communication management plan
  • Risk management plan
  • Procurement management plan

Other key components include, but are not limited to:

  • Milestone list
  • Resource calendar
  • Schedule baseline
  • Cost baseline
  • Quality baseline
  • Risk register
Published in Blogs
Thursday, 25 January 2007 15:15

Stakeholder Management

You should recognize the importance of involving stakeholders in the development of the project plan. It is the responsibility of the project manager and the project team to create an environment in which all stakeholders can contribute as appropriate, but recognize that who contributes and the level of the contribution will vary by stakeholder. There are usually a number of people who are either directly involved in a project or who have a stake in its outcome. These people are called stakeholders. The key stakeholders in most projects are:

Published in Blogs
Page 3 of 7

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 524 guests and no members online

Got something to say?