A&d High Tech - Team 2.pptx

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 & EFFECTS ANALYSIS WORKSHEET

• Hardware Compatibility Issues • Software Compatibility Issues – ERP • Availability of Resources Item/ Process Step

Potential Failure Mode

Technical Infrastructure

Potential Effect(s) of Failure Delay in Project because of the need to order new hardware

7

WHY

Potential Cause(s) of Failure Constant changes & updates with hardware & drivers Failure to gather correct testing requirements during Test Planning Phase.

Detection

Severity

WHAT

WHEN

3

Testing

Unsuccessful system test scripts

Unable to proceed with testing until test scripts are revised

3

Deployment

Deployment from test environment to production unsuccessful

Time needed to troubleshoot and resolve issues

7

Incomplete / inaccurate test plan

4

Project Management

Inappropriate Resource Leveling

Delay or failure of the project

8

Inefficient resource allocations

6

5

Mitigation Controls Check to ensure latest drivers are installed Have formal review and sign-off on test plans with individuals that have multiple expertise. Have formal review and sign-off on test plans with individuals that have multiple expertise. Evaluate project plan to ensure proper resource allocation

2

42

4

60

3

84

2

96

Develop a through stakeholder analysis

2

98

Have a back-up for each critical task

5

105

4

120

4

144

6

192

6

216

7

315

7

567

• Scope Creep & Last Minute Changes Detailed Design

Project Management

Loss of key resource(s)

Time delays caused by new planning, design, and rework efforts

7

Left without an expert

7

Key Stakeholders were not included during requirements phases

7

Retirement, new job, personal 3 emergency Individual Strengths and Expertise not 6 identified

– Enforce a strict change control process

Project Management

Inappropriate Work Assignments

People are not working in areas of their expertise

5

Software Requirements

S

Delays in attempting to correct issues 9

Test Planning

Failure to consider end to end testing

Incomplete test plans

8

Inefficient workflow

9

Development & Unit Test Software Requirements

Design shortcuts taken to meet deadline

Does not meet customer needs

9

System Requirements

Gathering Inaccurate Requirements

Delays due to Scope Change

9

Inadequate planning

Test Plan designer did not have a full understanding of the system Poor quality of code Designer does not understand workflow / Inefficient Design Making Assumptions, rather than verifying information

4 4 4 5

9

RPN

FMEA Date (Original):

Occurrence

Process / Product:

Develop a RACI Matrix Verify all software requirements with key stakeholders, gather formal signoff Ensure Test Planner is involved with design from the beginning Peer Reviews Ensure communication between designer and key stakeholders Hold requirement walkthroughs with all key stakeholders (business & 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!