Microsoft Office Project 2007 Tackles Scope Creep | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Resources > White Papers
Managing scope creep and communicating changes to key stakeholders with Microsoft Office Project 2007.
According to Project Managers, most project failures are a result of a breakdown in communication. They report that key stakeholders who continue to change project parameters or make new change requests after the project start put ultimate success of their projects at risk. In fact, it is not change but the lack of change control that usually causes a project to fail. This paper discusses change control and the use of Microsoft Office Project 2007 to better manage scope creep during the implementation of a project. Tips and techniques to communicate the impact the changes have on the triple constraint of cost, time and scope are examined. New ways to create views that immediately show the impact of change are also described.
Introduction
Project Managers list the key reasons for project failure as:
> Project goals are poorly defined, and outcomes are not identified in specific and measurable terms.
> Project plans lack sufficient detail, leading to insufficient time allocation and inadequate financial support and/or other resources.
> Key stakeholders do not “buy-in”- agree to provide adequate support.
> A risk analysis is not performed.
> The project scope expands uncontrollably- scope creep.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement