Software Project Management

Submitted By: Muhammad Ali Hussain

ID: F2016065210
Submitted To: Mam Tayyaba Anees
Software Project Management

ASSIGNMENT #1
Question 1: How will you do Stakeholder Analysis as a project manager?
Stakeholder:

A stakeholder is anyone who is affected by, or can influence, the project outcome. Primary
stakeholders, such as executive sponsors, management or company employees, have a direct
stake in the project and are usually involved in all aspects. Secondary stakeholders, such as
vendors, government entities, and members of the public, are those indirectly affecting or
affected by business operations.

Stakeholder Analysis:

Stakeholder analysis is the process of identifying and analyzing the stakeholders that are likely to affect
or be affected by a proposed action (positively or negatively).

This is useful to manage them appropriately and effectively.

It can be done once or on a regular basis to track the attitudes of stakeholder’s overtime.

Widely used in project management.

When it is used?

In project management to develop cooperation between the stakeholders and the project team.

It helps to identify:

 The people to be informed during implementation.

 The key people to be involved and

Stakeholder as Project Manager:

The actual steps which I will take as a stakeholder analysis are:

 Stakeholder identification
 Stakeholder expectations and interests
 Stakeholder influence and role in the project
Stakeholder Identification: This first step is concerned with the question "Who are the
stakeholders?" For this, you basically draw maps of people or groups and their relationships.
You start with two names on a whiteboard and before you know it, you are drawing on the walls.

Stakeholder Expectations and Interests: This is most difficult step; here we get the socio-
psycho stuff. For expectations it is fairly straightforward: just ask. You can ask in person or via
mail or email. Create some variations on the question, so that it is not too obvious what you are
trying to find out. Stakeholder interests are another thing. Trying to elicit their interests is
always guesswork, deducting them from other information. For this, there are two types of
approaches:

 Using a checklist to assist your thinking about the stakeholder and

 Plotting people in small models that help determine the way to approach them.

For the first type, consider a list with questions like: "Is he satisfied with his current job?", "Is he
covering up his own incompetence?" and "Does he want a bigger office?" Thinking about these
questions help you build an image of the persons interests. Consider the list at the end of this
article as good starting point.

Using small models, the second type, can be easier than it sounds. For this, you have to plot a
stakeholder in a dimension, and by doing that, you get an idea of how to approach the
stakeholder. Dimensions can include: "How much in favor of the project", "Process or Content-
oriented" and "Group or Individual-oriented."

Stakeholder Influence and Role in the Project : The insights about the stakeholders will assist
us also to construct the project organization:

 Do we have to include the stakeholders in the organization?

 If so, is it wise to grant stakeholders great influence or should we give them positions
where they can do no harm?
 How can we construct stakeholder job descriptions in such a way that they are as
motivated as possible?
Question 2: What is project scope management? As a project manager how will you write
Preliminary Scope Statement?

Project Scope Management

The Project Scope Management is the process to ensure that a particular project includes all the
work relevant/appropriate to achieve the project's objectives. Its primary aim is to control what is
and is not involved in the project. The Scope Management techniques enable project managers
and supervisors to allocate just the right amount of work necessary to complete a project.

When I am working as a Project Manager. I will be following this hierarchy:

Plan scope management: The scope management plan describes the project scope and
documents how it will be further defined, validated, and controlled throughout the lifecycle of
the project.
Collect requirements: It is the process of defining and documenting stakeholders needs to meet
the project activities. The document for collecting requirements is developed in the project
planning phase.

Define scope: This is the process of developing a detailed description of the Project and product.
So while Collecting requirement list, all the different requirements of the Project and the
resulting product or service are defined.

Create Work Breakdown Structure: Creating work breakdown structure is done using a

technique called decomposition/breakdown. It is the process of subdividing project deliverables
and project work into smaller and more manageable components for achieving a better outcome.

Validate scope: A part of project monitoring and control process group in which the process
includes reviewing deliverables with the customer or sponsor to ensure that they are completed
satisfactorily and obtaining formal acceptance of deliverables by the customer or sponsor.

Control scope: Control Scope is the last process group in the project scope management. It is
again a part of project monitoring and control process group. Control scope is the process of
monitoring the status of the project and product scope and managing changes to the scope
baseline.