Fundamentals Of Project Management

  • Uploaded by: Yasi Eemo
  • 0
  • 0
  • May 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Fundamentals Of Project Management as PDF for free.

More details

  • Words: 316
  • Pages: 12
FUNDAMENTALS OF PROJECT MANAGEMENT LECTURE 6: PROJECT SCOPE MANAGEMENT(VALIDATE AND CONTROL SCOPE) COURSE INSTRUCTOR: OWAIS TAHIR

VALIDATE SCOPE • Process of formal acceptance of the deliverables and/or product, service or result that was to be produced as a result of the project. • Each deliverable and then the final product is validated for scope • Deliverables are verified in the control quality process by the QC team. • These are then forwarded to the scope validation • Difference between QC and scope validation is QC is concerned with correctness of deliverables • Scope validation is concerned with acceptance of deliverables

Inputs • Project Management Plan (scope management plan, scope baseline) • Requirements documentation • Requirements Traceability Matrix • Quality Reports • Lessons Learnt Database. From current project • Verified Deliverables (QC) • Work Performance Data (usually from QC)

Tools and Techniques • Inspection. (reviews, audits, walkthroughs etc) • Group Decision Making Techniques. For example voting.

Outputs • Accepted Deliverables • Change Requests • Work Performance Information. How many deliverables have been accepted, what were conditions of acceptance, what is acceptance rate and acceptance ratio and why. • Project Document updates for example lessons learnt database, requirements traceability matrix.

Control Scope • Basically to avoid scope creep • Scope Creep is “uncontrolled expansion to product or project scope without adjustments to time, cost and resources”. • Basically change control for scope

Inputs • • • • •

Project Management Plan Requirements Documentation Requirements Traceability Matrix Work Performance Data OPA’s

Tools and Techniques • Variance Analysis. How much variance exists from the planned value and is it within the threshold limit. • Trend Analysis. With time, is the performance of the project improving or deteriorating.

Outputs • Work Performance Information • Change Requests • Project Management Plan updates (scope baselines, other baselines etc) • Project document updates (requirements documentation, traceability matrix, lessons learnt database.)



END OF LECTURE

Related Documents


More Documents from ""