Pmm-190 Chapter 5

Chapter Five

DQ 1-5

spotsy

September 3, 2014

[Abstract]

This paper will answer the questions posed in discussion questions 1-5 at the end of chapter five in the eBook. The questions read as follows:

1. What is involved in project scope management, and why is good project scope management so important on IT projects?

2. What is involved in collecting requirements for a project? Why is it often difficult to do?

3. Discuss the process of defining project scope in more detail as a project progresses, going from information in a project charter to a project scope statement, WBS, and WBS dictionary.

4. Describe different ways to develop a WBS and explain why it is often so difficult to do.

5. What is the main technique used for validating scope? Give an example of scope validation on a project.

Chapter Five

DQ 1-5

DQ 1:

Scope refers to all the work being performed during the execution phase necessary to produce a product. Project scope management involves six processes. These processes are:

* planning scope management

* collecting requirements

* defining scope

* creating the work breakdown schedule

* validating scope

* controlling scope

Project scope management is crucial in making sure the stakeholders and all those involved are in sync with what products are to be produced and how they will get produced. The stakeholders should acknowledge what the particular project’s deliverables or products are and should also understand, generally, how they should be produced to define all of the deliverables. Project scope management helps to insure the project’s successful outcome.

DQ 2:

Collecting requirements involves determining exactly what functions the client or end-users are looking for in the product as well as, more precisely, the products specifications. It also includes a description of how the products will be created. All of this information is then documented in requirements documentation and...