Assignment of

PROJECT MANAGEMENT

SUBMITTED BY:

Mohd Salahuddin
M. ARCH. (Medical)

SEMESTER- IV

FACULTY OF ARCHITECTURE & EKISTICS

JAMIA MILLIA ISLAMIA
NEW DELHI
2014-15
Ans 1)
Product Scope

Product scope can be defined as the features or characteristics of a product itself.

Whether considering design, function or component parts, the key point is that product scope
refers to the actual tangible product. In the case of good, questions of product scope would
address how it works, how it is physically made and how it can be improved in future iterations.
For example, if the product is a bridge, the product scope might be its length, width, load
strength, etc.

Project Scope

In contrast to product scope, project scope focuses on the various steps taken to deliver
a product or service. Project scope can include, among other things, assembly lines, budgets,
staff training, and supply chains and personnel allocations. Basically, it refers to anything that is
needed in order to arrange the production or implementation of a good or service. For example,
if you have been given a project to build a bridge, in this case the project scope will tell you how
you are going to build the bridge. It gives you all the required information to construct the bridge.

Project Scope Management includes the processes required to ensure that the project
includes all the work required, and only the work required, to complete the project successfully.
It is primarily concerned with defining and controlling what is or is not included in the project. To
accomplish this you need to work through the five following processes:

1) Collect requirements.
2) Definition of the scope.
3) Produce a work breakdown structure (WBS).
4) Verify scope.
5) Control scope.

An important function of this particular plan is that of defining how our project scope will
be managed and controlled as the project progresses.

1) COLLECT REQUIREMENTS

This process is concerned with assessing, documenting, and managing stakeholder needs
to meet project objectives. All requirements should be gathered at the start because it is costly
to make changes as the project progresses. Gathering requirements from all stakeholders will
also ensure that their opinions are taken into consideration,
INPUTS
I. Project Charter

A project charter is a document that formally recognizes the existence of a project

and provides direction on the project’s objectives and management.

II. Stakeholder Register

The stakeholder register is used to identify stakeholders that can provide information
on detailed project and product requirements.

Tools and Techniques

I. Interviews: An interview is a formal or informal approach to discover information
from stakeholders by talking to them directly.

II. Focus groups: Focus groups bring together prequalified stakeholders and subject
matter experts to learn about their expectations attitudes about a proposed product,
service, or result.

III. Facilitated Workshops: Workshops are considered a primary technique for quickly
defining cross‐functional requirements and reconciling stakeholder differences.

IV. Group Creativity techniques:

 Brainstorming
 Nominal group technique
 The Delphi Technique
 ldea /mind mapping
 Affinity diagram

V. Group Decision Making Techniques: There are multiple methods of reaching a

group decision, for example:

• Unanimity. Everyone agrees on a single course 0f action.

• Majority. Support from more than 50% of the members of the group.
• Plurality. The largest block in a group decides even if a majority is not achieved.
• Dictatorship. 0ne individual makes the decision for the group.

VI. Questionnaires and Surveys:

VII. 0bservations:

VIII. Prototypes:
OUTPUTS
I. Requirements Documentation

II. Requirements Management Plan

III. Requirements Traceability Matrix

2) Define Scope is the process of developing a detailed description of the project and
product.

INPUTS
I. Project Charter

II. Requirements Documentation

III. Organizational Process Assets:

a) Policies, procedures, and templates

b) Lessons learned from previous projects

Tools and Techniques

I. Expert Judgment

II. Product Analysis

III. Alternatives identification

IV. Facilitated Workshops

OUTPUTS
I. Project Scope Statement: The project scope statement describes, in detail, the
project's deliverables and the work required to create those deliverables. It includes:

a) Product scope description

b) Product acceptance criteria

c) Project deliverables
 d) Project exclusions

e) Project assumptions

II. Proiect Document Updates

 Stakeholder register

 Requirements documentation

 Requirements traceability matrix

3) Create WBS
Create WBS is the process of subdividing project deliverables and project work into
smaller, more manageable components

INPUTS

I. Project Scope Statement

II. Requirements Documentation
III. Organizational Process Assets

TOOLS AND TECHNIQUES

I. Decomposition

OUTPUTS

I. WBS

II. WBS Dictionary

a) A number Identifier
b) Who is responsible for what
c) A description of each work package
d) Any related codes

III. Scope Baseline

IV. Project Document updates
4) Verify Scope:

Verify Scope is the process of formalizing acceptance of the completed project

deliverables.

INPUTS

I. Project Management Plan

II. Requirements Documentation

III. Requirements Traceability Matrix

IV. Validated Deliverables

TOOLS AND TECHNIQUES

I. Inspections:

lnspection includes activities such as measuring, examining, and verifying to determine

whether work and deliverables meet requirements q and product acceptance criteria

OUTPUTS

I. Accepted Deliverables
II. Change Requests
III. Project Document Updates

5) Control Scope

Control Scope is the process of monitoring the status of the project and product scope
and managing changes to the scope baseline

INPUTS

I. Project Management Plan

 Scope baseline
 Scope management plan
 Change management plan
 Configuration management plan
 Requirements management plan

II. Work Performance lnformation

 III. Requirements Documentation

IV. Requirements Traceability Matrix

V. Organizational Process Assets

TOOLS AND TECHNIQUES

I. Variance Analysis:
Project performance measurements are used to assess the magnitude of variation from
the original scope baseline

OUTPUTS

I. Work Performance Measurements

II. Organizational Process Assets Updates

III. Change Requests

IV. Project Management Plan Updates

V. Project Document Updates

 Ans 3)
Project Quality Management
Project Quality Management includes the processes and activities of the performing
organization that determines quality policies, objectives, and responsibilities so that the project will
satisfy the needs for which it was undertaken.

There are three Critical Project Quality Management Processes:

1.) Quality Planning

2.) Perform Quality Assurance
3.) Perform Quality Control

1.) Plan Quality Management

Process of identifying quality requirements and standards for the project and its deliverables
and documenting how the project will demonstrate compliance with quality requirements

INPUTS
I. Project management plan
a) Scope Baseline
b) Work breakdown structure
c) WBS Dictionary
d) Schedule baseline
e) Cost baseline
f) Other management plans

I. Stakeholder register
II. Risk register
III. Requirements documentation
IV. Enterprise environmental factors
V. Organizational process

TOOLS & TECHNIQUES

I. Cost-Benefit Analysis: -
A cost-benefit analysis for each quality activity compares the cost of the quality step to
the expected benefit.
 II. Cost of quality

a. Cost of Conformance means delivering products that meet requirements and fitness for
use.
b. Cost of Non-Conformance means taking responsibility for failures or not meeting quality
expectations.

III. Seven basic quality tools

a. Cause-and-effect diagrams
b. Flowcharts
c. Check sheets
d. Pareto diagrams
e. Histograms
f. Control charts
g. Scatter diagrams

IV. Benchmarking

V. Design of experiments

VI. Statistical sampling

VII. Additional quality planning tools

a. Brainstorming
b. Force field analysis
c. Nominal group technique
d. Quality management and control tools

VIII. Meetings

OUTPUTS
I. Quality Management Plan:-
The quality management plan is a component of the project management plan that describes
how the organization’s quality policies will be implemented.

II. Process Improvement Plan

a. Process boundaries.
 b. Process configuration.
c. Process metrics.
d. Targets for improved performance.
III. Quality Metrics
IV. Quality Checklists
V. Project Documents Updates

2.) Perform Quality Assurance

Quality Assurance (QA) is concerned with establishing, evaluating, improving and maintaining the
quality of the processes. Once processes are consistent, QA "assure" that the same level of quality will
be incorporated into each product produced by that process by use of different tools and techniques.

INPUTS
I. Quality management plan

II. Process improvement plan

III. Quality metrics

IV. Quality control measurements

V. Project documents

TOOLS & TECHNIQUES

I. Quality management & control tools

a. Affinity Diagrams
b. Process decision program charts (PDPC)
c. Interrelationship digraphs
d. Tree diagrams
e. Prioritization matrices
f. Activity network diagrams
g. Matrix diagrams
a) Affinity Diagrams

It is an orderly extension of a structured brainstorming session to generate ideas

b) Process decision program charts (PDPC)

Systematically identifies what might go wrong in a plan under development. By using

PDPC, you can either revise the plan to avoid the problems or be ready with the best response
when a problem occurs.

• Develop a tree diagram of the proposed plan

• For each task on the third level, brainstorm what could go wrong

• Review all the potential problems and eliminate any that are insignificant

• For each potential problem, brainstorm possible countermeasures

• Decide how practical each countermeasure is. Use criteria such as cost, time required,
ease of implementation and effectiveness. Mark impractical countermeasures with an X
and practical ones with an O.

c) Interrelationship digraphs

Show cause-and-effect relationships, and help analyze the natural links between different
aspects of a complex situation
 1. Create a Problem Statement
2. Brainstorm Ideas
3. Determine Relationships Between Ideas
4. Analyze the Diagram

d) Tree diagrams

It is used to figure out all the various tasks that must be undertaken to achieve a given
objective

e) Prioritization matrices

1 2 3 4

f) Activity network diagrams

 g) Matrix diagrams

II. Quality audits

III. Process analysis

OUTPUTS
 Change Requests

 Project Management Plan Updates

 Project Documents Updates

 Organizational Process Assets Updates

3.) Perform Quality Control

Control Quality is the process of monitoring and recording results of executing the quality
activities to assess performance and recommend necessary changes

INPUTS
I. Project management plan

II. Quality Metrics

III. Quality Checklist

IV. Work performance data

 V. Approved Change Requests

VI. Deliverables

VII. Project Documents

VIII. Organizational Process Assets

TOOLS & TECHNIQUES

I. Seven Basic Quality Tools

II. Statistical Sampling

III. Inspection

IV. Approved Change Requests Review

OUTPUTS
I. Quality Control Measurements

II. Verified Deliverables

III. Work Performance Information

IV. Validated Changes

V. Change Requests

VI. Project Management Plan Updates

VII. Project Documents Updates

VIII. Organizational Process Assets Updates