1.

What is involved in project scope management, and why is good project scope
management so important on IT projects?
Scope refers to all the work involved in creating the products of the project and the
processed used to create them. Project scope management includes initiation,
scope planning, scope definition, scope verification, and scope change control.
Scope management is very important on information technology projects because
many projects suffer from unclear requirements and scope creep.
2. What is involved in collecting requirements for a project? Why is it often difficult to
do?
There are two things that collecting requirements involved: First is, defining and
second, is documenting. These things will defined and document the features and
functions of the products for the project as well as the processes used for creating
them. Difficult because it depends of the project, t7here are projects that have bigger
scope.
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.
In defining a project scope it includes reviewing the scope management plan, project
charter, requirements documents, and organizational process assets to create a
scope statement. This requirements changes upon adding more information or
updates.
4. Describe different ways to develop a WBS and explain why it is often so difficult to
do.
First way is the analogy approach, second way is the top-down approach. Third is
the bottom-up approach, and lastly is the mind-mapping approach. It is difficult
because in creating a good WBS you need to follow this approaches and this
approach has a unique based on the project and the team.
5. What is the main technique used for validating scope? Give an example of scope
validation on a project.
The main technique used for validating scope is formalizing acceptance of the
project deliverables. The major stakeholders such as the customer and sponsor of
the project will validate and accept the deliverables. For example comparing the
scope requirements to decide whether the team has produced what was plan and
documented.
6. Using examples in this book or online, describe a project that suffered from scope
creep. Could it have been avoided? How? Can scope creep be a good thing? When?

What can organizations do to successfully manage inevitable changes in scope that are
good for business?
The FoxMeyer drug a pharmaceutical company in which the company has resulted
bankruptcy because they cannot handle bigger scope. The companies problem could
have been avoided if the companies managers focused on the business needs not the
technology. Scope creep can maybe sometimes a good thing, such as if you are
working in a company that is a consulting company in which you are getting paid by an
hour then the project continues to grow in scope, which means the company have more
work and therefore make more money.
7. Why do you need a good WBS to use project management software? What other
types of software can you use to assist in project scope management?
The tasks in a Gantt chart should be based on a WBS. Other types of software that
assist in project scope management include word-processing software, spreadsheet
software, database software, and various types of communications software. There are
also special products to help use balanced scorecards or create mind maps.