Professional Documents
Culture Documents
Asme Product Development Cycle
Asme Product Development Cycle
OVERVIEW
Explain the product development cycle
Define project management processes
Relate #1 and #2
Discuss the tasks behind each process
Suggest simple communication tools
Bob Carson
March 11, 2004
11MARCH04
Expected Outcomes
11MARCH04
Common Definitions
Product Development
Motivation
Engineers should learn about
todays development practices
An engineers skill set should
parallel industrys expectations
Efficient individuals develop
effective project management skills
11MARCH04
11MARCH04
Phase
Goal
Product Development
Phases
0
Sell
Ideas
1
Plan
2
Develop
3
Validat
e
4
Qualify
5
Produc
e
Proof
of
specs
Proof of
build
Robust
proces
s
Releas
e
Produc
t to
Sell
Proces Develop
Ideas
s
Plan the
work for
the
Team
Engineer
Functiona
l Models
Test
Proto
units
Build &
Test
Pilot
units
Main
Artifac
t
Gantt
Chart
Working
Modules
&
Prototype
s
Solid
System
Proto
Working Quality
Product Produc
t
into
Proposal
Initial
Project
Summar
y
11MARCH04
Owner Project
Product Development
6
Extended or Core Team Member
Core
Project Management
Process Steps
1.
2.
3.
4.
Present an idea
Plan the work
Work the plan
Learn from experiences
11MARCH04
ProcessPhase Relationship
Projec Phase 0 Phase 1
Ideas
Plan
t
Mgmt
Proces
s
Steps
1
2
Phase
Phase 3
2
Validate
Develo
p
Phase
4
Qualif
y
Phase
5
Produc
e
Develo
p Ideas
Plan
the
work
3
Work the Plan
4
Learn from positive and negative events
11MARCH04
Product Development
11MARCH04
STEP 1
10
STEP 1
11
STEP 1
12
Quick
Goal
Product Roadmap
Key Selling Points
Key Customers
Proposed Team
Business Case
Recommendation to decision-makers
STEP 1
13
14
STEP 2
15
CORE TEAM
Research
Quality
Hardware
Software
Mechanical
Manufacturing
Marketing/Sales
Finance
16
STEP 2
17
Link deliverables
Match deliverables to milestones by phase.
Plan for deliverables that are not tied to key
milestones. What are some examples of key
deliverables?
18
Define tradeoffs
Showstoppers need defined before
finalizing the plan
Establish tradeoffs to give the team clear
direction should known risks develop
This task avoids wasted time later in the
project. It shows the decision-makers a
teams due diligence to project success
STEP 2
19
20
21
STEP 3
22
Report routinely
Report project progress using data
Communicate project status to all
decision-makers and stakeholders with
Quality, Performance, Cost and
Schedule metrics
Suggest recommendations when
negative data identifies a need for
change. Never report a problem
without a recommended solution
STEP 3
23
Date: 11MAR04
GREEN
RED
Quality
Performance
Schedule
Cost
% Over Budget
_____
Upcoming Activities
UACT 1
UACT 2
UACT n
Start Date
Completed Activities
CACT 1
CACT 2
CACT n
Completion Date
Team Member
Due Date
Andersen
20MAR04
24MAR04
Green
Green
Zeller
15MAR04
10MAR04
Green
Issue
Summary
Action
Schedule
Comments:
Low risk item: Mfg Engr has high confidence that Production tests will still meet schedule
Owner
HILL
Status
RED
Due Date
15MAR
24
25
Cost of Changes
HYPOTHETICAL
26
Communicate change
Never surprise anyone
Over-communicate when change
happens
Ensure all decision-makers and
stakeholders agree with any new
tasks or plan changes
STEP 3
27
28
11MARCH04
29
STEP 4
30
Document events
31
32
NMI Discipline
33
34
35
Conclusions
Proces Phase 0 Phase 1
Ideas
Plan
s
Steps
1
Phase
3
Validat
e
Phase
Phase 5
4
Produce
Qualify
Develo
p Ideas
3
4
Phase
2
Develo
p
Plan
the
work
Work the Plan
Learn from positive and negative events
11MARCH04
Product Development
36