Project Integration Management (Project Charter)

Project Stakeholder Management (Identify SHs)

Project Scope Management (planning Processes)
Point to Ponder:
“If you do what you love to do,
you’ll never work a day in your
life.”
Develop Project Charter
 Input: (Pre Project Activities)
Business Document: Source of information about
project objectives
and how the project will contribute to Project Goals
Business Case
Market demand, Technical advance, Legal,
Customer or Govt. Social)
 Product Scope Description (Product / Service / Result)
 Strategic Plan (Goal, Vision, Mission)
 Cost Benefit Analysis (feasibility)
 Agreements (MoUs, Contracts etc. If external customer)
 EEF Portfolio / Program & OPA
 Develop Project Charter cont-1…
 Tools & Techniques (to develop charter)
 Expert Judgment
 (Industry/Focus area of the project, Duration & Budget estimation,
Benefit Measurement, Risk identification)
 Data Gathering
 Brainstorming (Idea generation & analysis)
 Focus Group (Stakeholders & SMEs)
 Interviews (Assumptions or Constraints, Approval Criteria – SHs)
 Interpersonal & Team Skills
 Conflict Management
 Facilitation
 Meeting Management
 Meetings (develop milestones, key deliverables, Success criteria etc.)
 Develop Project Charter cont-2…
 Output:
 Project Charter:
 Project Purpose
 Measurable Project Objectives & Related Success Criteria
 High level requirements.
 High level Project Description, Boundaries and Key deliverables
 High level risks
 Summary milestones
 Summary budget
 Name & Authority of the Sponsor or other persons authorizing the
project charter
 Project Criteria (Conditions)
 Project Approval Criteria (who decides its success and who signs off)
 Assumption Log:
 Used to record all assumptions & Constraints throughout the project life
cycle
What is the difference between Assumptions &
Constraints?
 Assumptions:
 Assumptions play an important role in developing the Risk Management Plan.
Therefore, as a project manager you must collect and identify as many
assumptions as you can. It will assist you in developing a sound risk
management plan. The following are a few examples of assumptions:
 You will get all resources required by you.
 During the rainy season, cheap labor will be available.
 All important Stakeholders will come to the next meeting.

 Constraints:
 Constraints are limitations imposed on the project, such as the limitation of
cost, schedule, or resources, and you have to work within the boundaries
restricted by these constraints. The PMBOK Guide recognizes six project
constraints: scope, quality, schedule, budget, resource, and risk.
 Example: (Anybody?)
Identify Stakeholders
 Input:
 Project Charter
 Business Case
 Benefits Management Plan
 Agreements
 EEF & OPA

 Tools & Techniques:

 Expert Judgement
 Policies & Power Structure in the organization
 Knowledge of the environment & culture of the organization
 Knowledge of the industry
 Knowledge of individual team member contribution and expertise
Identify Stakeholders … Cont-1
 Output:
 Stakeholder Register
 Identification Information
 Name, Org. Position, Location, Contact Details, Role on project

 Assessment Information
 Major requirements, Expectations, influence when & where and
impact
 Stakeholder Classification
 Internal / external, Role identified by the Project Manager
Project Scope
Management
Where are we
 We have completed the initiation process
We are ready to start the Project Planning Process
 Purpose of this Lecture:
 Defining Project Goals & Objectives
 Discovering Requirement
 Agreeing on Deliverables
 Determining Assumptions & Constraints
 Compiling the Project Scope Statement
 Creation of WBS and Scope Baseline
 What is Scope?
 Project scope –The work that must be done in order to deliver a product
with the specified features and functions.

 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, with all the requirements and
characteristics agreed upon.

 Project Scope Management is primarily concerned with defining and

controlling what is and is not included in the project.
Plan Scope Management

?
COLLECT REQUIREMENTS
How requirements can be collected?
COLLECT REQUIREMENTS
 How do you collect requirements? T & T
 Expert Judgement
 Data Gathering Techniques: (Directly with stakeholders)
 Brain Storming
 Interviews
 Focus Group (SMEs)
 Questionnaires & Surveys (Large, dispersed and quick response)
 Benchmarking (Comparable Organizations)
 Data Analysis:
 Document Analysis
 Decision Making:
 Voting
 Unanimity, Majority, Plurality, Autocratic & Multicriteria
Decision analysis (Risk level, uncertainty, impact etc)
Collect Requirements … Cont-1
 Data Representation:
 Affinity Diagram
 Mind Mapping
 Interpersonal & Team Skills:
 NGT
 (Question/Problem, silently write down ideas)
 Moderator writes down ideas on flip chart
 Each idea is discussed for clear understanding
 Voting takes place on scale 1-5, highest is selected
 Observation / Conversation
 Facilitation: JAD, QFD
 Context Diagram
 PROTOTYPES (early feedback by providing a working model)
 Output:
 Requirement documentation
 Requirement Traceability Matrix
Collect Requirements Outputs
1. Requirement Documentation
Business Requirements
Stakeholders Requirements
Solution Requirements (Functional & Non-Functional)
Project Requirements
Quality Requirement
 Business need or opportunity to be seized
 Project objectives for traceability
 Functional requirements (business processes, information)
 Non-functional requirements (level of services, performance, safety)
 Quality requirements
 Acceptance criteria
 Business rules
 Impact of other organizational area, sales, technology group
 Support and training requirements
 Requirements assumptions and constraints
Collect Requirements
2. Requirement Traceability Matrix
 A table that links requirements to their origin and traces them
throughout the project life cycle.
 It helps to ensure that each requirement adds business value by linking it
to the business and projective objectives.
 It provides a mean to track requirements throughout the project life
cycle.
 Help to ensure that requirements approved in the requirement
documents are delivered at the end of the project.
 It provides a structure for managing changes to the product scope.

Attributes are associated with each requirement and recorded in the

requirement traceability matrix; such as: a unique identifier, textural
description of each requirement, rationale of inclusion, owner, source,
priority, version, current status and date completed.
Thank You Any Questions?

Next Lecture:
Project Time Management