Professional Documents
Culture Documents
Week 4 - Scope Management
Week 4 - Scope Management
1
11/16/2021
Configuration Management
• Needed on software projects:
• numerous artifacts are produced
• A supporting process that runs alongside the development process.
• Assist in current / updated version
Version Control
management system:
Characteristics of a
good configuration
Auditable
Centrally Located
Secure
Access to all Team members
Accessible to remote teams
Continues integration
Artifact Location
Software Project Management – Asst Prof Athar Mohsin- NUST 3
Configuration Management
• Configuration Management:
• Need to store, archive, identify, retrieve, and release work products and
information items for the entire project team
• Used by the entire project team,
Year and
Project Documen Documen Activity Documen Version
time Author
name t name t number identifier t type number
stamp
2
11/16/2021
Requirements Requirements
Requirements
Version 1 Version 2
Project 1
Construction Construction
Construction
Version 1 Version 2
3
11/16/2021
Define Scope The process of developing a detailed description of the project and product.
The process of subdividing project deliverables and project work into smaller, more
Create WBS
manageable components.
Validate Scope The process of formalizing acceptance of the completed project deliverables.
The process of monitoring the status of the project and product scope and
Control Scope
managing changes to the scope baseline
Expert judgment .
Tools &
Data analysis .
Techniques .
Meetings .
4
11/16/2021
Project Scope
• Importance: Most Project failed due to poorly
Assignment # 1
defined scope
Question 2
• Intangible nature of software product
• Explain Project Scope
• Requirements keep changing/ Poorly defined
Requirements Management as
• Disrupts development activity Knowledge Area
• Susceptibility to defects • Identify the Input, Tools
• Increased volume of the project work & Techniques and
• Cost escalation and an elongation of the schedule Output of all Tasks
• Plan Scope Management covering all process
groups.
• The process of creating a scope management
plan that documents how the project and product • Identify the Difference
scope will be defined, validated, and controlled. between Product Scope
& Project Scope
5
11/16/2021
Scope Management
• SCOPE MANAGEMENT PLAN
• A component of the project management plan that describes:
• How the scope will be defined, developed, monitored, controlled, and validated.
• The components of a scope management plan include:
• Process for preparing a project scope statement;
• Process that enables the creation of the WBS from the detailed project scope statement;
• Process that establishes how the scope baseline will be approved and maintained; and
• Process that specifies how formal acceptance of the completed project deliverables will be
obtained.
6
11/16/2021
7
11/16/2021
8
11/16/2021
WBS Dictionary
Descriptio
• Most of the Assumptio
ns and
n of work
Schedule
information included constraints
milestones
,
,
in the WBS
dictionary:
• Created by other Responsib
Associated
le
processes and organizatio
schedule
activities
n
added to this WBS
Dictionary
document at a later
stage
• Information in the Resources Acceptanc
WBS dictionary may required e criteria
9
11/16/2021
Todays Objective
• Last Lecture Recap
• Project integration Management Process group
• Project Configuration Management
• Scope Management
• This Session Agenda
• Project Risk Management
• Ref:
• Chapter 4 Software Project Management By Dr Ashfaque
• Chapter 4 Project Management Body of Knowledge
Risk
Predicting the future is impossible!!!
Possibility
of not
achieving
•Target Components
Risk
of Projects
• Budget,
Planned but • Time,
non
occurrence
Risk Uncertainty
• Resources,
• Quality,
• Technology
Unplanned
Happening
10
11/16/2021
Risk
• Risk can be either negative or positive:
• Negative risks, also referred to as threats,
• Potentially have a detrimental effect on one or more of the project objectives, such as
causing you to miss a deadline.
• Positive risks, also referred to as opportunities,
• Potentially have a beneficial effect on project objectives, such as allowing you to complete
a task with fewer personnel than you originally planned.
Risk Management
Risk Management
Assess the Monitor the status Inform key
Develop plans for
potential effects of of your project’s audiences of all
Identify risks. mitigating the
those risks on risks throughout risks involved with
effects of the risks.
your project. performance. your project.
Determine whether
existing risks are still Explain the status
Determine which Consider what can Decide how you can
present, whether the and potential effect
aspects of your plan happen if those protect your project
likelihood of these of all project risks —
or project aspects don’t work from the
risks is increasing or from the initial
environment may out the way you consequences of
decreasing, and concept to the
change. envision. risks.
whether new risks project’s completion.
are arising.
11
11/16/2021
Reference
• Chapter 4 Project Management Body of Knowledge
• Chapter 1 & 2 Software Project Management by Dr Ashfaque
• https://www.projectmanager.com/blog/project-charter/
•
12