Loading documents preview...
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
Process / Product:
• Hardware Compatibility Issues • Software Compatibility Issues – ERP • Availability of Resources
WHAT
WHEN
Item/ Process Step
Potential Failure Mode
Technical Infrastructure
Potential Effect(s) of Failure
FMEA Date (Original):
Sev erit y
WHY
Potential Cause(s) of Failure
Delay in Project because of the 7 need to order new hardware
Constant changes & updates with hardware & drivers
Oc cur ren ce Mitigation Controls
3
Testing
Unsuccessful system test scripts
Unable to proceed with testing 3 until test scripts are revised
Failure to gather correct testing requirements during Test 5 Planning Phase.
Deployment
Deployment from test environment to production unsuccessful
Time needed to troubleshoot and resolve issues
Incomplete / inaccurate test plan
7
4
Check to ensure latest drivers are installed
Det ecti on 2
Have formal review and sign-off on test plans with individuals 4 that have multiple expertise. Have formal review and sign-off on test plans with individuals 3 that have multiple expertise. Evaluate project plan to ensure 2 proper resource allocation
• Scope Creep & Last Minute Changes Project Management
Inappropriate Resource Leveling
Detailed Design
Delay or failure of the project
8
Time delays caused by new planning, design, and rework efforts
7
Inefficient resource allocations 6 Key Stakeholders were not included during requirements phases Retirement, new job, personal emergency Individual Strengths and Expertise not identified
42
60 84 96 98
3
Have a back-up for each critical 5 task
105
6
Develop a RACI Matrix
4
120
Loss of key resource(s)
Left without an expert
Project Management
Inappropriate Work Assignments
People are not working in areas 5 of their expertise
Software Requirements
S
Delays in attempting to correct 9 issues
Inadequate planning
4
Verify all software requirements with key stakeholders, gather 4 formal sign-off
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 4 system
Ensure Test Planner is involved 6 with design from the beginning
192
Inefficient workflow
9
Poor quality of code
Peer Reviews
216
Development & Unit Test
7
RPN
Develop a through stakeholder 2 analysis
7
– Enforce a strict change control process
Project Management
4
Software Requirements
Design shortcuts taken to meet deadline
Does not meet customer needs 9
Designer does not understand 5 workflow / Inefficient Design
System Requirements
Gathering Inaccurate Requirements
Delays due to Scope Change
Making Assumptions, rather than verifying information
9
9
6
Ensure communication between designer and key 7 stakeholders Hold requirement walkthroughs with all key stakeholders 7 (business & technical), gather formal sign-off
315
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!