Tải bản đầy đủ (.pptx) (16 trang)

WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management

Bạn đang xem bản rút gọn của tài liệu. Xem và tải ngay bản đầy đủ của tài liệu tại đây (2.18 MB, 16 trang )

<span class="text_page_counter">Trang 1</span><div class="page_container" data-page="1">

SCOPE MANAGEMENT

<small>DEMARCATION OF WORK</small>

</div><span class="text_page_counter">Trang 2</span><div class="page_container" data-page="2">

WHAT IS SCOPE OF WORK & SCOPE MANAGEMENT

• Scope defines the who, what, when, where and how

<small>• Product scope: feature and function that characterize a product, service or result</small>

<small>• Project scope: is the work that project team will do to deliver the product</small>

• The Project Scope Management is the process to ensure that a project includes all the work

relevant/appropriate to achieve the project's objectives.

</div><span class="text_page_counter">Trang 3</span><div class="page_container" data-page="3">

<small>CUSTOMER EXPECT</small> <sub>SALE ADVERTISE</sub> <sub>COMPLETE PRODUCT</sub>

WHY IT’S

 Define project needs

 Understand project objective  Define the project scope

</div><span class="text_page_counter">Trang 4</span><div class="page_container" data-page="4">

WHY IT’S IMPORTANT?

• A scope creep is adding features and

functionality to project scope without

addressing the effects on time, costs, and resources, or without customer approval”

</div><span class="text_page_counter">Trang 5</span><div class="page_container" data-page="5">

WHY IT’S

IMPORTANT?

</div><span class="text_page_counter">Trang 6</span><div class="page_container" data-page="6">

CONCE PT

• Predictive life cycle (or classic or

planning focus life cycle): scope fixed. • Adaptive or agile life cycle or

change-driven, scope identify in high level

</div><span class="text_page_counter">Trang 8</span><div class="page_container" data-page="8">

• How the project defined, validated and controlled

• SCOPE MANAGEMENT PLAN - Describe how the scope will be

defined, develop, monitor, control and validate

• REQUIREMENT MANAGEMENT PLAN: to answer question like: Once I have all the requirements, what will I do to analyze, prioritize, manage and track changes to them?

</div><span class="text_page_counter">Trang 9</span><div class="page_container" data-page="9">

<small>• Understand what is needed to satisfy stakeholders, then documenting that understanding </small>

<small>• process of determining, documenting, and managing stakeholder needs and requirements to meet objectives</small>

<small>• REQUIREMENT DOCUMENTATION </small>

<small>describes what needs to be performed and why each requirement is </small>

<small>important on the project. 1 thing must include in acceptance criteria</small>

</div><span class="text_page_counter">Trang 10</span><div class="page_container" data-page="10">

<small>• Developing details description of project and product</small>

<small>• Project scope statement = HERE WHAT WE WILL DO ON THIS </small>

<small>• On plan-driven project, can take a lot of time and involve many expert </small>

<small>judgment, stakeholder and expert outside of organization. </small>

<small>• On change-driven project, it will less detail, but it will have sufficient </small>

<small>detail to define what include/ exclude.</small>

</div><span class="text_page_counter">Trang 11</span><div class="page_container" data-page="11">

CREATE WORK BREAKDOWN

<small>• Dividing project deliverables and project work into smaller, easy to manage </small>

<small>• Decomposition - breaking down the project deliverable into smaller components</small>

<small>• SCOPE BASELINE - approved version of </small>

<small>scope statement, WBS, and WBS dictionary. Only change through formal change control procedure</small>

<small>4.Create WBS</small>

</div><span class="text_page_counter">Trang 12</span><div class="page_container" data-page="12">

<small>• Formal acceptance of the completed project deliverables</small>

<small>• Accepted deliverables: formally signed off and approved by the customer or sponsor. </small>

<small>• Work performance information: Tell how deliverable was created, on time, within budgets, how the resources used compared with </small>

<small>inspect the deliverable for completeness and correctness</small>

<small>Validate scope</small>

<small>building the right product</small>

<small>Make sure that the products meet the customer’s requirements</small>

</div>

×