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
11MARCH04
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
Goal
0
Sell Ideas
Generate
many
ideas
1
Plan
Develop
Plan
2
Develop
Advance
idea to
product
3
Validate
4
Qualify
5
Produce
Proof of
specs
Proof of
build
Robust
process
Process Develop
Plan the
Engineer
work for Functional
the Team Models
Test
Proto
units
Build &
Test Pilot
units
Release
Product
to Sell
Main Initial
Artifact Project
Gantt
Chart
Solid
System
Proto
Working
Product
Quality
Product
Ideas into
Proposal
Summary
Owner Project
Core
Champion Team
11MARCH04
Working
Modules &
Prototypes
Present an idea
2.
3.
4.
11MARCH04
ProcessPhase Relationship
Project Phase 0 Phase 1
Ideas
Plan
Mgmt
Process
Steps
1
Develop
Ideas
2
3
4
11MARCH04
Phase 2 Phase 3
Develop Validate
Phase 4 Phase 5
Qualify Produce
Plan the
work
Work the Plan
Learn from positive and negative events
11MARCH04
STEP 1
Customer wants
Customer needs
Competitor products
Competitor plans
Marketing/sales logs
Organizational strategies
Society attitudes and opinions
Product Development Cycle and
Project Management Process
10
11
12
Goal
Product Roadmap
Key Selling Points
Key Customers
Proposed Team
Business Case
Recommendation to decision-makers
STEP 1
Quick
13
14
STEP 2
15
STEP 2
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?
STEP 2
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
11MARCH04
21
STEP 3
22
Report routinely
Report project progress using data
Communicate project status to all decisionmakers 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
Upcoming Activities
UACT 1
UACT 2
UACT n
Start Date
Completed Activities
CACT 1
CACT 2
CACT n
Completion Date
% Over Budget
_____
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
WEEKLY STATUS
REPORT
Owner
HILL
Status
RED
Due Date
15MAR
24
25
Cost of Changes
Cost
$1,000,000
1,000,000
900,000
800,000
700,000
600,000
$500,000
500,000
400,000
300,000
$250,000
200,000
100,000
0
$50,000
$5,000
$500
Phase 0 Phase 1 Phase 2 Phase 3 Phase 4 Phase 5
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
STEP 4
31
STEP 4
32
NMI Discipline
STEP 4
33
STEP 4
34
STEP 4
35
Conclusions
Process Phase 0 Phase 1
Ideas
Plan
Steps
1
Develop
Ideas
Phase 2 Phase 3
Develop Validate
11MARCH04
Phase 5
Produce
Plan the
work
3
4
Phase 4
Qualify
36