Name: GWAGSI GLENN FOFEYIN

Assignment 4
1. what is involved in project scope management, and why is good project
scope management so important to IT field?

2. what is involved in collecting requirements for a project ? why is it so

difficult to do so?

3. describe different ways to develop a WBS and explain why it is often so

difficult to do?

1) WHAT IS INVOLVED IN PROJECT SCOPE MANAGEMENT, AND

WHY IS GOOD PROJECT SCOPE MANAGEMENT SO IMPORTANT TO
IT FIELD?
Project Scope Management refers to the set of processes that ensure a project’s
scope is accurately defined and mapped. Scope Management techniques enable
project managers and supervisors to allocate the right amount of work necessary to
successfully complete a project—concerned primarily with controlling what is and
what is not part of the project’s scope. Without a comprehensive project scope
management plan, there’s a good chance your team is doing work that’s
unnecessary to complete the project at hand or even wasting time thinking about
what they should be doing next. The three processes involved in project scope
management are:
Planning: The planning process is when an attempt is made to capture and define
the work that needs to be done. 

Controlling: The controlling and monitoring processes focus on documenting

tracking, scope creep, tracking, and disapproving/approving project changes.

Closing: In the final process, the closing includes an audit of the project
deliverables and an assessment of the outcomes against the original plan.

Managing the expectations of clients and stakeholders can be one of the most

difficult tasks a project manager can face in the IT field. With a distinct scope, it
helps everyone to stay on the same page throughout the life cycle of the project. A
well-defined scope can help to avoid common problems like:

 Requirements that constantly change

 Requirements that need a rethink mid-project
 The final outcome not being what the client expected
 The budget overrunning
 The project is way behind schedule

Effective scope management can help to avoid some of these issues by clearly
defining and communicating the scope to all parties involved in the project. Project
scope helps to distinguish what is and is not involved in the project and controls
what is allowed or removed as it is executed. Scope management establishes
control factors, that can be used to address elements that result in changes during
the lifecycle of the project.

2) WHAT IS INVOLVED IN COLLECTING REQUIREMENTS FOR A

PROJECT? WHY IS IT SO DIFFICULT TO DO SO?
Collecting requirements is defining and documenting the features and functions of
the products produced during the project as well as the processes used for creating
them. Part of the difficulty is that people often do not have a good process for
collecting and documenting project requirements. For some IT projects, it is
helpful to divide requirements development into categories called elicitation,
analysis, specification, and validation. It is important to use an iterative approach
to defining requirements since they are often unclear early in a project.
3) DESCRIBE DIFFERENT WAYS TO DEVELOP A WBS AND EXPLAIN
WHY IT IS OFTEN SO DIFFICULT TO DO?
Using guidelines: Some organizations, like the DOD, provide guidelines for
preparing WBSs the analogy approach: Review WBSs of similar projects and tailor
to your project. The top-down approach: Start with the largest items of the project
and break them down. The bottom-up approach: Start with the specific tasks and
roll them up Mind-mapping approach: Mind mapping is a technique that uses
branches radiating out from a core idea to structure thoughts and ideas
Nevertheless, it is very difficult to create a good WBS. To create a good WBS, you
must understand the project and its scope and incorporate the needs and knowledge
of the stakeholders. The project manager and the project team must decide as a
group how to organize the work and how many levels to include in the WBS.
Another concern when creating a WBS is how to organize it to provide the basis
for the project schedule. You should focus on what work needs to be done and how
it will be done, not when it will be done.