1
Project Management SystemBased on Work-Breakdown-Structure
Process Model
Satoshi Awane
2
Topics
1. Introduction
2. Summary of “Pro-Navi” and “PRO-NAVI WBS”
3. Project Management with “Pro-Navi”
4. Application example
5. Evaluation
3
1. Introduction
4
What is project management?
*What is Project?
• What is Project management?
Why a system to support project management is needed?
5
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”
6
2. Summary of “Pro-Navi” and “PRO-NAVI WBS”
7
“Pro-Navi” System Structure
8
“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)
9
“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. co.Jp /project/PJ0AP00012/
- WBS -
+ ビジネス開発+ システム開発- ソフトウエア開発 - 基本設計 開発方式設計 データ項目設計 データベース論理設計 ソフトウェア要件定義 + 詳細設計 - プログラム作成 設計プログラム プログラミング 単体テスト 組合せテスト + テスト + 検査- プロジェクト管理 + 工程管理 + 品質管理 + 仕様変更管理 + 懸案管理
XX生産管理次期ステム( PJ0AP00012 ) [ プロジェクト情報 ] [ 成果物 ]
関連規則 [ 項目編集 ] 関連情報 [ 項目編集 ]
作業・成果物一覧 [ 項目編集 ]
作業・成果物名称 作成日 担当者 期限
必要資料一覧 [ 項目編集 ]
資料名称 作成日 担当者 期限
関連規則 [ 項目編集 ]・SSS DD01 基本仕様書作成基準・SSS DC08 ソフトウェア開発におけるデザイ
関連情報 [ 項目編集 ]・HIPACE 情報システム開発計画・統合サーバ事例検索 [ 基本設計 ]・工程別ツール適用マップ
ソフトウェア開発 >> 基本設計 >> 【ソフトウェア要件定義】 作業・成果物一覧 [ 項目編集 ]
作業・成果物名称 作成日 担当者 期限 概要検討 佐藤 99/11/1 ・概要検討 メモ 99/11/1 14:00 高橋 99/11/1 基本仕様書 佐藤 99/12/10 基本仕様書レビュー 森沢 99/12/11 ・基本設計書レビュー報告書 大泉 99/12/11
ソフトウェア開発 >> システム計画 >> 【基本設計】 必要資料一覧 [ 項目編集 ]
資料名称 作成日 担当者 期限 開発計画書 99/9/30 22:10 東山 99/10/1
Required document
Outcomes of former processes
Reference materials from outside
Hitachi standards
WBS
10
PRO-NAVI WBS
11
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
12
3. Project Management with “Pro-Navi”
13
PROJECT MANAGEMENT CYCLE
• P-D-C-(A)
Plan
Action
Check
DoManagementSystem
14
Plan
* Apply standard WBS Choice of a prototype relevant
to business field
*Add and modify work items
*Work items and schedule
WBS generation
WBS customization
Approval and notification
15
PLANNING
• Generate WBS
Is a clarification ofProcess, works, outcomes.
• Embody Work step information
• Define management process of each work
:
16
Input Work Output
Outcomes of prior workCommon rulesExamples
Outcomes(document)
We had plentiful asset of standardization rules, development procedures, worksheets, check lists, know-howsSuch as reliability design, etc.
Embodiment of Work step information
17
Define management process of each work
WORKAssign memberSet due dates Storate and approval rules
Issues
BugsCheck and reporting method ofWorks progress status trace method of
Outbreak and extinction
OUTCOMES
18
“Pro-Navi” assisted Planning
PRO-NAVI WBSessence
Pro-Navi Systemtools
Input Work Output
Outcomes of prior workCommon rulesExamples
Outcomes(document)
WORKAssign memberSet due dates
Issues
BugsCheck and reporting method ofWorks progress status
OUTCOMES
19
“Do”
• Confirm one’s work
• Exectution=Outcome making
*Gather information
*Check procedure
• Outcome registration and update
Confirm “work”
Execute “work”
Store outcome andreport
20
Project View
PROGRESS STATUS
ASSIGNEDor
Registration DUE DATE
Prerequisite Works/ References materials ..
Product File(s)
Register
Check
Reference
Procedures
Outcomes
1
2
3
:deadline failure
21
“Check”
• Check one’s progress
• Comparison of schedule and actual status (Grasp fact)
• Direct check of outcome– Uniform management of outcomes
Work progress check
Comparison
Check outcomes
22
Grasp project status• Store ALL OUTCOMES AN
D WORK STATUS in PRO-NAVI data base.
Then display
on “Project View”
23
4. Application example
24
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
25
A railroad company ticket system
* EFFECT
26
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.
27
5. Evaluation
28
Actual application record
• 1200 projects are using “PRO-NAVI”
• 310,000 files registered– March, 2004.
29
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”.
30
Analysis and Considerations
*EFFECTSClarification and notification of project plan througho
ut 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 progr
ess status based on products
31
Thank you!