140 likes | 473 Views
Review. 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.Project scope is the work that needs to be accomplished to deliver a product, service or result with the sp
E N D
1. Project Scope Management 2nd knowledge management
2. Review 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.
Project scope is the work that needs to be accomplished to deliver a product, service or result with the specified features and functions
3. Project Scope Management Processes Include Collect Requirement
Define Scope
Create WBS
Verify Scope
Control Scope
4. COLLECT REQUIREMENTS INPUTS
PROJECT CHARTER
STAKEHOLDER REGISTER
TOOLS AND TECHNIQUES
INTERVIEWS (Directly with stakeholders)
FOCUS GROUPS (prequalified Stakeholders & Subject matter experts)
FACILITATED WORKSHOPS (Focused cross functional stakeholders)
JAD Joint application design (Software), QFD Quality function development (New product development) VOC: Voice of the Customers (customer needs)
GROUP CREATIVITY TECHNIQUES (brainstorming, nominal group technique, Delphi Technique, Idea/mind mapping, Affinity Diagram)
GROUP DECISION MAKING TECHNIQUES (Unanimity, Majority, Plurality, Dictatorship)
QUESTIONNAIRE AND SURVEYS (wide number of respondents)
OBSERVATION (viewing individual in their environment)
PROTOTYPES (early feedback by providing a working model)
5. COLLECT REQUIREMENTS Outputs:
Requirement Documentation
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
Requirement Management Plan
How requirement activities will be planned, tracked & reported
How changes to the product initiated, impact analysis and level of authorization for approval of change
Requirement Prioritization process
6. COLLECT REQUIREMENTS Outputs:
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.
7. DEFINE SCOPE INPUT;
PROJECT CHARTER
RQUIREMENT DOCUMENTATION
ORGANIZATIONAL PROCESS ASSETS (Policies, procedures, archives of project, lessons learnt from previous phases and projects)
TOOLS AND TECHNIQUES
EXPERT JUDGEMENT Used to analyze the info needed to develop project scope statement) (other units within the org., consultants, stakeholders, customers, sponsors, subject matter experts, industry groups)
PRODUCT ANALYSIS ( Product breakdown, requirement analysis, system engineering, value engineering and value analysis)
ALTERNATIVE IDENTIFICATION (different approaches to execute and perform the work of the project)
FACILITATED WORKSHOPS
OUTPUTS
PROJECT SCOPE STATEMENT (Sample provided)
PROJECT DOCUMENT UPDATES (Stakeholder register, requirement document, requirement traceability matrix)
8. CREATE WBS INPUT;
PROJECT SCOPE STATEMENT
REQUIREMENT DOCUMENT
ORGANIZATIONAL PROCESS ASSETS
TOOLS AND TECHNIQUES
DECOMPOSITION : it is the subdivision of project deliverables in to smaller, more manageable components until the work and deliverables are defined to the work package level (lowest level of WBS)
Identify & analyze the deliverables and related work
Structuring and organizing the WBS
Developing the upper WBS level to lower detailed components
Developing and assigning codes to WBS components
Verify that the degree of decomposition of work is necessary and sufficient
OUTPUTS
WBS : It is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team
WBS DICTIONARY (Code, description of work, responsible organization, list of schedule milestones, associated schedule activities, resources required, cost estimates, quality requirements, acceptance criteria)
SCOPE BASELINE: A component of project management plan (PSS, WBS, WBS Dictionary)
PROJECT DOCUMENT UPDATE (includes approved changes)
9. VERIFY SCOPE INPUT
PROJECT MANAGEMENT PLAN
REQUIREMENTS DOCUMENTATION
REQUIREMENTS TRACEABILITY MATRIX
VALIDATED DELIVERABLES
TOOLS AND TECHNIQUES
INSPECTION (Includes activities such as measuring, examining and verifying to determine whether work & deliverables meet requirement and product requirement criteria. Also called: review, product reviews, audits & walkthroughs)
OUTPUTS
ACCEPTED DELIVERABLES
The ones that meet the acceptance criteria are formally signed off and approved.
CHANGE REQUESTS (the once not meet acceptance run through project integrated change control process)
PROJECT DOCUMENT UPDATES
10. CONTROL SCOPEThe process of monitoring status of the project & product scope & managing changes to scope baseline INPUT;
PROJECT MANAGEMENT PLAN
Scope base line is compared to actual
Scope management plan describes how to manage and control
Change management plan
Configuration management plan
Requirement measurement plan
WORK PERFORMANCE INFORMATION
Information about project process
REQUIREMENTS DOCUMENTATION
REQUIEMENT TRACEABILITY MATRIX
ORGANIZATIONAL PROCESS ASSETS
Existing formal & informal scope control related policies, procedures and guidelines
Reporting and monitoring methods to be used
TOOLS AND TECHNIQUES
VARIANCE ANALYSIS: assess the magnitude of variation from original scope baseline.
11. CONTROL SCOPEThe process of monitoring status of the project & product scope & managing changes to scope baseline OUTPUTS
WORK PERFORMANCE MEASUREMENTS (Planned vs Original)
ORGANIZATIONAL PROCESS ASSETS UPDATES
(causes of variance, corrective measures, lesson learned)
CHANGE REQUESTS to the scope baseline or other components of project management plan
PROJECT MANAGEMENT PLAN UPDATES
Scope baseline cost baseline and schedule baselines update,
PROJECT DOCUMENT UPDATES
Requirements documentation
Requirement traceability matrix
12. Revision of the Chapter Discovering Requirements
Requirement gathering Process
Conduct Meetings
Conduct Good Ideas for Phase Two
Critical Success Factors
Identifying Assumptions & Constraints
Key project members availability, Performance, skills
Vendors delivery, uniform quality
Customers involvement and approval
Defining Constraints
Lack of commitment from sponsor
Business interruption
Lack of skilled resources
13. Creating Project Scope Statement Project Overview, including a description of the product of project
Goals of the projects, using SMART formula
Comprehensive list of project deliverables
Comprehensive list of project requirements
Exclusion from Scope
Time and Cost Estimates
Roles and Responsibilities
Assumptions
Product Acceptance Criteria
Constraints
Signatures: Project Sponsor, Project manager, Key stakeholders, customers, vendors
14. Thank you