Vous êtes sur la page 1sur 8

TERADYNE Case Study

Prepared by:
Jasjeet Singh (2013D02)
Swaroop Das Chowdhury (2013D04)
Prashant Gupta (2013D14)
Subhashini N. (2013D17)

Discuss use of PM tools how to build capabilities to benefit subsequent


projects. Use exhibits1, 2, 3, 6, 7 and 9 to analyse and explain.
Integration
Develop Project
Charter
* Proposal
submitted May-02
Develop Project
Management Plan
* During Phase II

Scope
Collect
Requirements
Define Scope
Create WBS
Verify Scope

Schedule

Cost
Quality
Plan Cost
Define Activities
Management Plan QM
Estimate
Prepare
Sequence Activities
Costs
QA
Estimate Activity
Resources
Estimate Activity
Durations

*3-point
estimation
Determine
Budget

Direct and Manage


*3-point estimation
Project Work
Control Scope
Control Costs
Monitor and Control
* Earned
Project Work
Develop Schedule Value Analysis
Perform Integrated
*Critical Path
Change Control
Method
Close Project or
Phase
~Primavera used
Control Schedule
*Earned Value
Analysis

QC

Risk

HR

Communication

Plan Risk Mgt

Plan Human Resources Plan Communications


* who was needed + who
*Meetings
Identify Risks was available
* During Phase II
~core team to meet
weekly (telecon)
Perform
~core team to meet
Qualitative RA * Project Team Structure monthly (person)

Acquire Project Team

Perform
Quantitative RA
Plan Risk
Response
Monitor &
Control

~ set of project teams


-one per subsystem
~ core team :i) heads of all teams
ii) program manager
iii) head - O'Brien

Develop Project Team


*Continuous Upgrade
~ memory business exited

~ agenda - analyse
critical path

Manage
Communications
Control
Communications

Procurem
ent

Stakeholder
Identify Stakeholders
Plan Stakeholder
Management
Manage Stakeholder
Engagement
Control Stakeholder
Engagement

Engg

Profit Realized

20.0%
10.0%
0.0%
-10.0%
-20.0%
-30.0%
-40.0%
-50.0%
-60.0%
1992

1996

1998

2000

2002

2004

2006

Actual Staffing

2000

250

1500

Semiconductor Test System


Connection Systems
Assembly Test Systems
Other Test Systems
TOTAL

1000
500
0
2002

1994

2003

2004

200
150
Number of people

100
50
0

60
50
40
30
20
10
0

HW
System
Verification

SW
Admin

Value of the project management tools has to be taught to the project manager teams

Causes for behavioral issues


Changes due to aggregate project planning

Behavioral Biases

Solving the problems

Thank You!