System Implementation – From Design Specification to Program Deliverable

The design specification could be quite general to describe logical flow of a system. The work item would be divided to smaller work items and they could be validated with the design specification. The validation would be transferred into test plan.


  • Transform System Design Specification into Smaller Work Items.
  • Develop System according to Work Items
  • Prepare Test Plan according to Work Items
  • Unit Test Program Development
  • Commit Source Code

Control Scope

The process of monitoring the status of the project and product scope and managing changes to the scope baseline.

Assessing additional requirement by the customer or proactively overlooking the project scope.


  • Project Management Plan
  • Requirement documentation
  • Requirement traceability matrix
  • Work performance data
  • Organization process assets


  • Variance Analysis


  • Work performance information
  • Change requests
  • Project management plan
  • project document update
  • organizational process assets update


Validate Scope

The process of formalizing acceptance of the completed project deliverables.

Gain formal acceptance of deliverables from customer/stakeholder. e.g. UAT.

Validate Scope is primarily concerned with acceptance of the deliverables while Control Quality is primarily concerned with correctness of the deliverables and meeting the quality requirement specified for the deliverables.


  • Project Management Plan
  • Requirement Documentation
  • Requirement Traceability Matrix
  • Verified Deliverables
  • Work Performance Data


  • Inspection
  • Group Decision-making technique


  • Accepted Deliverables
  • Change Requests
  • Work Performance Information
  • Project Document Updates

Create WBS (Work Breakdown Structure)

deliverable-oriented hierachical decomposition of the work

The Process of subdividing project deliverables and project work into smaller, more manageable components.

Scope Baseline

  • Scope Statement
  • WBS – hierarchical decomposition of the total scope of work
  • WBS Dictionary – a document that provides detailed deliverable, activity and scheduling information of each component in the WBS.

Rules of Thumb for task sizing

  • Should not smaller than 1 man day or larger than 10
  • Should not longer than the reporting period
  • Further decompose a task only if it can facilitate to estimate assign and track it
  • Sometimes, a very small task sizing required for tight control.


  • Scope management plan
  • project scope statement
  • requirement document
  • enterprise environmental factors
  • organizational process assets


  • Decomposition
  • Expert Judgement


  • Scope baseline
  • Project document update

Define Scope

The process of developing a detailed description of the project or product.

Outlines what will be and what will not be included in the deliverables, including details of risks, constraints and assumptions.

  • All Work required, and only the work required.
  • what is NOT included in the project (Highly Recommended)
    • Mentioned.
    • Feedback to user. Black and White to protect myself.

The important primary means is to understand and manage stakeholder expections.

Project Scope Statement

  • Product Scope Description
  • Project Deliverables
  • Project Boundaries
  • Product Acceptance Criteria
  • Project Contraints
  • Project Assumptions


  • Scope Management Plan
  • Project Charter
  • Requirement Document
  • Organization Process Assets


  • Expert Judgement
  • Product Analysis
  • Alternative Generation
  • Facilitated Workshops


  • Project Scope Statement
  • Project Document Updates

Collect Requirement

The process of determining , documenting and managing stakeholder needs and requirements to meet project objectives.

Type of Requirement

  • Business Requirement
  • Stakeholder Requirement
  • Solution Requirement
  • Transitional requirement
  • Project Requirement
  • Quality Requirement


  • Scope Management Plan
  • Requirements Management Plan
  • Stakeholder Management Plan
  • Plan Charter
  • Stakeholder Register


  • Interviews
  • Focus Group
  • Workshops
  • Questionnaires and Surveys
  • Observations
  • Benchmarking
  • Prototypes
  • Context Diagram
  • Document Analysis
  • Quality Function Deployment
  • Joint Application Design


  • Requirement Documentation
  • Requirement Traceability Matrix

Plan Scope Management

The process of creating a scope management plan that document how the project scope is defined, validated and controlled.


  • Project Management Plan
  • Project Charter
  • Enterprise Environmental Factors
  • Organization Process Assets


  • Expert Judgement
  • Meetings


  • Scope Management Plan
  • Requirement Management Plan

Perform Integrated Change Control

It is a process of reviewing all change requests, approving changes and managing changes to deliverables, organizational process assets, project documents and communicating their disposition.

A Change Control Board (CCB) perform the integrated change control process which is responsible for reviewing, evaluating, approving, delaying or rejecting changes to the project, and for recording and communicating such decision.

Approved Change Request can require new or revised cost estimates, activity sequences, schedule dates, resource requirements and analysis of risk response alternatives.

Maintaining the integrity of baselines by releasing only approved changes for incorporation into project plans and documents.