A&D High Tech Project

Team 2:
Yusuf Akkoca
Tom Bloom
Karen Delton
Shweta Hire
Eric Johnson
David Mahzonni
 Project Priority
• Main priority is completion time
• May until Mid November to
complete;
about 6 months
 Projected Completion Time

• 322 Days to Complete

• With Deployment at 11/14/2003
and 100% resource usage.
 Costs – Labor & Capital

• Total costs $3,846,782

– Hardware costs $98,500
– Labor costs $3,748,282
Critical Path
 Potential of on Time Completion

• High potential for Failure

 Risks & Mitigation
FAILURE MODES &

• Hardware Compatibility Issues

EFFECTS ANALYSIS
WORKSHEET
Process / Product: FMEA Date (Original):

• Software Compatibility Issues – ERP

RPN
Detection
Occurrence
WHAT WHY

Severity
WHEN

Item/ Process Step Potential Failure Mode Potential Effect(s) of Failure Potential Cause(s) of Failure Mitigation Controls
Delay in Project because of the need Constant changes & updates with Check to ensure latest drivers are

• Availability of Resources
Technical Infrastructure 7 3 2 42
to order new hardware hardware & drivers installed
Failure to gather correct testing Have formal review and sign-off on
Unable to proceed with testing until
Testing Unsuccessful system test scripts 3 requirements during Test Planning 5 test plans with individuals that have 4 60
test scripts are revised
Phase. multiple expertise.
Have formal review and sign-off on
Deployment from test environment to Time needed to troubleshoot and
Deployment 7 Incomplete / inaccurate test plan 4 test plans with individuals that have 3 84
production unsuccessful resolve issues
multiple expertise.
Evaluate project plan to ensure proper
Project Management Inappropriate Resource Leveling Delay or failure of the project 8 Inefficient resource allocations 6 2 96
resource allocation

• Scope Creep & Last Minute Changes

Time delays caused by new planning, Key Stakeholders were not included Develop a through stakeholder
Detailed Design 7 7 2 98
design, and rework efforts during requirements phases analysis
Retirement, new job, personal
Project Management Loss of key resource(s) Left without an expert 7 3 Have a back-up for each critical task 5 105
emergency

– Enforce a strict change control process

People are not working in areas of Individual Strengths and Expertise not
Project Management Inappropriate Work Assignments 5 6 Develop a RACI Matrix 4 120
their expertise identified
Verify all software requirements with
Software Requirements S Delays in attempting to correct issues 9 Inadequate planning 4 key stakeholders, gather formal sign- 4 144
off
Test Plan designer did not have a full Ensure Test Planner is involved with
Test Planning Failure to consider end to end testing Incomplete test plans 8 4 6 192
understanding of the system design from the beginning
Development & Unit Test Inefficient workflow 9 Poor quality of code 4 Peer Reviews 6 216
Designer does not understand Ensure communication between
Software Requirements Design shortcuts taken to meet deadline Does not meet customer needs 9 5 7 315
workflow / Inefficient Design designer and key stakeholders

Hold requirement walkthroughs with

Making Assumptions, rather than
System Requirements Gathering Inaccurate Requirements Delays due to Scope Change 9 9 all key stakeholders (business & 7 567
verifying information
technical), gather formal sign-off
 Scope Changes / Change Control
• Develop a Strict Change control Process.
• Only approve changes deemed critical, other
will be added to a “Phase 2”.
Thank you!