PMCenter Project Fall 2003 EOSP

1
PMCenter ProjectFall 2003EOSP
2
Agenda

• Introduction
• Project Background
• Processes
• Difficulties
• Lessons Learned
• Next Step

3
Team Introduction

• GEO (Green Elephants from the Orient)
• Team members
• SoYoung Kim
• JungHee Jo
• JunSuk Oh
• KwangChun Lee
• Younbok Lee
• Mentors
• Gil Taran
• HoJin Choi

4
Project Background

• Customer
• OSSL(Operations Support System Lab.) in KT (Korea
  Telecom)
• Problem
• Support tool for project management through the
  whole life cycle
• Improve software development process
• CMMI model as a reference
• Proposed Solution
• PMCenter software project management system

5
System Overview
Administrator
Web Browser
Project Manager
PMCenter
Client Application
Project Member
Web Browser
6
Team Goals

• If you are not having fun, youre not doing it
  right
• Work smarter
• Be punctual
• Respect each other
• Do team building

7
Management Process

• Roles
• TSP Roles Responsibilities
• Meeting
• Three roles Facilitator, Time keeper, Scriber
• Take roles in turn
• Risk Management
• Configuration Management

8
Development Process

• Adopt RUP
• Most popular
• Adapt to change
• Well-defined artifact sets
• Roles and activities
• Customer recommendation
• This Semester Inception phase
• Launch the project
• Resolve system scope
• Resolve requirement ambiguities
• Establish a candidate architecture

?
?
?
?
9
Requirements
Elicitation
Analysis
Specification
V V

• Bench marking
• Study CMMI
• Interview with customer

• Scope
• Make feature List
• Prioritize

• SRS
• Use case Model

• Peer Review
• Customer Approval

10
Project Scope (initial)

• Initial Scope
• Customer requested
• 6 KPAs of CMMI Level 2
• Large and ambiguous scope
• Scoping process
• Studying KPAs in CMMI Level 2
• Customer prioritized the functionalities
• Proposing specified scope to customer

Requirements Management
Project Planning
Project Monitoring and Control
Measurement and Analysis
Configuration Management
Quality Assurance
11
Project Scope (Fixed)

• Fixed Scope
• What are the key functionalities for Project
  Management
• Finalized three KPAs of CMMI Level 2

Requirements Management

Project Planning
Project Monitoring and Control
Measurement and Analysis
Configuration Management
Quality Assurance
12
System Context (1/3) - Workflows
13
System Context (2/3) - Functionalities
Project Management
Registration
Resource/Cost
WBS
Task Assignment
Metric
Risk Management
Progress Mgt
Schedule
Add-on
MyPage
Document Management
System Admin
system functionalities
User Management
14
System Context (3/3)
Functionalities
Project Planning
Project Execution
Project Management
Registration
Break down works
Resource/Cost
Analyze the dependency among tasks
Organize the team
WBS
Task Assignment
Categorize tasks
Allocate resources
Metric
Risk Management
Plan project schedule
Progress Mgt
Plan cost
Schedule
Evaluate risk
Add-on
plan quality assurance
Assign tasks
MyPage
Approve project plan
Document Management
Development
System Admin
Register deliverables
User Management
activities in scope
system functionalities
activities out of scope
15
Risk Management
Recognition of Risks
Taxonomy-based risk identification Risk
management in SEI Software risk management
principles and practices
CRM (Continuous Risk Management)
16
Difficulties

• Scope management
• Process definition
• Role definition and balanced responsibilities
• Communication
• Among team members
• With Customers
• Long distance
• Change of Customer Lead
• Team Lead Turnover

17
Project Footprints
SRS SPMP
Feature List SOW
Requirement Scoping
Launching
Lead Turnover
Role Definition
18
Lessons Learned

• Harmony among team members
• Time is the most precious resource
• Customer expectation is always high
• Balancing workload

Learning By Doing Team Work
19
Next Steps for Spring 2004

• Developing Software Architecture
• Analysis and Design
• Prototyping User Interface
• Developing Test plan
• CRM (Continuous Risk Management)
• Transition to New Roles

20
QA