Supply Chain Design Executive Summary and Presentation

Riordan Lessons Learned Report Project Name CardiCare Valve Proof-of-Concept Release Draft/Final

Date: 6/5/04

Author:

Craig Mulligan

Owner:

Craig Mulligan

Client:

NA (internal project)

Document Number:

RD595

Document History Revision History

Date of next revision: NA

Revision Date

Previous Revision Date

Summary of Changes Change Author

5/15/04 NA Initial Draft NA 5/22/04 5/15/04 Proofreader touch-up’s R. Minsky

Distribution This document has been distributed to:

Name Title Date of Issue

Version

K. Collins SVP 6/1/04 Final

Riordan Lessons Learned Report

Purpose To share lessons that may be of value to other projects.

Contents This publication contains the following topics:

Topic See Page Management and quality processes 2 Abnormal events 2 Technical methods and tools 2 Project Issues 3 Recommendations 3

Management and quality processes Positives - Brainstorming session helped identify numerous user requirements

that the technical team could evaluate for feasibility - Use of instant messaging for just-in-time discussions between project

team members - Weekly face-to-face meetings with project team to share updates and

vent frustrations Negatives - Inconsistent participation by user representatives

- Waiting until the end of extensive development prior to obtain user feedback

Not available - Issue tracking tool available to all team members (all items had to be funneled to a single contact for data entry into Excel)

- Sophisticated CAD tool not available at start of project (some delays until tool installed and accessible)

Abnormal events - Key technical contact not available for extended period (personal

leave) - Unexpected power outage resulted in loss of some project data

Technical methods and tools CAD tool available at project start antiquated. Further investigation revealed

that tool was no longer supported by vendor source, necessitating a fast-track approach to investigating and securing a more adequate alternative.

Riordan Lessons Learned Report

Project Issues

a) CAD tool not advanced enough to model submitted changes – see “Technical Methods and Tools” section; CAD tool upgraded for assigned CAD operators b) Incorporating additional materials increase product development costs by 20% - resulted from user feedback/change requests; intend for product’s revenue to cover resource investments c) Operational units not outfitted to accommodate modifications suggested via change requests – decision to invest in internal staff training or engaging contractual/offshore resources delegated to higher level management d) User representatives continue to submit change requests as development team attempts to finalize design – Ongoing Product Support activity to manage users expectations

Recommendations For future projects, consider the following activities:

- Solicit 1-2 representatives from each user area to evaluate project deliverables to help insure that all user perspectives are available

- Use iterative product development methodologies that allow users to see and comment on product building blocks (versus nearly complete end product) so development can shift focus if necessary with relative ease

- Evaluate appropriateness/value of available tools/technologies early in the planning process to allow time for acquisition of replacements if warranted

- Pair up key staffing resources so backup staff is readily available to key project schedule on track