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

• Hardware Compatibility Issues• Software Compatibility Issues – ERP • Availability of Resources

• Scope Creep & Last Minute Changes– Enforce a strict change control process

FAILURE MODES & EFFECTS ANALYSIS WORKSHEET

Process / Product: FMEA Date (Original):

WHEN

Item/ Process Step

WHAT

Potential Failure Mode Potential Effect(s) of Failure

Severity

WHY

Potential Cause(s) of Failure

Occurrence Mitigation Controls

Detection RPN

Technical Infrastructure Delay in Project because of the need to order new hardware 7 Constant changes & updates with

hardware & drivers 3 Check to ensure latest drivers are installed 2 42

Testing Unsuccessful system test scripts Unable to proceed with testing until test scripts are revised 3

Failure to gather correct testing requirements during Test Planning Phase.

5Have formal review and sign-off on test plans with individuals that have multiple expertise.

4 60

Deployment Deployment from test environment to production unsuccessful

Time needed to troubleshoot and resolve issues 7 Incomplete / inaccurate test plan 4

Have formal review and sign-off on test plans with individuals that have multiple expertise.

3 84

Project Management Inappropriate Resource Leveling Delay or failure of the project 8 Inefficient resource allocations 6 Evaluate project plan to ensure proper resource allocation 2 96

Detailed Design Time delays caused by new planning, design, and rework efforts 7 Key Stakeholders were not included

during requirements phases 7 Develop a through stakeholder analysis 2 98

Project Management Loss of key resource(s) Left without an expert 7 Retirement, new job, personal emergency 3 Have a back-up for each critical task 5 105

Project Management Inappropriate Work Assignments People are not working in areas of their expertise 5 Individual Strengths and Expertise not

identified 6 Develop a RACI Matrix 4 120

Software Requirements S Delays in attempting to correct issues 9 Inadequate planning 4 Verify all software requirements with key stakeholders, gather formal sign-off 4 144

Test Planning Failure to consider end to end testing Incomplete test plans 8 Test Plan designer did not have a full understanding of the system 4 Ensure Test Planner is involved with

design from the beginning 6 192

Development & Unit Test Inefficient workflow 9 Poor quality of code 4 Peer Reviews 6 216

Software Requirements Design shortcuts taken to meet deadline Does not meet customer needs 9 Designer does not understand workflow / Inefficient Design 5 Ensure communication between

designer and key stakeholders 7 315

System Requirements Gathering Inaccurate Requirements Delays due to Scope Change 9 Making Assumptions, rather than verifying information 9

Hold requirement walkthroughs with all key stakeholders (business & technical), gather formal sign-off

7 567

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!