Scribd
Upload
12 views5 pages

Part 1 Scope

Uploaded by

jnznthv79n
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views5 pages

Part 1 Scope

Uploaded by

jnznthv79n
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Part 1: Scope

1. Project Justification
Why you select a project? Convince why you are making this project?
• Projects come based on:
Market Demand Upgrade to existing New Legal Customer
system/project/product development Requirement Request
Personal need, Financial aspects and profits (if Technological Strategies of Priorities
Business need, your priority is money, you will Advance government, (helping/charity)
social need select the profitable project) goals, and
objectives
• By having an initial business case showing the benefits we can decide to implement the
project
• By making an initial feasibility study, we can decide if the project is feasible (is the project
worth doing, based on its importance to us, is it beneficial to our strategy)
Project: Building a house Developing a new app
Example:
Justification: Personal/family need Technological advance

2. Project Scope Management Processes

Collectng Creatng the Validatng Controlling


Planning scope Defning scope
requirements WBS scope scope

• Planning scope: determining how the project’s scope and requirements will be managed
(based on policies and strategies).
• Collectng requirements: defining the features and functions of the products and
processes to create them.
• Defning scope: reviewing the project charter, requirements documents, and organizatonal
process assets to create a scope statement.
• Creatng the WBS: subdividing the major project deliverables into smaller components.
• Validatng scope: accepting the project deliverables.
• Controlling scope: controlling changes to project scope.
3. Planning scope management
The project team uses expert judgment and meetings to develop the scope management
plan and the requirements management plan to agree on the below:
• How to prepare a detailed project scope statement
• How to create, maintain and approve the WBS
• How to obtain formal acceptance of the deliverables
• How to control requests for changes

4. Requirements
How to identify the requirements:
• Requirements: are conditions or capabilities that must be met by the project or present in
the product or service.
• Requirements are collected by:
- Interviewing - Focus groups and facilitated workshops - Prototyping

- Observation - Questionnaires and surveys - Benchmarking

Requirement Traceability Matrix: The requirements management plan:


• A list showing all the requirements, various • Documents how project requirements will be
atributes, and the status of the requirements analyzed, documented, and managed

Example: Mobile phone requirements


10,000 mAh battery iOS operating system 5-inch screen size 512 GB memory

5. Scope Definition
• Scope refers to all the work involved in creatng the products of the project and the
processes used to create them.

Project scope statements include:


A. Product scope B. Product user C. Project deliverables D. Boundaries, constraints, and
description acceptance criteria assumptions
5.1. Project Scope and Product scope description:
Explain the Product scope:
• The product scope is between the project manager and project owner, both know what
they will do and what they will get (No assumptions).
• It describes the product or service (features, functions, characteristics, and standards) in
general it states the requirements.
• Completion of the product scope is measured against the product requirements.
Product: Product scope:
Examples: Phone Screen size, battery backup, camera type, memory, processor speed
House Size of building, number of rooms, number of toilets, paint color

Explain the Project scope:


• It is between the project manager and project team.
• The project scope includes all the work (activities) that must be done to deliver a product
with the specified features and functions.
• Therefore, WBS is developed to know all the activities.
• Completion of the project scope is measured against the project plan.
Project: Project scope:
Example:
Construct a bridge How exactly to build the bridge as per all the requirements

5.2. Deliverables
Explain the deliverable:
• It is a product produced as part of a project, such as hardware or hardware, planning
document, or meeting minutes.
• It is developed based on requirements
Project: Deliverables:
Example:
Car Car body, engine, gear
5.3. Acceptance criteria
The conditions that the project must meet to be accepted.
5.4. Boundaries, Constraints and Assumptions
Constraints: is a restriction that will affect the performance of the project
Assumptions: factors that are considered to be true, real, or certain

5. Work Breakdown Structure

Explain the Wok breakdown structure:


• Based on the scope statement and requirements, WBS is developed.
• It is subdividing the major project deliverables into smaller components in order that:
- Planning can be performed - Costs and budgets can be established
- Objectives can be linked to available resources - Specific responsibility can be assigned

Approaches to Developing WBS:


Using guidelines organizatons guidelines for preparing WBS.
The analogy approach Review WBSs of similar projects.
Example: Construction companies can use the same WBS for all buildings projects
The top-down approach Start with the largest items of the project and break them down
The botom-up approach Start with the specifc tasks and roll them up
Mind-mapping approach is a technique that uses branches radiatng out from a core idea to structure ideas

Work package: Is a task at the lowest level of the WBS.


WBS code: Numbers added to the project tasks. 1.1 1.2 1.3....
WBS dictionary: Is a document that describes detailed information about each WBS item.
Scope baseline: The approved scope statement and WBS and WBS dictionary.
WBS Benefits:
• Helps new team members see their • Facilitates communication among the project
role team and stakeholder
• Helps prevent changes • Provides a basis for estimating staff, cost, and
time

6. Validating scope
• Scope validation involves formal acceptance of the completed project deliverables
• Achieved by a customer inspection and then sign-off on key deliverables

7. Controlling Scope
• Scope control involves controlling changes to the project scope
• Goals of scope control are:
- To control the factors that cause scope changes
- To assure changes are processed according to procedures
- To manage changes when they occur

8. Best practices for avoiding scope problems


- Keep the scope realistic
- Involve users in project management
- Use off-the-shelf hardware and software
- Follow good project management processes

You might also like