Why Project Mgmt Concerns

1
(No Transcript)
2
(No Transcript)
3
(No Transcript)
4
(No Transcript)
5
(No Transcript)
6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
Why Project Mgmt Concerns

• Almost one-third of IS/IT projects never finish
• Over half of IS/IT projects cost almost twice the
  original estimate
• Only slightly more than 15 finish on time and
  within budget
• Standish Group International
• Chaos Report a survey of 365 companies

10
(No Transcript)
11
Top Five Reasons for Failure

• Lack of Prioritization (Only one number one)
• No one in charge (with power and knowledge)
• Poor Requirements Management
• Poorly defined scope (80/20 rule)
• Missing details (often 50 of tasks)
• Lack of Inspections (adds a third to the time)
• No Project Management
• Lack of control (line control of all resources)
• No true plan (WBS and PERT)

12
Prioritizing

• Too Many Projects, Too Few Resources
• Intelligent prioritizing resource allocation
• dollars
• people
• There can be only one number one project
• Who is in charge
• customer functional executive or steering
  committee
• customer user manager or IS project manager

13
Poor Requirements Analysis

• Poorly Defined Scope
• finite number of functions (transactions/files)
• 80/20 rule
• manageable complexity of functions (TPS/MIS
  separation)
• Incomplete Business Requirements (Analysis)
• Incomplete Technical Requirements (Design)
• details found during testing

14
Lack of Inspections

• You cant test quality into a product
• quality circles
• Structured walkthroughs
• Requirements documents and operations manuals
• All technical documents (system, conversion and
  testing)
• Add 30 for inspections

15
No Project Management

• Why project management
• Can you do it? (reliable estimating)
• Where are we? (based on plan)
• Are we in control? (WBS 20-40 hours each)
• When will we be done? (PERT chart)
• Prove someone is in charge

16
No True Plan

• Defines all required resources
• personnel (executive, customer, IS/IT)
• technology (infrastructure, applications)
• funding and time
• Defines monitoring and oversight
• Defines Change control
• Specifies completion of milestones and current
  phase
• All stakeholders believe in the plan