Tuesday, July 10, 2007

Other Inputs to Project Scope Definition

When defining project scope, you may find that the formal scope planning documents are not always a sufficient source of information. What other sources can you tap into to get the information you need, so you can accurately define project scope?

One source of additional information that contributes to scope definition is outputs from other project planning processes. Outputs of the planning processes in the other knowledge areas can be inputs to defining project scope.

Typically, other planning processes are underway simultaneously with scope planning. The outputs that result from many of these planning processes should be reviewed during scope definition because they often contain valuable information that can be used when defining the project's scope. Oftentimes, the outputs from other planning processes have an impact on the defined scope for a project.

Although you can review other management areas when defining your project scope, you should review four key areas that produce outputs to determine if these outputs have an impact on project scope definition. The four areas you should review are listed below.
  • Project cost management. This area ensures that a project is completed within the approved budget. Since scope definition involves cost estimating, outputs from this area that should be used as inputs to scope definition will focus on resource planning, cost estimating, and cost budgeting.
  • Project time management. This area ensures timely project completion. Since project scope definition requires duration estimates, outputs from this knowledge area that should be used as inputs to scope definition focus on activity definition, activity sequencing, and schedule development.
  • Project human resource management. This area helps a project manager make the most effective use of team members. Since scope definition requires resource projections, outputs from this area that should be used as inputs to scope definition concern organizational planning and staff acquisition.
  • Project quality management. This area ensures that the project will satisfy the needs for which it was undertaken. Since scope definition requires defining deliverables for client satisfaction, outputs from this area will focus on quality planning, quality assurance, and quality control.
Given the importance of the scope definition process, you should seek out all available supporting information. Outputs of the four project management areas described above are excellent inputs that can help you accurately and efficiently define your project scope.

4 comments:

Rich said...

What a great Blog for Managing IT project management.

Why did you stop .. Did you get you PMP .. What lessons have you learned While project managing?

So much more to learn. I loved this information Thanks so so much please continue

dheeraj said...

This is so helpful, almost like a lesson in project management. very well written, Thanks so much!

Anonymous said...

Hi,
yes it is real practical blog,keep it up, but i have one question , which is that here the scope definition is the first step in plaining how come those areas will be input to scope if they are not yet established, or you mean that on a high level they will input to scope definition as they might be part of defining the scope

Anonymous said...

Matchless phrase ;)