Software Project Management SPM

1
Software Project Management (SPM)

• Lecture 5
• Project Scope Management
• Dr. Daniel Keret

2
Reading Assignment

• A Guide to the Project Management Body of
  Knowledge, PMI Publications, 3rd Edition, 2004
• Chapter 5

3
Scope Management

• Project Scope definition
• Product Scope The Features and Functions that
  Characterize the Product
• Project Scope The WORK that Needs to be
  Accomplished to Deliver the Product
• Work Breakdown Structure (WBS)
• Scope Control
• Scope Verification

4
Scope Definition

• Preparation of a Detailed Project Scope
  Definition Based On
• Major Deliverables
• Assumptions
• Constrains
• Stakeholders Needs, Wants and Expectations are
  Converted into Requirements
• Approved Change Requests CAN Change the Scope
  Definition.
• Tools and Techniques
• Product Analysis Translating Objectives and
  Requirements into Tangible Deliverables
• Alternatives Identifications- Different
  Alternatives to Execute the Work
• Expert Judgment
• Stakeholders Analysis- Select, Prioritize and
  Quantified the Needs, Wants and Expectations.

5
Scope Definition - Content

• Project Scope Statement
• Detailed Project Deliverables Work Needs to
  Accomplish the Deliverables and What Work is
  Excluded
• Enables the Project Team to Perform More Detailed
  Planning, Guide the Project Team How to Execute
  the Work and Provide the Baseline for the Project
  Evaluation
• Requested Changes
• Project Scope Management Plan (Updates)
• Changes Due to Approved Change Requests

6
Scope Definition Appendixes

• Project Objectives Measurable Success Criteria.
  (Business, Cost, Schedule, Quality, Technical
  Etc.)
• Product Scope Description Characteristic of the
  Product/Service, Specifications
• Project Requirements Conditions to Satisfy
  Contract, Standards, Specifications, Legal Etc.
• Project Boundaries What includes within the
  boundaries of the project, What is excluded.
• Project Deliverables Outputs that Compromise
  the Product/Service of the Project. Other Project
  Outputs such as Management Reports,
  Documentation.
• Project Constraints Predefined Budget, Imposed
  Dates/Milestones,Performance Criteria,
  Contractual Constrains Etc.

7
Scope Definition Appendixes (cont)

• Project Assumptions The Assumptions and the
  Consequences if they Appears to be False.
• Initial Project Organization
• Initial Defined Risks
• Scheduled Milestones
• Fund Limitation
• Cost Estimate
• Project Configuration Control Requirements
  Configuration Management and Change Control to be
  Implemented
• Project Specifications Identify the Specs
  Document that the Project Should Comply
• Approval Requirement Applies to Objectives,
  Deliverables, Documents, Work

8
Work Breakdown Structure (WBS)

• Deliverable Hierarchical Decomposition of the
  Work to be Executed By the Project Team
• The Lower Level WBS components (Tasks) Can Be
  Scheduled, Cost Estimated, Monitored and
  Controlled.
• Few Approaches Are Possible. Examples
• Software Process Steps Products Components
• Software Products Components Process Steps
• Products Software Components, User Manuals,
  Integration, Acceptance Testing, Conversion.
• Component Detail Design, Code, Unit Test.
• Process Steps Programming Dossiers, Coding,
  Programmer Tests, Unit Tests

9
WBS ExampleSoftware Process Steps Products
- Components
10
WBS Objectives Content

• Objectives
• Cost Estimating All Activities will be
  Estimated. Roll Up Costs of individual WBS to
  Overall Cost.
• Cost Accounting Determine Cost of Each Element.
  Assign Each Cost to the Appropriate Cost Center.
• Schedule Planning
• Resource Planning
• Content
• Identify the work expected
• Staffing Requirements
• Name of Responsible Individuals
• Schedule ( Duration)
• Budget Assigned
• Acceptance Criteria
• Etc.

11
Scope Control

• Influencing the Factors that Create Scope Changes
• Controlling the Impact of the Scope Changes
• Manage the Actual Changes Its Integrations with
  All the Project Processes
• Change Control System is Used to Track the Scope
  Change
• Documentation
• Tracking
• Approval
• Monitor Contractual Obligations Due to the Scope
  Change
• Scope Change Requires
• Variance Analysis (assess the magnitude of the
  change)
• Preplanning (Modifications to WBS, Scope
  Statement, Management Plan)
• Configuration Management System (Reports
  Implementation Status and Deliverables)

12
Scope Verification

• Stakeholders Formal Acceptance of the Project
  Scope and Deliverables
• Product Review (Audit, Walkthrough) Measuring,
  Examining and Verifying Compliance with
  Requirements and Product acceptance Criteria
• Outcome of the Scope Verification Can Be
  Requested Changes and Recommended Corrective
  Actions

13
Main Steps to Build a Win-Win Set of
Requirements

• Identify Success-Critical Stakeholders,
• Identify Stakeholders Win Conditions.
• Identify Win Condition Conflict Issues,
• Negotiate Top-Level Win-Win Agreement,
• Invent Options for Mutual Gains,
• Explore Option Trade-Offs,
• Manage Expectations,
• Incorporate Win-Win Agreements into
  Specifications and Plans,
• Confront and Resolve New Win-Loss, Loss-Loss Risk
  Items.