Project Management System
Based on Work-Breakdown-Structure
Process Model
Satoshi Awane
1
Topics
1. Introduction
2. Summary of “Pro-Navi” and
“PRO-NAVI WBS”
3. Project Management with “Pro-Navi”
4. Application example
5. Evaluation
2
1. Introduction
3
What is project management?
*What is Project?
• What is Project management?
Why a system to support
project management is needed?
4
ISSUES of PROJECT
MANAGEMENT
*“Integrated management of process, work,
outcomes, and know-how”
Mutual mapping with “WBS process model”
-Clarify process/work/outcome at planning
-Grasp project progress status
-Standardize and navigate development process
-Share knowledge: outcomes, know-how, ..
We realized with “PRO-NAVI”
5
2. Summary of “Pro-Navi” and
“PRO-NAVI WBS”
6
“Pro-Navi” System Structure
7
“Pro-Navi” data structure
• Project information
• WBS
• Work related information
– Mutual dependency
– Common rules, etc.,
• Management information
of a WORK
– Due dates
– Assigned member
– Status
• Outcomes(documents)
8
“Pro-Navi” UI (User Interface)
Prnv Project WorkSpace(PJAP00012) –
□□□
File(F) Edit (E) View(V) Move(G) Booknmark(A) Help(H)
アドレス
https://dev01.sangyou.aaa.ｃｏ．Ｊｐ/project/PJ0AP00012/
ＸＸ生産管理次期ステム（PJ0AP00012）
-
WBS
WBS -
+ ビジネス開発
+ システム開発
- ソフトウエア開発
- 基本設計
開発方式設計
データ項目設計
データベース論理設計
ソフトウェア要件定義
+ 詳細設計
- プログラム作成
ﾌﾟﾛｸﾞﾗﾑ設計
ﾌﾟﾛｸﾞﾗﾐﾝｸﾞ
単体テスト
組合せテスト
+ テスト
+ 検査
- プロジェクト管理
+ 工程管理
+ 品質管理
+ 仕様変更管理
+ 懸案管理
[プロジェクト情報] [成果物]
ソフトウェア開発 >> 基本設計 >> 【ソフトウェア要件定義】
作業・成果物名称
概要検討
・概要検討 メモ
基本仕様書
基本仕様書レビュー
・基本設計書レビュー報告書
作成日
担当者
佐藤
99/11/1 14:00 高橋
佐藤
森沢
大泉
ソフトウェア開発 >> システム計画 >> 【基本設計】
資料名称
開発計画書
Required
document
[項目編集]
[項目編集]
期限
99/11/1
99/11/1
99/12/10
99/12/11
99/12/11
Outcomes of
former
必要資料一覧
必要資料一覧
[項目編集] [項目編集]
processes
作成日
担当者
99/9/30 22:10 東山
関連規則
[項目編集]
・SSS DD01 基本仕様書作成基準
・SSS DC08 ソフトウェア開発におけるデザイ
Hitachi
standards
作業・成果物一覧
作業・成果物一覧
期限
99/10/1
関連情報
[項目編集]
・HIPACE 情報システム開発計画
・統合サーバ事例検索 [基本設計]
・工程別ツール適用マップ
Reference
materials
from
outside
9
PRO-NAVI WBS
10
Characteristics of “PRO-NAVI WBS”
• Hold WBS structure as prototype Plus
– Mutual dependence of works
– Display necessary outside Information and Link
• Rules and work procedures, etc
• Relate WBS’s work with SLCP-JFC98*
activities and tasks
*A common frame for software centric development and trades
PLUS necessity level of works and leveling of standard’s
customization allowance
11
3. Project Management with
“Pro-Navi”
12
PROJECT MANAGEMENT
CYCLE
• P-D-C-(A)
Plan
Action
Management
System
Do
Check
13
Plan
* Apply standard WBS
WBS generation
Choice of a prototype relevant
to business field
WBS customization
*Add and modify work items
Approval and
notification
*Work items and schedule
14
PLANNING
Is a clarification of
Process, works, outcomes.
• Generate WBS
• Embody Work step information
• Define management process of each work
：
15
Embodiment of Work step
information
Input
Outcomes of prior work
Common rules
Examples
Work
Output
Outcomes
(document)
We had plentiful asset of standardization rules,
development procedures, worksheets, check lists, know-hows
16
Such as reliability design, etc.
Define management process of
each work
Assign member
Set due dates
OUTCOMES
WORK
Storate and approval rules
Issues
Check and reporting
method of
Works progress status
Bugs
trace method of
Outbreak 17
and extinction
“Pro-Navi” assisted Planning
Input
Work
Outcomes of prior work
Common rules
Examples
Assign member
Set due dates
Output
essence
PRO-NAVI WBS
tools
Pro-Navi System
Outcomes
(document)
OUTCOMES
WORK
Issues
Check and reporting
method of
Works progress status
Bugs
18
“Do”
• Confirm one’s work
Confirm “work”
Execute “work”
Store outcome and
report
• Exectution=Outcome making
*Gather information
*Check procedure
• Outcome registration and
update
19
Project View
1
Check
PROGRESS
STATUS
3
Outcome
s
ASSIGNED
or
Registration
DUE DATE
Register
Product File(s)
Procedure
s
2
Reference
Prerequisite Works/ References materials ..
20
:deadline failure
“Check”
• Check one’s progress
Work progress check
Comparison
• Comparison of schedule and
actual status (Grasp fact)
• Direct check of outcome
Check outcomes
– Uniform management of
outcomes
21
Grasp project status
• Store ALL OUTCOMES AND
WORK STATUS in PRONAVI data base.
Then display
on “Project View”
22
4. Application example
23
A railroad company ticket system
• Profile– 800 Kilo source lines of code
– 200 project members in 10 separate
development locations.
• Why– To achieve high efficiency development and
management level
– To share project progress status, product files
and project common documents
24
A railroad company ticket system
* EFFECT
25
A railroad company ticket system
• Issue of the project management
– Product progress status gathering function
• example, to grasp project progress status, one needs
to select a work in “PRONAVI WBS display frame”
of the project view, and then check its progress work
by work in “product information display frame”.
This operation method has advantage in grasping
percentage of completion of products, however, it
costs effort to grasp project progress status, and
requires a new function to sum up product progress.
26
5. Evaluation
27
Actual application record
• 1200 projects are
using “PRO-NAVI”
• 310,000 files
registered
– March, 2004.
28
Evaluation from PRO-NAVI USERS
Evaluations from “PRO-NAVI” users :
(1) Getting across job of the project standard document and project
development plan to its project members has become easier.
(2) Development errors due to “version-mistakes” have disappeared,
because most recent products can be shared in a secured manner.
(3) Search job for necessary products has become much easier.
(4) Distribution job of products has become easier.
(5) Hard copy document distribution has decreased.
(6) Version management of products has become possible.
(7) A project manager can easily verify the project status report, because
the project manager can directly check the status of the product and its
contents with “PRO-NAVI”.
29
Analysis and Considerations
*EFFECTS
Clarification and notification of project plan throughout
the project.
– Correct grasp of project progress status.
– Higher quality, higher efficiency, standardization of the
project due to easy access to products and common
documents.
*NEXT STEP
– Easier project progress status gathering
– Eg., Automatic collection apparatus of project progress
status based on products
30
Thank you!
31