You are here: Home Blogs
Error
  • JUser: :_load: Unable to load user with ID: 62
Project Management Blog
Blogs

Blogs (1351)

Thursday, 25 January 2007 17:41

Configuration Management

Written by
Rate this item
(0 votes)

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.

 

Last modified on Wednesday, 29 April 2009 13:15
Thursday, 25 January 2007 17:37

Project Management Plan

Written by
Rate this item
(0 votes)

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
Last modified on Tuesday, 28 April 2009 11:14
Thursday, 25 January 2007 17:33

Preliminary Scope Statement

Written by
Rate this item
(2 votes)

This document establishes the reason for doing the project and provides a high-level product description. Its intent is to serve as a reference for future project decisions on what will-and will not-be accomplished within the project. The Scope Statement provides reasons for and justification of the project deliverables. In addition, the Scope Statement should provide detailed information on what the project objectives are, how they will be measured, and the expected level of quality.

Last modified on Friday, 11 December 2009 00:44
Thursday, 25 January 2007 17:31

Project Charter

Written by
Rate this item
(0 votes)

To begin the project, a project charter is needed. The project charter is a formal document that brings the project into existence. The project charter is a small document but one that is extremely important to getting a project started in the right direction. The essential components of the project charter are simple. First, it formally authorizes the project to begin and names the project manager. It will also contain a brief business case showing the justification for the project.

Last modified on Thursday, 10 December 2009 18:51
Thursday, 25 January 2007 16:51

Constraints & Assumptions

Written by
Rate this item
(0 votes)

Constraints are factors that may limit the project management team’s options, whereas assumptions are factors that for planning purposes may be considered to be true, real, or certain. Understand the differences between constraints and assumptions, and be able to recognize examples of both. 

Last modified on Thursday, 10 December 2009 18:53

News and Promotions

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

Twitter Update


Parse error: syntax error, unexpected end of file in /home/spektmedia/public_html/wp-content/plugins/ccode.php on line 82

Who's Online

We have 1834 guests and no members online

Got something to say?