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 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 Failure to gather correct testing requirements during Test Planning Phase. 5 Have 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 Incomplete / inaccurate test plan 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 96 Detailed Design Time delays caused by new planning, design, and rework efforts Key Stakeholders were not included during requirements phases Develop a through stakeholder analysis 98 Loss of key resource(s) Left without an expert Retirement, new job, personal emergency Have a back-up for each critical task 105 Inappropriate Work Assignments People are not working in areas of their expertise Individual Strengths and Expertise not identified Develop a RACI Matrix 120 Software Requirements Delays in attempting to correct issues 9 Inadequate planning Verify all software requirements with key stakeholders, gather formal sign-off 144 Test Planning Failure to consider end to end testing Incomplete test plans Test Plan designer did not have a full understanding of the system Ensure Test Planner is involved with design from the beginning 192 Development & Unit Test Inefficient workflow Poor quality of code Peer Reviews 216 Design shortcuts taken to meet deadline Does not meet customer needs Designer does not understand workflow / Inefficient Design Ensure communication between designer and key stakeholders 315 System Requirements Gathering Inaccurate Requirements Delays due to Scope Change Making Assumptions, rather than verifying information Hold requirement walkthroughs with all key stakeholders (business & technical), gather formal sign-off 567 Hardware Compatibility Issues Software Compatibility Issues – ERP Availability of Resources Scope Creep & Last Minute Changes Enforce a strict change control process

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!