10 PM-Plan PDF

CNP01L07A
CNP01L07A
Project Management
Project Management Planning

Planning
TRAINING FOR
INFORMATION PROCESSING
NOTES
OKINAWA INTERNATIONAL CENTRE

JAPAN INTERNATIONAL COOPERATION AGENCY
Copyright 2007 NIPPON TELEGRAPH AND TELEPHONE EAST CORPORATION
All products, names and services used in this book may be trademarks or registered
trademarks of their respective owners.
No part of this text book may be copied or reproduced in any way and by any means
without the permission of the copyright holder .
Contents
Project Management Planning .......................................................................... 1
Objectives ........................................................................................................... 2
Contents ............................................................................................................... 3
Chapter 1 Project Planning Outline ............................................................ 1-1
1.1 Purpose of Project Planning 1-2
1.2 Effect of Project Planning 1-10
1.3 Project Plan Outline 1-14
Chapter 2 Project Planning............................................................................. 2-1
2.1 Project Initiating 2-2
2.2 Project Charter Creation 2-4
2.3 Project Plan Creation 2-6
Chapter 3 Project Planning Overview............................................................ 3-1

Project Management Planning
Project Management Planning 1
1
Objectives
Upon completion of this class, you are expected to :
1. Understand elements and procedures for project planning.
2. Understand about project planning that considers the characteristics of a

project.
3. Explain how to apply project planning method in the exercise.
2
Contents
Chapter 1. Project Planning Outline
Chapter 2. Project Planning
Chapter 3. Project Planning Overview
3
1. Project Planning Outline
1.1 Purpose of Project Planning
1.2 Effect of Project Planning
1.3 Project Plan Outline
1. Project Planning Outline 1-1
In this chapter, you are going to recognize the importance of project planning and purpose and
effect of planning in a project.
You are also expected to understand the outline of Project Plan as output of Project
Planning although details will be discussed in chapter 2 Project Planning.

Understand 5 major purposes for project planning

Understand 3 major effects obtained from project planning

Understand project plan outline along the project planning flow
1-1
Various projects
Project (small) Holding Graduation Ceremony Committee

Scope=school
Project (medium) Dam Construction Project

Scope= enterprise and local government
Project (large) NASA Space Station Development Project

Scope=world(earth)
All projects require Planning and it is the key to success
Before we go into the purpose of project planning, lets think about the project plan around us
in general.
As a case of small-size project, Holding Graduation Ceremony Committee can be one of
project plans where the target is limited to a school.
As a case of medium-size project, Dam Construction Project is the one targeting an
enterprise or local government.
As a case of large-size project, NASA Space Station Development Project is one of the
project plans involving multiple nations and scaling to the earth.
System development projects vary from micro-project with small size and budget to national
system development project plan with large size and budget. One thing in common is
whatever the project is, the first threshold to begin any project activity is this project planning
process and cannot be skipped. It isnt an overstatement if the good or bad of planning holds a
key to success.
From the next page, let us consider about the effective project planning which leads project
managers to succeed.
1-2
Five Purposes for Project Planning
Purpose 1: Forming Guideline to Perform Project

Purpose 2: Clarifying the Scope of Project
Purpose 3: Setting up Baseline to Control Project
Purpose 4: Defining Conditions of Project
Purpose 5: Contact and Communication among Stakeholders
The final purpose:

Steer the project to execution and make the project succeed.
There are five purposes for project planning.

Purpose 3: Setting up Baseline to Control Project Execution
The final purpose is to steer the project to execution and make the project succeed.
1-3
Purpose1: Forming Guideline to Perform Project
Each project has its objective(theme), project policy.

It is necessary to clarify these, by creating guidelines before project activity starts.
<Examples of Guideline>
-System development corresponding to legal revision
with the set enforcement date
Assigning highest priority in the development

period as guideline
-Medical system development which saves human life
Assigning highest priority in the highest-level

system quality as guideline
What to do?
Which direction to work?
The first purpose of project planning is Forming guideline to perform a project.

As described before in what is project planning, each project has its objective(theme),
project policy. Before project activity starts, it is necessary to clarify these.
For example, the system development corresponding to legal revision with the set
enforcement date assigns the highest priority of the guideline in the development period. If it
is the medical system development which saves human life, its primary guideline is the
highest-level system quality.
Following the clarification of these, project planning addresses the prospected project
activity in order to develop in minimum cost and period while considering the high output
quality as the project objective.
For the success of the project, it is necessary to make the project team understand what they
should do and which direction they should work to. This is achieved by giving instructions
subsequent to defining the project purpose and goal clearly based on the project plan.
1-4
Themes and Policies of Project
Theme:
Wind Power Generation Project 100% Ecological Energy
in Mohave Desert
Theme:
Wisdom of Nature
Aichi Exposition Preparation Project

Theme:
Bioscientific Apollo Plan
Human Genome Analysis Project

Each Project Policy Varies
Lets consider what is project planning.
Project planning is to depict the theme(objective) the starting project holds and policy the
project should go along. The project theme is for external personnel and policy for internal
ones, clarifying project promoters intention. Lets take a look at these projects.
1) Wind power generation project in Mohave Desert

This is the project started in Mohave Desert, California, U.S., in 1987 and wind power
generation project abroad. It is a model case of energy development project. Theme is 100%
ecological energy and project policy the conversion efficiency improvement to electric
energy! .
2) Aichi Exposition Preparation Project

A typical event is Aichi Exposition Preparation Project, which was held in Aichi March
2005. The theme was wisdom of Nature and the project policy was Pursuit of Relationship
between nature and humans.
3) Human genome analysis project

It is a national research organizations project decoding the combination of all the human
genome information ( 3 billion base alignment) with 5 other nations and typical common
research project. Its theme is Bioscientific Apollo Plan and project policy Earlier and more
precise decoding!.
Each project holds a theme and project policy, clarifying the project promoters intention.
For the success of the project, it is essential to form a project plan reflecting theme and policy.
1-5
Purpose2: Clarifying the Scope of Project
Decide and Clarify Each scope of Input Information, Project Activity
Contents, Output Information
Project
Quality
Scope?
OUT
Balance is
important
Customer
Delivery Cost Product
Business
Needs
Management
Resource Task
Procedure
Scope?
IN
Scope?
The second purpose of project planning is Clarifying the Scope of Project.
In project planning, you need to know what tasks to comprise, how much resources to
divide into each task, how the schedule goes and how much budget to prepare, this should be
planned out in order for the accomplishment.
It is necessary to define the project scope. Mainly,

- Define the target customers and business needs
- Clarify the necessary resources for information system development
Clarifying the QCD management and management procedure of risk
management
- Decide the target product the project produces
1-6
Purpose3: Setting up Baseline to Control Project
Set up the framework to control project proceeding for grasping the project status
and achieving the result as planned
Ex. Effort (plan vs. actual)
Accumulated
Legend
Effort
Plan
Actual
Authorized plan
time
Design Programming Testing
The third purpose is Setting up Baseline to Control Project.
Needless to say, to manage the achievement requires a plan. By comparing the plan and the
result, we can grasp the project status, and control the project proceeding. To set plan values
for this comparing, is the setup of baseline.
Project plan sets up the framework to control project proceeding for grasping the project
status and achieving the result as planned. The early plan values of the project is used to trace
the achievement during the on-going process following the activity start.
For example, it is necessary to look at how the achievement goes along with the planned
line to manage if the development effort actual proceeds as planned or not.
Following the activity start, planned value can be changed corresponding to the obvious
difference between the actual and plan or change requirement due to other factors. The plan
value is compared with the actual value appropriately, which might require the revision at
certain events. The project plan sets up the baseline of such base. The baseline setup is
significant because the degree of the well-planned decides the success/failure of the plan.
1-7
Purpose4: Defining Conditions of Project
Prerequisite, limited condition, hypothetical condition found during

project planning should be written down. we have to clarify when to
decide officially and who has the final responsibility of the provisional
decision.
Prerequisite, limited condition, hypothetical condition should be clearly stated.
The 4th purpose of project planning is Defining Conditions of Project.
Prerequisite, limited condition, hypothetical condition are the factors affecting all the phases
of project planning process.
If prerequisite, limited condition, hypothetical condition are orally decided with a customer
in planning the project, it will be the cause of a trouble and must be clarified. For example, the
hypothetical items may occur in these phases.
At the time of project planning, these should be pointed out.

- What is not clear in planning
- Somewhat clear but not decided
- Something not decided
Following these points distinguished, those decided and undecided should be written down.
It is important to clearly state when to decide or who has the final responsibility about
provisional decision or alternatives in prerequisites.
1-8
Purpose5: Contact and Communication among Stakeholders
In the process of Project Planning, promote communication among

stakeholders to obtain common understanding.
Promoting Communication
The 5th purpose of project planning is Contact and Communication among Stakeholders.
It is necessary to obtain the common understanding in operation of the project. That is the
project plan agreement with stakeholders as people concerned in the project.
It will lead to better contact among the stakeholders, promote communication, and run the
project operation smoothly.
1-9
Three Effects of Project Planning
Effect 1:
Participation in the plan by project members increases the motivation of
objective achievement.
Effect 2:
The agreed plan becomes the common understanding among stakeholders
and establishes as objectivity and persuasiveness.
Effect 3:
The weak point of the project can be found from the whole plan with individual
parts accumulated.
Lets look at the Effect of Project Planning.
There are three major effects of project planning.
Effect 1: Participation in the plan by project members increases the motivation of

objective achievement.
Effect 2: The agreed plan becomes the common understanding among

stakeholders and establishes as objectivity and persuasiveness.
Effect 3: The weak point of the project can be found from the whole plan with
individual parts accumulated.
Lets check these effects one by one from the next page.
1-10
Effect 1: Motivate Project Members
Effect 1:
Participation in the plan by project members increases the motivation of objective
achievement.
Sharing the plan information with all the participants elevates the objective
achievement motivation.
Project plan becomes the action standard for each participant and base for
team consensus in direction to project objective and goal.
This should be done Isnt it better this

by XX? way?
Project Plan is the action standard for each project participant.
The first effect of project planning is Participation in the plan by project members increases
the motivation of objective achievement.
Usually the project manager and group leader are involved in project planning and project
members share the information on authorized project plan.
By clarifying each role and responsibility of project promotion organization and project
participants, project plan becomes the action standard for each participant and base for team
consensus.
Sharing the plan information with all the participants elevates the objective achievement
motivation.
1-11
Effect2 : Share the Common Understanding
Effect 2: Stakeholders can share the Common Understanding
The agreed plan by stakeholders establishes objectivity

and persuasiveness and becomes common understanding
among all stakeholders.
This function can This budget

be substituted by should go to that.
the existing one.
Project plan is trade off of stakeholder requirement items and alternatives.
The second effect of project planning is Share the Common Understanding.
Project plan becomes the common understanding among stakeholders and shared material of
decision making during the project.
For planning, various factors for project execution are effectively harmonized and decided.
The important point here is, the contents decided or agreed upon are in the most cases the trade
off of each stakeholders requirement items and alternatives.
It means the plan agreed by stakeholders establishes objectivity and persuasiveness to
become the shared acknowledgement among all stakeholders.
1-12
Effect 3: The Weak Points can be found
Effect 3: The weak points of the project can be found from the whole plan.
The weak point of the project can be found from the whole plan
with individual parts accumulated. This can be eliminated by managing
one as a risk.
I cannot walk a thin

line like this!
Is the plan as shaky as the tightrope? No trap(risk)?
The third effect of project planning is the weak point can be found from the whole project
plan with individual parts accumulated.
The weak point of the project can be found from the whole plan with individual parts
accumulated.
This should be captured in the early stage and take necessary measures swiftly or manage
one as a risk in case the early solution is not possible and consider future prevention in
advance.
For example, if nothing looks wrong by a look at the schedule, the trap including various
risks and problems can be seen with personnel plan, estimate size, and quality objective etc.,
1-13
What is Project Plan

It is the officially authorized document used as a guideline
to run and control a project.
Main Use
Documentation of prerequisite and decision items at plan
Good communication among stakeholders
Indication of each baseline of authorized scope, cost and schedule
The output created along with the purpose of project planning, and includes all necessary
contents (policies, scope, plan values, conditions, etc.), is Project Plan.
We will take a look at Outline of Project Plan as follows;
Project Plan is distributed by the regulation of the officially authorized communication

management plan(*)
Main use of project plan is:

- Documentation of prerequisite and decision items at plan
- Good communication among stakeholders
- Indication of each baseline of authorized scope, cost and schedule
(*) Communication management plan is the output plan in communication plan process to
specify stakeholder information and communication needs including who, when, and how
information is required, and by who and how such information provided.
1-14
Necessary Information for Project Plan(1/2)
Necessary Information for creating Project Plan
Output from other plan

Other plan
Past actual information
Past
Organization policy information
Constrained condition Organization
technique
Tool and
policy
Prerequisite Constrained
condition
Prerequisite Project
plan
Project Plan Method

Ex.
Stakeholder skill and knowledge
Project Management System
There are five kinds of necessary information in compiling project plan.
- Output from other plan : All the output of plan process

- Past actual information : Actual information of the current development system developed
in the past or the usable past information of the similar system
- Organization policy : Official and unofficial operation policy which may affect any
organization involved in the project
- Constrained condition : Factors which may affect the restriction and alternatives in
correspondence with the project performance (example: the allocated budget in advance)
- Prerequisite : Factors considered as truth, reality, or certainty in planning. (example:
increase in users, opposed-system existence, etc.,)
- Project Plan Method : (example: Standard format, template etc.,)

- Stakeholder skill and knowledge: Useful skill and knowledge each stakeholder holds in
project planning (example: DB expert engineer at time of DBMS decision)
- Project Management System: Tools and technique used to collect, integrate, and distribute
output ( example: operation calculation system etc.,)
1-15
Procedure of Project Plan Creation and Documents
Procedure of project plan creation and Documents
Documents
(Procedure) (Document symbol) A) Project Information
1)Basic Development Policy Formulation BO B) Dev. Purpose/Policy/
2) WBS and Product Definition KM Method/Technology
C) Dev. Schedule
3) Effort Estimate and Scheduling CDE D) Dev. Size
4) Procurement Planning HJ E) Dev. Effort
F) Dev. Cost
5) Cost Planning F G) Organization Chart
6) Cut over Planning K H) S/W Subcontract
I) Quality Target Value
7) Quality Planning IN J) System Configuration
8) Project Plan Wrap-up AGL K) Delivery/Handover
L) Related Dept.
9) Project Plan Review and Publicity All M) WBS Definition
N) Verification/Inspection plan
O) Dev. Risk
The project plan creation procedure is as follows:

1) Basic Development Policy Formulation
2) WBS (*1)and Product Definition
3) Effort Estimate and Scheduling
4) Procurement Planning
5) Cost Planning
6) Cut over Planning
7) Quality Planning
8) Project Plan Wrap-up
9) Project Plan Review and Publicity
*1: WBS : Work Breakdown Structure
1-16
Proc.1: Basic Development Policy Formulation
Documents
A) Project Information
B) Dev. Purpose/Policy/
Clarify the development purpose and Method/Technology
items C) Dev. Schedule
D) Dev. Size
Development Policy Formulation E) Dev. Effort
F) Dev. Cost
G) Organization Chart
Development Risk Concretization H) S/W Subcontract
J) System Configuration
K) Delivery/Handover
L) Related Dept.
M) WBS Definition
N) Verification/Inspection plan
O) Dev. Risk
Lets look at the outline of each procedure of project planning.
The first procedure of project planning Basic Development Policy Formulation handles
these items.
- Clarify the development purpose and items

Clarify development purpose and development contents(development items) from
requirement condition document and planning procedure(*)
- Development policy formulation

Grasp the project requirements from development purpose, development contents,
planning procedure review status, customer hearing and so on and consider the specific
development policy to satisfy quality, cost and delivery.
- Development Risk Concretization

Consider the risk in terms of project characteristics and preventive measure to prevent
envisaged incompatibility from happening based on other projects and former construction
information.
(*) This plan procedure means information strategy plan(SE at earlier stage for a customer)
before we start Development (before project planning), Business process analysis, and Whole
system plan.
1-17
Proc.2: WBS and Product Definition
Documents
Method/Technology
WBS Definition C) Dev. Schedule
D) Dev. Size
Defining Input/output of development E) Dev. Effort
stage F) Dev. Cost
Product Definition H) S/W Subcontract
L) Related Dept.
M) WBS Definition
N) Verification/Inspection Plan
O) Dev. Risk
The 2nd procedure of project planning WBS and Product Definition handles these items.
- WBS Definition
Decide which work to implement in each stage and define WBS.
- Defining input/output of development stage

Clarify the input/output of each development stage based on consideration
status of planning procedure.
- Product Definition
Product includes delivery and handover. The delivery is for a customer and
handover is the product for an operational department. we have to clarify the
delivery to the customer, where and when to deliver. Based on the result adjusted with
the customer of their requirement. Also clarify the handover and when to take
over in a case to offer to the operational department.
1-18
Proc.3: Effort estimate and Scheduling
Documents
Method/Technology
Development Size Estimate C) Dev. Schedule
D) Dev. Size
E) Dev. Effort
Effort Estimate F) Dev. Cost
H) S/W Subcontract
Development Scheduling
L) Related Dept.
M) WBS Definition
O) Dev. Risk
The 3rd procedure of project planning Effort estimate and Scheduling deals with these items.
- Development size estimate

The development size in each operation is estimated in reference to the review status of each
operation in planning procedure and development size of the similar system. Specify the reuse
part and estimate how much the revision size of that will be.
- Effort estimate
The total development effort(=the development size/productivity of the whole project) is
estimated based on the development size and productivity of the whole project. The effort in
each stage is estimated by effort allocation rate per stage, setting up the proper effort per stage
by adopting the calculation value in each stage as necessary, and estimating tool productivity,
system difficulty, and personnel skill.
- Development Scheduling
Formulate development schedule based on the development schedule of the similar systems
equal development size, past achievement of the own project, contents of the current
development, and implementation technology, etc.,
1-19
Proc.4: Procurement planning
Documents
Method/Technology
Procurement plan of computer C) Dev. Schedule
products etc., D) Dev. Size
E) Dev. Effort
Procurement plan of subcontractors F) Dev. Cost
H) S/W Subcontract
L) Related Dept.
M) WBS Definition
O) Dev. Risk
The 4th procedure of project planning Procurement planning handles these items.
- Procurement plan of computer products etc.,

Clarify the work result at plan procedure, volume, schedule, price of development
environment facility and commercial environment facility to purchase .
- Procurement plan of subcontractors

Clarify the contract type, contract stage, subcontractor cost, and effort in each subcontractor
in terms of the required subcontractors.
1-20
Proc.5: Cost Planning
Documents
Method/Technology
C) Dev. Schedule
D) Dev. Size
Cost planning E) Dev. Effort
F) Dev. Cost
H) S/W Subcontract
L) Related Dept.
M) WBS Definition
O) Dev. Risk
The 5th procedure of project planning Cost planning calculates all the necessary cost to
promote the project from each sheet made at effort and procurement planning.
1-21
Proc.6: Cut over Planning
Documents
Method/Technology
C) Dev. Schedule
D) Dev. Size
Cut over Planning E) Dev. Effort
F) Dev. Cost
H) S/W Subcontract
L) Related Dept.
M) WBS Definition
O) Dev. Risk
The 6th procedure of project planning Cut over Planning specifies the work items and period
to implement in the service implementation related work plan following System Test stage.
- Product copy and installation for Operational Test environment construction

- Product copy and installation for service environment construction
- Delivery to customer
- Handover to operation department
1-22
Proc.7: Quality Planning
Documents
Method/Technology
C) Dev. Schedule
Quality Planning D) Dev. Size
E) Dev. Effort
F) Dev. Cost
H) S/W Subcontract
L) Related Dept.
M) WBS Definition
O) Dev. Risk
The 7th procedure of project planning Quality Planning handles these items.
Project manager consider the index, past actual, planned, and so on, then decide the target
value of quality target values:
- Error density in each stage
- Review density in each stage
- Comment density in each stage
- Test density in each stage
- Bug density in each stage
- Bug extraction rate in each stage
The decision base should be clarified.

These quality target values will be discussed in chapter 2.
1-23
Proc.8 : Project plan document wrap-up
Documents
Method/Technology
C) Dev. Schedule
D) Dev. Size
Project plan document wrap-up
E) Dev. Effort
F) Dev. Cost
H) S/W Subcontract
L) Related Dept.
M) WBS Definition
O) Dev. Risk
In the 8th procedure of project planning Project plan document wrap-up,

- Project Information
- Organization Chart
- Related Departments
are made and wrap up as Project Plan in consolidation of the sheets made between 1) and 7)
procedure and planning procedure review status.
This is the time to harvest following all the task procedure, provided this is agriculture.
1-24
Proc.9 : Project Plan Review and Publicity
Documents
B) Dev. Purpose/policy/
Method/Technology
Review C) Dev. Schedule
D) Dev. Size
Authorization E) Dev. Effort
F) Dev. Cost
Publicity H) S/W Subcontract
L) Related Dept.
M) WBS Definition
O) Dev. Risk
In the 9th procedure of project planning Project Plan Review and Publicity, the following
work is implemented.
- Review
Project Manager will review the Project Plan with project group leaders. For necessary
planning items, the customers will join.
- Authorization
The Project Plan will be authorized by project evaluation personnel following the review
completion.
- Publicity
Project Manger publicizes the authorized contents of Project Plan to project members and
share the information.
These are the project planning procedures.
1-25
2. Project Planning
2.1 Project Initiating
2.2 Project Charter Creation
2.3 Project Plan Creation
2. Project Planning 2-1
In this chapter, we will recognize which process the project planning corresponds to in project life
cycle and understand the method from project initiating to project plan creation in a development
project.

Understand the outline of the project initiating process

Understand the contents of project charter and description process.

Understand forms of description methods comprising the project plan.
2-1
What is Project Initiating?

Officially approve to implement the applicable project or the next phase of the project
as the implementation organization (project).
Evaluate to plan the project and the validity of such implementation

to realize the information system.
Clarify the aim of the applicable information system, how to tackle
the project and issues for implementation.
Determine whether to implement one or not by considering
the validity of the planned details.
GO!
Project manager is chosen and appointed
Project charter is issued
Lets look at the first process of the project planning Project Initiating.
The project initiating means to officially approve to implement the applicable project or the next
phase of the project as the project implementation organization.
Specifically, evaluate to plan the project and the validity of such implementation to realize the
information system.
Clarify the aim of the applicable information system, how to tackle the project and issues for
implementation.
Determine whether to implement one or not by considering the validity of the planned details.
Following this, project manager will be chosen and appointed; then project charter will be issued.
Project charter will be discussed later.
2-2
Project Approval
Cases of the project approval
The project is approved if more than one factor of the following exist.
Market
MarketDemand
Demand
Social
SocialNeeds
Needs Business
BusinessNeeds
Needs
Legal
LegalDemand
Demand
Customer
CustomerDemand
Demand
Technological
TechnologicalProgress
Progress
The project is approved if more than one of the following factors exist.
Market demand:
An automaker approves a project to produce high fuel efficiency and low pollution vehicle or
electric car in response to gas supply shortage and/or environmental protection, for example.
Business needs:
An educational training company approves the project to create new training course in response to
the new operations.
Customer demand:
An electric power company approves the project to build a new substation to provide the newly
developed residential and resort areas with the electric power.
Technological progress:
An electronic manufacturer approves a project to develop video, video games, store media in
parallel with computer and memory technology progress.
Legal demand:
A paint maker approves the project to form a guideline to deal with toxic material.
Social needs:
The government approves the project to support the recovery from the natural disaster.
2-3
What is the Project Charter?
It is the document to officially approve the project and

the project initiating organization, the customer in most cases, usually compiles one.
Project Charter Officially

Initiates the project
Approves to use the resources for the activity project manager implements
Explicitly outlines the project objective
Project Charter is the official document.
The Project Charter is the output of project initiating process.
It is the document to officially approve the project and the project initiating organization, the
customer in most cases, usually compiles one.
The Project Charter officially initiates the project, approves to use the resources for the activity
project manager implements, and explicitly outlines the project objective.
2-4
Example of Project Charter
Example of Project Charter
Project Charter
Project Name: Made by:
Project Manager Name: Authorized by: Signature
1) Project Needs
2) Project Objective
3) Related Information
i) Constraint
ii) Precondition
iii) Responsibility and authority
Here is an example of project charter. This is just an example and I will explain each item in the
charter. The positioning of this project is determined depending on who authorizes the charter. The
management of the customer(a person responsible for the contract) usually is the one who authorizes
one.
1)Project needs: 6 cases were pointed in the last page as a case for project commencement approval;
these are market demand, business needs, customer demand, technological progress, legal demand
and social needs. The applicable one of these needs should be put here.
2)Project Objective: Customer Project should be aimed at strategic objective realization and specify
what project it is for, what should be obtained in the end, what is the objective of the result in the
project, and so on.
3)Related information
i) Constraint:
Constraint is the factor to limit the project alternatives. For example, the budget set up
in advance has the possibility to limit the alternatives of scope, staff allocation, and
scheduling.
ii) Precondition:
Precondition is a factor considered to take place with high possibility in planning. For
example, if you know the number of system implementation users increases for sure, it
will affect hardware/software selection, performance objective, and so on.
iii) Responsibility and authority:
Clarify which department bears what authority and how they are related.
2-5
Project Plan configuration
Project Plan Front Page

B) Dev. Purpose/Policy/ H) Software Subcontract
Method/Technology I) Quality Target Value
C) Development Schedule J) System Configuration
D) Development Size K) Delivery/Handover
E) Development Effort L) Related Departments
F) Development Cost M) WBS Definition Table
G) Organization Chart N) Verification/Inspection Plan
O) Development Risk
These are the typical 15 forms.
2.3 Project Plan Creation 2-6
Well move onto how to fill in the project plan forms.
The form of Project Plan bears 15 types.

A) Project Information,
B) Development Purpose/Policy/Method/Technology
C) Development Schedule
D) Development Size
E) Development Effort
F) Development Cost
H) Software Subcontract
L) Related Departments
M) WBS Definition
O) Development Risk
2-6
2.3.1 Forms of Project Plan
Document Name Serial Form Name Category
Symbol
A Project Information Scope

B Development Purpose/Policy/Method/Technology Scope/Integration
C Development Schedule Time
D Development Size Cost
E Development Effort Cost
F Development Cost Cost
Project Plan
G Organization Chart Human Resouce

H Software Subcontract Procurement
I Quality Target Value Quality
J System Confiuration Procurement
K Delivery/Handover Scope
L Related Departments Human Resource
M WBS Defintion Scope
N Verification/Inspection Plan Quality
O Development Risk Risk
2.3.1 Forms of Project Plan 2-7
This table shows forms of project plan. Category indicates which forms related in which purpose
of project plan.
2-7
2.3.2 Project Plan Front Page(1/2)
Title Version 1.01

2)
Issue date 3) 2004/4/1
1)
Update date 4) 2004/5/10
(PROJECT PLAN)
Maintenance
Period 5) 5 years
eProcurament system
(Ver x.x)
Owner 6) Tonkara rin
+81 xxx xxxx

Contact 7) xxx@xxx.xx.jp
2.3.2 Project Plan Front Page 2-8
First, this is the Project Plan Front Page.
The table shows how to fill in. Information Management Items 1) to 7) should be filled in the
Project Plan.
Description items are:

1) Title,
2) Version,
3) Issue date,
4) Update date,
5) Maintenance Period,
6) Owner ,and
7) Contact.
2-8
2.3.2 Project Plan Front Page(2/2)
1)Title
The project(product/construction name) with its abbreviation if any in
parenthesis followed by version.
2) Version
The version created of the Project Plan
3) Issue date
The first issue date of the Project Plan
4) Update date
The most recent update date of the Project Plan
5) Maintenance period
The maintenance period set down by the company or project
6) Owner
Project Plan owner(responsible person)
7) Contact
Owners phone number and e-mail address
2.3.2 Project Plan Front Page 2-9
Lets look at each description items in Project Plan Front Page.
1) Title:
Write product name or construction name with its abbreviation if any in parenthesis followed by
version.
2) Version:
Write the version created of the Project Plan.
3) Issue date:
Write the first issue date of the Project Plan.
4) Update date:
Write the most recent update date of the Project Plan.
5) Maintenance period:
Write the maintenance period set down by the company or project.
6) Owner:
Write Project Plan owner(responsible person).
7) Contact:
Write owners phone number and e-mail address.
2-9
2.3.3 Project Information
(A) Project information
Comissioned Organization Development
Project Name
1) OIC-sales department Project Name 2) OIC eProcure system Project
Project Manager Name 3) Tonkara rin

Project Name
Project Code Abbreviation(Verx.x)
(Product Name/Construction Name)
Project OIC2004WVS101 4) eProcurement System 5) eProcurement(Ver1.0) 6)
Dev. Env.
Hardware Development
Existence 7) None
Development Environment
Equipment Expansion
8) None Commercial Environment
Equipment Expansion 9) None
Contract Contract Type 10)subcontract
Client 11)OIC:Okinawa International Center
Contract Date(Plan/Actual) 12)2004/04/01 2004/04/10
Plan Actual
Schedule Dev. Period (ED to ) 13) 2004/04/01 - 2004/08/31 5months 2004/04/10 - 2004/09/10 5.3month
OT Period 14) 2004/09/01 - 2004/11/30 3months 2004/09/11 - 2004/12/20 3.3months
Shipment Date 15) 2004/08/31 2004/09/10
Client Inspection Start Date 16) 2004/09/01 2004/09/11
Delivery Date
17) 2004/09/07 2004/09/17
Service Start Date 2004/09/08 2004/09/18

18)
2004/07/10
Plan Changed on
19)
2.3.3 Project Information 2-10
This is the Project Information. The chart shows how to fill in.
Mainly the profile information on the project should be written.
Filling-in items are:

1) Commissioned Organization Project Name,
2) Development Organization Project Name,
3) Project Manager name,
4) Project Code,
5) Project Name(product/construction name),
6) Abbreviation (version number),
7) Hardware Development Existence,
8)Development Environment Equipment Expansion,
9)Commercial Equipment Expansion,
10)Contract Type
11)Client
12) Contract Date (Plan/Actual)
13) Development period (Plan/Actual),
14) OT Period (Plan/Actual),
15) Shipment Date (Plan/Actual),
16)Client Inspection Start Date (Plan/Actual),
17) Delivery Date (Plan/Actual),
18)Service Start date (Plan/Actual), and
19)Plan Changed on.
The information determined at Initiating Process Group is between 1) and 6).
2-10
Project Information Description(1/3)
(A) Project Information
1)Commissioned Organization Project Name:
Organization project name commissioned by the client.
2)Development Organization Project Name:
Organization project name commissioned to develop by Commissioned Organization.
3) Project Manager Name:
Project Manager Name of Development organization
4) Project Code:
Project Code assigned internally
5) Project Name(product/construction name):
Development product or construction name
6) Abbreviation (version number):
Project name abbreviation and its version number
7) Hardware Development Existence:
Whether hardware development is included in this development or not
8) Development Environment Equipment Expansion:
Whether Development Environment Equipment is expanded or not
9) Commercial Environment Equipment Expansion:
Whether Commercial Environment Equipment is expanded or not
Each item of project information is explained as above.
Project Information is a sort of profile of the project. All critical factors for carrying forward the
project but actual contents are written in this form.
2-11
10) Contract Type:
Contract type including consignment, subcontract, etc., with client
11) Client:
Customer name
12) Contract Date
Contract date with client Profile in the project
13) Development Period (ED to ST) :
Start date and end date from external design (ED) to system test (ST) completion
14) OT Period :
Start date and end date of operational test (OT) by client for acceptance inspection
15) Shipment Date :j
The date to ship the product following system construction completion
16) Client Inspection Start Date :
The date the client starts inspection after shipment date
17) Delivery Date:
Date to deliver the product to the client following the client inspection completion
18) Service Start Date:
The date to start commercial service
19) Plan Changed on:
The most-recent date when the plan changed during development period
(continued from previous page)
2-12
Milestones to write in Project Information
ED ID IT ST OT
Strategy Requirement P
(External (Internal (Integration (System (Operation Operation
Planning Definition (Programming)
Design) Design) Test) Test) al Test)
12) Contract Date

14)
13) Development Period
OT Period
15) Shipment Date
16) Client Inspection

Start Date
17) Delivery Date
18) Service Start

Schedule Notebook Date
In the Form Project Information , you will write in the major milestones in implementing the
project activity. They are between item12) and 18) and time schedule is shown here.
Usually, there is 12) Contract Date before 13) Development period ,and the Last Date of 13)
Development Period is 15) Shipment Date. The Start Date of 14) OT Period is 16) Client Inspection
Start Date. End Date of 14)OT Period is 17)Delivery Date. Following 17)Delivery Date , the
operation start date is 18) Service Start Date.
2-13
2.3.4 Development Purpose/Policy/Method/Technology(1/2)
(B) Development Purpose/Policy/Method/Technology
Objectives and Contents of Development

Computerize the procurement operation which requires complex proceedings to realize "Simple Public Administration with High Budget Efficiency". The
specific development items are:
1.Computerise series of bidding proceeding(front office operation) from Tender Notice Confirmation to Procurement
2. Computerize series of Tender Notice Issuer side's proceeding(back office operation) such as bidder registration, notice publication, and winning bidder
assignment.
1)
Development Policy
In consideration of budget efficiency, use less expensive and reliable development technology.
Use development technology flexible enough to change operation along with system and legal revision.
Adopt development method to assure reliability due to the operation requiring reliability.
Reuse existing function and technology as much as possible. 2)
Plan Achivement and Evaluation Know-how to succeed

Development Adopt Waterfall type to warrant quality.
Methodology 3)
Development Develop object-oriented technology
program.
Technology Hardware/Software
4)
2.3.4 Development Purpose/Policy/Method/Technology 2-14
Now, Form Development Purpose/Policy/Method/Technology.
This sheet will show a chart of how to enter.

You will enter the policy outline for implementing the project.
The fill-in items include :

1) Objectives and Contents of Development Items,
2) Development Policy,
3) Development Method, and
4) Development Technology.
2-14
2.3.4 Development Purpose/Policy/Method/Technology(2/2)
(B) Development Purpose/Policy/Method/Technology
1) Development Objectives and Contents of Development :

Enter the needs for the project the client sought, in other words, client sides development
purpose, development reasons, and development items to realize these.
2) Development Policy :
Describe how to proceed based on which policy among quality (Q), cost ( C), delivery (D)
management items and which development technology, development methodology, development
standard is selected. Enter project policy due to clients constraint if any.
3) Development Methodology :
Select and Describe the methodology appropriate for the project development size and feature.
(Waterfall, Spiral, Prototyping, etc.,)
4) Development Technology :
Name the type of development technology adopted from those including
development support tool, and package.
2.3.4 Development Purpose/Policy/Method/Technology 2-15
Well look at each item in Project Information as above.
It is all right if you attach the reference to describe the detail in a case that there is not enough
space in the form. Describe the key point in the form in that case.
2-15
2.3.5 Development Schedule(1/2)
(C) Development Schedule
2004 2005
Time remarks
10 11 12 1 2 3 4 5 6 7 8 9
Requirement External
Programming
1) Definition Design
Internal
Design
Testing Shipment/ Inspection
Plan Delivery
Review Review
Service Start
Schedule
Actual
2) Tender Selection Contract

Hardware Notice Construction
Procurement for delivery
3)
External Internal Test Shipment
Releted XXX Manufacturing Delivery
Design Design
Schedule System testing
External Interface Specification Message Service Start
Specification Check
Check
(Legend) : Plan
: Actual
2.3.5 Development Schedule 2-16
Now the Development Schedule. This sheet shows the chart with a filled-in form. The
development schedule and other related schedule are entered.
Description items are :

1) Development plan schedule,
2) Hardware procurement plan, and
3) Related systems development schedule.
2-16
2.3.5 Development Schedule(2/2)
(C) Development Schedule
1) Development Plan Schedule :

Fill in the planned period of process, validation plan for review, inspection plan and planned
dates for decision-making meetings.
2) Hardware Procurement Plan :

Fill in Selection Date for Development Environment Equipment and Commercial
Environment Equipment, Date to Contract, Date to Deliver, Construction Planned Date.
3) Development Plan Schedule for Related System :

Define the development process plan of the related system which provides the interface in
this development in addition to the work items with the related system and implementation
date.
Work Plan Procurement
2.3.5 Development Schedule 2-17
Here is Development Schedule to look at.
For Related System, if you have multiple systems, add the lines to describe and specify adjustment
period of external interface specification, set-up date, adjustment period of message specification,
set-up date, adjustment period of opposing test items, set-up date.
2-17
2.3.6 Development Size(1/3)
(D) Development Size
1) Development Development
Current Size Total size
Estimation method Plan/Actual Size Size
(KS) (KS)
(KS) (FP)
XXX function Plan
Actual
Business YYY function Plan 2) 5)
Actual
ZZZ function Plan
Actual
Total Plan
Actual
Insourcing Plan
Sourcing Actual
3)
Outsourcing Plan
Actual
Program Java Plan
language Actual
4)
Plan
Actual
2.3.6 Development Size 2-18
Lets go over Development Size. The chart shows you how to fill-in. You mainly define
development size and breakdown of the current size.
Description items include :

1) Size estimate method,
2) Operation/function-based development size,
3) Internal/external contract-based development size,
4) Language-based development size, and
5) Operation/function-based current size.
2-18
How to cover development size, current size, and total size.
Matrix size
Revision New body

size size
Development Size = New body Size + Revision Size

Current Size = Matrix Size - Revision Size
Total Size = Development Size + Current Size
= Matrix Size + New body Size
We will deal with form Development Size here and how to cover development size, current size,
and total size.
In the Development Size, add new body size and revision size.
In the Current size, deduct Matrix size from the Revision size this time.
Total Size should be the addition of Development size and Current size, equal to Matrix size and
New body size.
For example, if the Matrix size is 10KS, the Revision size 3KS in 10KS and New body size 2KS,
then the Development size = 2KS + 3KS=5KS, Current size=10KS-3KS = 7KS, and Total size=
5KS + 7KS or 10KS+2KS=12KS.
2-19
1) Size Estimate Method

Use the estimate method for size estimate including LOC method,
Function Point method
2) Operation/function-based development size

Define the development size breakdown with KS unit by operation or function.
3) Internal/external-based development size

Define the development size breakdown with KS unit by internal personnel or external
subcontract.
4) Language-based development Size

Define the development size breakdown with KS unit by development language used in
the Programming stage.
5) Operation/function-based current size

Define the current size breakdown with KS unit by operation or function.
Here are the Development Size and its description items.
LOC stands for Lines of Code. LOC method is a traditional estimate method to count lines of the
program itself. FP method is to count software functions as a scale of software size.
2-20
2.3.7 Development Effort(1/3)
(E) Development Effort
(unit : Man-month)
Stage P ST Total
Insourcing 1) office hour 10.00 15.00 20.00 20.00 10.00 75.00

overtime 2.00 2.00 2.00 1.00 7.00
Outsourcing 2) Consignment 20.00 5.00 50.00 20.00 2.00 97.00
Plan Subcontract 20.00 20.00 20.00 20.00 20.00 100.00
3) System Config Effort 10.00 10.00 20.00
4) Project management 6.00 5.20 9.20 6.20 3.30 29.90
total 66.0 57.2 101.2 68.2 36.3 328.9
5) Ratio 20% 17% 31% 21% 11% 100%
Stage P ST Total
Insourcing
office hour
overtime
Consignment
Outsourcing
Actual Subcontract
System Config Effort
Project management
total
Ratio
Project Plan(Detail) Creation Effort

Plan 1.00
Actual
2.3.7 Development Effort 2-21
Lets move onto form Development Effort.
Description form is shown in the chart and this sheet describes the estimate effort breakdown by
stage.
You will fill in the items including :

1) Insourcing effort,
2) Outsourcing effort (consignment),
3) Outsourcing effort (subcontract),
4) Project management effort,
5) Project planning effort.
2-21
3 persons x 1 month
What is man-month? = 3 man-month.
1st month
Man-month: Unit of Manpower
How to calculate ?
Effort = (Number of Personnel) x (duration)
Effort = Developing Size / Productivity
1 person x 3 months = 3 man-month.
1st month 2nd month 3rd month
Man-month, or person-month, is a unit to represent manpower (labor force). Man-month can be

obtained by multiplying the number of required personnel (=man, or person) by months. Therefore,
both of two cases above show the same amount of man-month. (3-man-month).
2-22
(E) Development Effort
1) Insourcing effort (internal effort)
Estimate the effort by internal personnel in each stage
and write in man-month unit.
2) Outsourcing effort (consignment)

Estimate the effort under the consignment contract by the external company in each
stage and write in man-month unit.
3) Outsourcing effort (subcontract)

Estimate the effort under the subcontract contract by the external company in each
stage and write in man-month unit.
4) Project management effort

Estimate the effort for project management including subcontract management
and write in man-month unit.
5) Project planning effort

Estimate the effort for project planning and write in man-month unit separately
from 1), 2), and 3).
Lets look at each description item Development Effort.
Following the completion of this form, you need to check the applicable balance among the stages
and internal/external rate in the end.
2-23
2.3.8 Development Cost
(F) Development Cost PJCD
Product Total PJCD
Plan ($) Actual($) difference
Contract Contract contract
System instruction System instruction System instruction
Category Breacdown
S/W H/W S/W H/W S/W H/W
Software Development Software Development Software Development
S/W Dev. S/W Dev S/W Dev
Effort cost (inhouse) 21.00 19.00 2.00
outsoure cost 38.00 37.00 1.00
S/W Dev. Cons. Cost 30.00 30.00
SE Cons. Cost 6.00 5.00 1.00
Other Cons. Cost 2.00 2.00
direct cost
Rental fee 14.00 12.00 2.00

production cost
Purchase Cost 7.00 0 7.00

1) Hardware 5.00 5.00
Software(License),etc 2.00 2.00
building cost 1.10 1.00 0.10
Equipment cost for testing 0.50 0.50
Other cost 0.90 0.80 0.10
total of direct cost 82.50 70.30 12.20
2) Indirect Cost 1.10 1.00 0.10
total of production cost 81.50 71.30 10.20
Sales & General Cost 9.00 8.00 1.00
3)
total of devekpoment cost 90.50 79.30 11.20
4)
Order(contract)volume 97.00 82.00 15.00
5) Defect cost 4.00 4.00
Reference
Val.Equip.Inv. 0
Equip. Inv.
H/W
Dev. Equip. Inv. 30.00 30.00
S/W S/W Inv. 0
6) Office E Power Equip. Inv. 2.00 2.00
2.3.8 Development Cost 2-24
We will cover Development cost next.
Description form is shown in the chart, you will fill in the breakdown of each estimate cost item.

1) Production cost (Direct cost),
2) Production cost(Indirect cost),
3) Sales and general management cost,
4) Order volume(Contract total),
5) Defect cost,
6) Equipment investment cost.
The form separates the software development from the equipment construction and the
breakdown for each should be written in.
2-24
Development cost - Subcontract Cost
(F) Development Cost
<Note on Subcontract Cost>

Subcontract cost is divided into Software development consignment cost, SE(*)
consignment cost, and Other consignment cost. Outline follows.
(*) SE: System Engineer
Operational Defect
Subcontract Cost Contract Type Contract Summary
responsibility Responsibility
S/W Dev. Contract to complete Responsibility

Subcontract Yes
Cons. cost work to Finish
Operation
SE Cons. Consignment Contract to process No (report
Execution
cost Contract certain office work obligation)
Responsibility
Other Usually
(Outside the Operation
Consignment above)
(Depends on consignment ) Execution Usually none
Cost Responsibility
Before we go into description of each item of development cost, I will outline the subcontract cost.
The subcontract cost is divided into Software development consignment cost, SE consignment
cost, and Other consignment cost. Each contract types, outline, operational responsibility, and
defect responsibility are explained in the chart.
2-25
Development Cost - Production Cost(1/2)
1) Production Cost (Direct Cost)

The direct cost of production cost is divided into the following items and the plan by dollar unit
should be written.
Effort Cost (in-house)
Payroll to supply to employees under direct management
Outsource Cost (Software Development Consignment Cost)
Cost necessary to commission software development( Software Development
Consignment ) to a subcontractor
Outsource Cost (SE Consignment Cost)
Cost necessary to commission software development(SE consignment) to a subcontractor
Outsource Cost (Other Consignment Cost)
Cost necessary (consultation commission cost etc.,) to commission other operations except
for software development consignment cost and SE consignment cost to a subcontractor.
Rental Fee
Cost for leased equipment in relation to software development and equipment construction.
Here is the Form Development Cost and its description items.
The direct cost of production cost is divided into these items and the plan by dollar unit should be
written.
Rental Fee is the cost for leased equipment in relation to software development and equipment
construction. It includes the rent for an office, warehouse, parking lot, computer, word processor,
copy machine, telephone, and fax machine.
2-26
Development Cost - Production Cost(2/2)
1) Production Cost (Direct Cost) (Continued)

Purchase Cost (Hardware)
Purchase cost necessary for development environment and commercial environment
Purchase Cost (Software (License Fee) ,etc.,)
The fee to use a patent of the logo or manufacturing technology proprietary to other firms
Building Cost
Rental fee for the land and building to use as work space
Equipment cost for testing
Rental fee to use validation equipments calculated from the building cost and depreciation allowance
Other cost
Other cost besides the above. It includes transportation expense, communication and delivery
expense, repair cost, incidentals, depreciation allowance, and training expense.
(Continued from previous page)
2-27
Development Cost - Others
2) Production cost(indirect cost)
Cost difficult to directly allocate on the particular development cost due to common cost
among multiple system developments.
3) Sales and general management cost

Cost necessary for sales activity and general administrative work
4) Order Volume(Contract Volume)

The amount contracted with the customer by receiving an order
5) Defect Cost
Cost for the possible defect(bug) of a system to fix in case the defect takes place following
the delivery(service start)
6) Equipment Investment Volume

The estimate amount of investment to hardware(validation equipment,
development equipment), software, and office(electric power equipment)
These are the description for the development cost.
In terms of these description items, it is all right if the reference is attached for the detail if there is
any estimate material elaborating the each cost item.
2-28
2.3.9 Organization Chart(1/2)
(G) Organization Chart
Enterprise Enterprise Enterprise

1) General Manager, Leader Member
System XX XX XXXX Enterprise
Member
XX XX
Project Manager Operation Leader Operation Member
2) Dev. Dept. Dev. Dept. Dev. Dept
XXXX XXXX XXXX
Dev. Dept
XXXX
System Leader System Member
Dev. Dept Dev. Dept
XXXX XXXXXX
PJ Management Quality Mgmt Specification Mgmt

Dev. Dept Dev. Dept Dev. Dept
XXXX XXXXX XXXX
Progress Mgmt Subcontract Mgmt

Dev. Dept Dev. Dept
Environment XXXX XXXX
Construction
Equipment Dept.
XXXXX
2.3.9 Organization Chart 2-29
This is one of the example of Organization Chart .
In this sheet, we describe all the organizations involved in the development including the client
section.
The major items in each box are :

1) Customer System , and
2) Development System.
2-29
2.3.9 Organization Chart(2/2)
(G) Organization Chart
1) Customer System
Clarify the customers organization including a contact with development side
and key person(last decision maker) with specific division, position, and name.
2) Development System
Clarify the development project side with Project Manager atop the list in
addition to clear group configuration specifying division, position, and name.
2.3.9 Organization Chart 2-30
Here are the description of Organization Chart.
2-30
2.3.10 Software Subcontract(1/2)
(H) Software Subcontract
1) 2) 3) 4) 5) 6) 7)
Contract Contract Period Cost Effort Size(KS) Cost efficiency
Stage Plan Actual
Contract
Contractor Start Plan Actual Plan Actual
Type Start date Start date Plan Actual Plan Actual
Stage
End Stage End date End date Size1 Size2 Size1 Size2 Cost1 Cost2 Cost1 Cost2
Information System ED 2004.04.01
Co. Ltd.,
Consignment 6.00 7.50
ST 2005.02.20
System Dev. Co. P/MT 2004.09.01
Subcontract 30.00 26.00 16.00
Ltd., ST 2005.02.20
consignment 6.00 7.50

subcontract 30.00 26.00
2.3.10 Software Subcontract 2-31
Lets look at Software Subcontract.
This sheet deals with various information regarding subcontract.

Major items are :
1) Contractor,
2) Contract Type,
3) Contract stage,
4) Contract Period,
5) Cost,
6) Effort, and
7) Size.
2-31
2.3.10 Software Subcontract(2/2)
(H) Software Subcontract
1) Contractor
Write the formal enterprise name to close a subcontract.
2) Contract Type
Write the contract type such as consignment or subcontract.
3) Contract Stage
Write the start stage and end stage to contract.
4) Contract Period
Write the start date and end date to contract.
5) Cost
Write the cost necessary to commission software development to contractor.
6) Effort
Write the effort necessary to commission software development to contractor.
7) Size
Write the size necessary to commission software development to contractor with KS unit.
2.3.10 Software Subcontract 2-32
Here are Software Subcontract description.
If the contract type is SE consignment and unable to specify the target size(in a case confining the
contract target by function or stage), it is not applicable.
2-32
2.3.11 Quality Target Value
(I) Quality Target Value
Quality
6)
Plan Actual
Target
1) 2) 3) 5) 7)
Value
No. of Errors
Review Effort/ 4)
Review
No. of
comment
Comment
No. of pages
of document
No. of pages Men for
No. of
Error Density Review Hours Density Density of document Review Review Comment
(Lower cases subject to No. of Errors Error Density comment
(Lower (Lower (Lower (Lower subject to *Review Density Density
Upper) (Lower review (Lower cases
Upper) Upper) Upper) Upper) review Hours
Upper) Upper)
(man- (man-
(cases) (cases/page) (man-hour) (cases) (cases/page) (page) (page) (cases) (cases/page) (man-hour) (cases) (cases/page)
hour/page) hour/page)
Stage
0.800 0.050 1.00
ED - - -
3.000 0.500 4.00
0.500 0.050 0.50
ID - - -
2.000 0.500 2.00
Quality
12)
Plan Actual
Target
Value
8) 9) 10) 11)
Bug Extraction
Test Density Bug Density
No. of Test Items No. of Programming Bugs Rate Bug Extraction
(Lower (Lower No. of Test Items Test Density No. of Programming Bugs Bug Density
(LowerUpper) (LowerUpper) (Lower Rate
Upper) Upper)
Upper)
Stage (items) (items/KS) (cases) (cases/KS) (items) (items/KS) (cases) (cases/KS)

15000 50.0 900 3.000 80.0%
IT - - - - -
27000 90.0 1500 5.000 95.0%
3000 10.0 90 0.300 95.0%
ST - - - - -
5400 18.0 150 0.600 100.0%
Plan
No. of Estimated Bugs 300 13)
2.3.11 Quality Target Value 2-33
Look at Quality Target Value.
Description form is shown in the chart and write Quality Target Value in each stage regarding
design/manufacturing in this sheet.
The major description items are :
1) number of errors,
2) error density,
3) review effort/review hour,
4) review density,
5) number of comments,
6) comment density,
7) number of documents for review,
8) number of test items,
9) test density,
10) number of bugs,
11) bug density by stage,
12) bug extraction rate, and
13) number of programming bugs.
2-33
Concept of Highest Value and Lowest Value
allowance scope after multiplying the standard
How to set the highest value with the constant( x%)
through the lowest low high
Standard value (A)

lowest highest
A x (100%-x%) A x (100%+x%)
Set up the allowance scope after multiplying the standard value with the constant(ratio).
Example :
(1)In a case with Error density : Standard value =0.20(case/page)
Constant = 30% highest value=0.26 lowest value=0.14
(2)In a case with Review density: Standard value=0.25(man-hour/page)

Constant= 20% highest value=0.3 lowest value=0.2
All the values to write in the form is the highest through the lowest.
How to measure the highest and lowest is to set up the allowance scope after multiplying the
standard value with the constant(ratio). The standard value is set up in consideration with the past
proprietary project data and production management data from the quality assurance department.
The diagram here is calculated with the constant reference value with -30% - +30% and -20% -
+20%.
2-34
Quality Target Values(1/2)
1) Number of errors
Number of Errors of document detected during document review
2) Error density
Error density = Number of errors / Number of document sheets for review
3) Review effort or Review Hours

Effort or hours spent for reviewing document
4) Review density
Review density = Review effort or Review hours/ Number of document sheets for review
5) Number of comment cases

Number of comments, questions, requests recorded during document review
6) Comment density
Comment density = Number of Comments / Number of document sheets for review
7) Number of pages of document subject to review

Number of pages of design documents to create, change, and reuse in the applicable
development
Here is the description of Quality Target Value.
2-35
Quality Target Values(2/2)
8) Number of test items
Number of test items to check by executing program or on the desk
whether the program satisfies requirement items or not
9) Test density
Test density = Number of test items / Development size
10) Number of Programming bugs

Number of Program errors (bugs) detected during test stage in applicable development
11) Bug density

Bug density = Number of bugs detected in each test stage / Development size
12) Bug extraction rate

Bug extraction rate = Number of bugs (*) / Number of estimated bug
(*) Accumulated number of bugs until applicable stage
13)Number of estimated bugs

Number of bugs estimated in consideration of applicable program/project features
by referring to past similar project achievement
(Continued from previous page)
2-36
2.3.12 System Configuration(1/2)
(J) System Configuration
Web Server AP Server
Building
Building
Client Client
1) 2) 3)
Equipment name Hardware conditions Software configuration
AP server CPU:Intel PenIV 120GHz OS: Windows 2000 Advanced Server
Memory:1000GB DBMS : Oracle9i Database Release
HDD:SCSI36GB RAID1 10(200.2.0)
Web server CPU:Intel PenIV 120GHz OS: Windows 3000 Advanced Server
Memory:1000GB DBMS : Oracle9i Database Release
HDD:SCSI 36GB RAID1 10(200.2.0)
Client CPU : corresponding to XX OS:Windows2000
Memory : 500GB
2.3.12 System Configuration 2-37
Lets look at System Configuration.
How to fill in the form is shown in the chart; in this sheet, you are going to describe the each
configuration of hardware, software, network, the development environment.

1) Equipment configuration,
2) Hardware condition, and
3) Software configuration.
As for 2) and 3), you can fill in the table as shown here.
2-37
2.3.12 System Configuration(2/2)
(J) System Configuration
1) Equipment configuration
Indicate the equipment including the network configuration and located position to use
in the development environment with the diagram.
2) Hardware conditions
Describe the necessary conditions(specification etc.,) for the hardware to use for the
server and client.
3) Software configuration
Describe the type and version for the software to use for the server and client.
2.3.12 System Configuration 2-38
Here is how to describe the System Configuration From.
2-38
2.3.13 Delivery/Handover(1/3)
(K) Delivery/Handover
1) 2) 3) 4) 5) 6) 7)
time to
Delivery/Handover Deliver to type media No. other
deliver
2.3.13 Delivery/Handover 2-39
Now, Delivery/Handover form.
How to describe is shown in the table.

In this sheet, you will write in the contents of delivery to the customer and handover to the
operation department and so on.

1) name of delivery/handover,
2) where to deliver/handover,
3) when to deliver/handover,
4) type,
5) media,
6)volume,and
7)other.
2-39
1) Name of delivery/handover
Refer to contract or agreement besides contract and specify all delivery to customer. Also clarify handover
to operational department.
2) Where to deliver/handover
Specify customer organization and enterprise to deliver and organization and enterprise to hand over.
3) When to deliver/handover
Write scheduled delivery/handover date.
4) Type
Write type of format corresponding to outputting media.
5) Media
Write media to output.
6) Number of Volume
Write number of outputting copy(one, original and a copy, etc.,)
7) Other
Distinguish between delivery and handover
This is how to describe Delivery/Handover .
2-40
Format Media
LM/OM/SM MT, CD-ROM, USB memory
Text, MS-Word, MS-Excel MO, FD
None, a set Paper
Regarding format and media, combination is described above.
2-41
2.3.14 Related Departments
(M) Related Departments
XX System Project
Purchase
Subcontract Dept.
Project
Manager Purchase inspection
Quality
Assurance
Product acceptance
inspection Dept.
Leader Cost
(Progress/ Product shipment
management inspection
Quality) Business
Promotion,
Progress meeting(weekly) Quality assurance
XX Dept.
activity
Overview
Specification (Process/product audit)
(Project
management Sales Dept.
planning)
Customer contract
Work instruction
Specification adjustment
Work status, results report
A Affiliate B Affiliate
company Company
2.3.14 Related Departments 2-42
Here is the next sheet, Related departments.
There is no certain format and this sheet handles related departments besides the project and their
roles as well as interface(including communication method) shown in diagrams or tables.
This diagram is one example indicating the relationship with the Purchase Department in
subcontract and purchase inspection.
2-42
2.3.15 WBS Definition(1/2)
(M) WBS Definition
1) 2)
Category WBS name other Category WBS name other
Decide the safety and reliability
ED03 ED15 Data Conceptual Design
policy
ED04 Decide the securityPolicy ED16 Data Security Design
ED05 Decide the Operation Policy ED17 Data Deployment Design

System
Data
Configuration
Construct and Maintenance for

ED01 Confirm stage plan ED21
Development Environment
Decide the system requirement
ED02
specification
Function Design for Business
ED11
Business Application
Environment
Application
2.3.15 WBS Definition 2-43
Here is WBS Definition.
This sheet defines the work items of WBS in a stage by each category.
Description items are

1) category, and
2) WBS name.
2-43
2.3.15 WBS Definition(2/2)
(M) WBS Definition
1) Category
This is the operational categorization to carry out WBS in consideration of execution
groups to develop. The category and stage correspondence table is shown below.
Strategy Requirement External Internal Integration System

Stage Programming
Planning Definition Design Design Test Test
Category
System
Configuration v v v v v v v
Business
v v v v v v v
Application
Data
v v v v
Environment v v v v v v v
2) WBS Name
Definition of work unit comprising a stage, describing based on application development.
2.3.15 WBS Definition 2-44
Now, well move onto WBS definition description items.
1) Category :This is the operational categorization to carry out WBS in consideration of execution
groups to develop. The category and stage correspondence table is shown below.
2) WBS Name : Definition of work unit comprising a stage, describing based on application
development.
2-44
2.3.16 Verification/Inspection Plan(1/2)
(N) Verification/Inspection Plan
1) 2) 3) 4) 5)
Verification/Inspection type Procedure Person in charge Pass/Fail judge Pass/Fail standard
Dev, Mangement Common
ED review Based on ED stage plan
Procedure
ID review Based on ID stage plan
Verification
Procedure
Programming review Based on Programming stage plan
Procedure
Integration test Based on test plan
Procedure
System test Based on test plan
Procedure
S/W Inspcetion Common Based on S/W Inspcetion
Judgement to start service
Procedure Common Procedure
S/W Inspcetion Common Based on S/W Inspcetion
S/W acceptance inspection
Procedure Common Procedure
Inspection plan
Purchase Inspection Based on Purchase Inspcetion

Purchase inspection
Common Procedure Common Procedure
Copy inspection Based on XX Procedure
Procedure
Installation inspection Based on XX Procedure
Procedure
2.3.16 Verification/Inspection Plan 2-45
Here we see Verification/Inspection Plan.
This sheet defines the types and plan contents of verification/inspection plan.
1) verification/inspection type,
2) procedure,
3) person in charge of implementation,
4) judge to pass/failure, and
5) Pass/failure standard.
2-45
2.3.16 Verification/Inspection Plan(2/2)
(N) Verification/Inspection Plan
1) Verification/inspection differentiation
Specify all verification names(review and test) as well as inspection
names to be planned in verification/inspection plan.
2) Procedure
Describe procedure to use in Project. In a case individual procedure to use exists, add
one, too.
3) Person in charge of implementation

Write Person in charge of implementing verification/inspection. In case no individual is
identified, the qualification name such as chief inspector or position will do.
4) Judge to pass/failure
Write Person in charge of judging pass/failure. In case no individual is identified, the
position such as Qualification Assurance General Manger or qualification name will do.
5) Pass/failure standard
Specify document name defining pass/failure standard in verification/inspection.
2.3.16 Verification/Inspection Plan 2-46
Now Verification/Inspection Plan. Is described like above.
2-46
2.3.17 Development Risk(1/2)
(O) Development Risk
1) 2) 3)
In case that project plan create In case project finish
Other
Risk items Coutermeasures Risk assesment
No PJ member familiar with development Find in-house personnel who used Handling objective date: August 5,
support tool to use as customer the tool before and ask the to 2004 Person in charge: XX
instructed. involve in PJ Manger, Personnel Dept.
2.3.17 Development Risk 2-47
Now Development risk.
This sheet defines the contents and countermeasures of conceivable risk in project planning.
1) risk items,
2) countermeasures, and
3) other.
2-47
2.3.17 Development Risk(2/2)
(O) Development risk
1) Risk items
List up the factors and events which may affect project operation(which may hinder
objective fulfillment) as risks and specify their contents.
Dev. Risk Customer requirement risk

Technological risk
Project operation risk
2) Countermeasures
Select countermeasures depending on risk size and evaluation against risk picked up in
1) and write down.
Countermeasure Prevention Risk Avoidance

Risk reduction measures
Measures Risk
following acceptance
occurrence measures
3) Other
Specify attachment items including handling objective date, and person in charge as
for 2)measures.
2.3.17 Development Risk 2-48
Form Development Risk is covered here.
1) Risk items :
Development Risk includes Customer requirement risk as the uncertainty and possible change
of customer requirement items, Technological risk as possible lack of technological reliability in
method, tool, environment, embedded product, and related system, and Project operation risk as
the possible defect in system, management method, resource, communication, subcontract in project
operation.
2) Countermeasures :
Prevention to prevent risk factors from occurring, Measures following occurrence to minimize
the effect in case of risk occurrence. There are two types of Prevention; one is Risk avoidance
to avoid risk occurrence by removing the risk factors, and the other Risk reduction to slush risk
size. In Measures following occurrence, there is Risk acceptance to prepare the
countermeasures in advance in case of risk occurrence.
3)Other:
Specify attachment items including handling objective date, and person in charge as for
2)measures.
These are the explanation on how to form project plan.
2-48
3. Project Planning Overview(1/3)
Purpose and Purpose and effect of Project Planning
Purpose of Project Planning
Purpose 3: Setting up Baseline to Control Project
The final purpose:
Steer the project to execution and make the project succeed.
Effect of Project Planning

Effect 1:Participation in the plan by project members increases the motivation
of objective achievement.
Effect 2:The agreed plan becomes the common understanding among

stakeholders and establishes objectivity and persuasiveness.
Effect 3:The weak point of the project can be found from the whole plan
with individual parts accumulated.
3. Project Planning Overview 3-1
Lets wrap up project planning.
First, I would like to discuss Purpose and Effect of Project Planning. There are five
purposes.
1) Form guideline to perform project.
2) Clarifying the scope of the project.
3) Setting up the baseline to control project
4) Defining conditions of project
5) Contact and Communication among stakeholders
The final purpose is Steer the project to execution and make the project succeed.
There are three effects of Project Planning.
1) Participation in the plan by project members increases the motivation of objective

achievement.
2) The agreed plan becomes the common understanding among stakeholders and establishes
objectivity and persuasiveness.
3) The weak point of the project can be found from the whole plan with individual parts
accumulated.
3-1
Initiating Project
Officially approve applicable project or next phase of project as project

execution organization.
Project manager is chosen and appointed
Project charter is issued
Next, well go over Initiating Project. Initiating Project means to officially approve
applicable project or next phase of the project as project execution organization.
At Initiating Project, choose and appoint Project Manager to issue the project charter as a
result.
3-2
Project Plan Configuration
9 Processes in Planning Processes
Forms to comprise Project Plan

Front Page
H) Software Subcontract
B) Development Purpose/Policy
/Method/Technology
C) Development Schedule
L) Related Departments
D) Development Size
M) WBS Definition
E) Development Effort
N) Verification Plan/Inspection Plan
F) Development Cost
O) Development Risk
To Project Executing Processes

In the end, let me check with the forms comprising the project plan.
There are 15 types in the project plan including :

A) Project Information,
B) Development Purpose/Policy/Method/Technology,
C) Development Schedule,
D) Development Size,
E) Development Effort,
F) Development Cost,
G) Organization Chart,
H) Software Subcontract,
I) Quality Target Value,
K) Delivery/Handover,
L) Related Departments,
M) WBS Definition,
N) Verification/Inspection Plan, and
O) Development Risk.
These forms are for consistent documentation without any contradiction using Project
Planning result and passed onto Project Executing. Project Planning is repeatedly carried out
through the project execution and the project plan is updated each time.
3-3

10 PM-Plan PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

10 PM-Plan PDF

Hochgeladen von

Copyright:

Verfügbare Formate

CNP01L07A

Project Management Planning

OKINAWA INTERNATIONAL CENTRE

Project Management Planning .......................................................................... 1

Chapter 1 Project Planning Outline ............................................................ 1-1

1.1 Purpose of Project Planning 1-2

1.2 Effect of Project Planning 1-10

1.3 Project Plan Outline 1-14

Chapter 2 Project Planning............................................................................. 2-1

2.1 Project Initiating 2-2

2.2 Project Charter Creation 2-4

2.3 Project Plan Creation 2-6

Chapter 3 Project Planning Overview............................................................ 3-1

Copyright 2007 NIPPON TELEGRAPH AND TELEPHONE EAST CORPORATION

Project Management Planning 1

Upon completion of this class, you are expected to :

1. Understand elements and procedures for project planning.

2. Understand about project planning that considers the characteristics of a

3. Explain how to apply project planning method in the exercise.

Project Management Planning 2

Chapter 1. Project Planning Outline

Chapter 2. Project Planning

Chapter 3. Project Planning Overview

Project Management Planning 3

1.1 Purpose of Project Planning

1.2 Effect of Project Planning

1.3 Project Plan Outline

1. Project Planning Outline 1-1

1.1 Purpose of Project Planning

1.2 Effect of Project Planning

1.3 Project Plan Outline

Project (small) Holding Graduation Ceremony Committee

Project (medium) Dam Construction Project

Project (large) NASA Space Station Development Project

All projects require Planning and it is the key to success

1.1 Purpose of Project Planning 1-2

Purpose 1: Forming Guideline to Perform Project

The final purpose:

1.1 Purpose of Project Planning 1-3

There are five purposes for project planning.

Purpose 1: Forming Guideline to Perform Project

Each project has its objective(theme), project policy.

Assigning highest priority in the development

-Medical system development which saves human life

Assigning highest priority in the highest-level

1.1 Purpose of Project Planning 1-4

The first purpose of project planning is Forming guideline to perform a project.

Aichi Exposition Preparation Project

Human Genome Analysis Project

1.1 Purpose of Project Planning 1-5

Lets consider what is project planning.

1) Wind power generation project in Mohave Desert

2) Aichi Exposition Preparation Project

3) Human genome analysis project

1.1 Purpose of Project Planning 1-6

The second purpose of project planning is Clarifying the Scope of Project.

It is necessary to define the project scope. Mainly,

Ex. Effort (plan vs. actual)

1.1 Purpose of Project Planning 1-7

The third purpose is Setting up Baseline to Control Project.

Prerequisite, limited condition, hypothetical condition found during

Prerequisite, limited condition, hypothetical condition should be clearly stated.

1.1 Purpose of Project Planning 1-8