The document discusses reasons why IT projects fail and succeed. It fails due to incomplete requirements, lack of user involvement, poor planning and unclear objectives. It succeeds with clear requirements, user involvement, management support, thorough planning and realistic schedules. The role of the project manager is to organize tasks, develop schedules, assign team members, monitor progress and quality, and report status. Project planning involves defining problems, scheduling tasks, confirming feasibility through risk assessment and cost/benefit analysis.

1. The Analyst as a Project Manager
Systems Analysis and Design

2. System Development Facts
• 32% of all development projects are cancelled
before they were completed
• More than half of computer system projects cost
almost double the original budget
• Many systems are implemented with only a
portion of the original requirements satisfied
• Completely successful projects range only from 9-
16%
• System development is a difficult activity
requiring careful planning, control and execution

3. Some Reasons Why Projects Fail:
• Incomplete or changing system requirements
• Limited user involvement
• Lack of executive support
• Lack of technical support
• Poor project planning
• Unclear objectives
• Lack of required resources

4. Some Reasons Why Projects Succeed:
• Clear system requirement definitions
• Substantial user involvement
• Support from upper management
• Thorough and detailed project plans
• Realistic work schedules and milestones

5. Project Management
• Project management is organizing and
directing other people to achieve a planned
result within a predetermined schedule and
budget.

6. The Role of the Project Manager
• Identify tasks and build a work breakdown
structure
• Develop a project schedule
• Recruit and train team members
• Assign team members to tasks
• Coordinate activities of team members and
subteams
• Assess project risks
• Monitor and control deliverables and milestones
• Verify the quality of project deliverables

7. External Responsibilities of a Project Manager
• Report the project’s status and progress
• Establish good working relationships with the
people who will use the system
• Work directly with the client
• Identify resource needs and obtain resources

8. A Project Manager works with several
groups of people:
• Client – the person/group who funds the
project
• Oversight Committee – clients and key
managers who review and direct the project
• User – the person/group of persons who will
use the system

9. Participants in a System Development
Project
Project
Manager
Client
Oversight
Committee
Users
Team Leader A
• Programmer
• Designer
Team Leader B
• DB Admin
• DB Designer

10. Project Initiation and Project Planning
• Information System development projects are
initiated for various reasons:
– To respond to an opportunity
– To resolve a problem
– To conform to a directive

11. The Project Planning Phase
Define
the
problem
Produce
the
project
schedule
Confirm
project
feasibility
Staff the
Project
Launch
the
Project

12. Defining the Problem
• System Scope Document – a document
containing problem description, business
benefits and system capabilities to help define
the scope of a new system

13. Producing the project schedule
• Gantt Chart – a bar chart that represents the
tasks and activities of the project schedule

14. Confirming Project Feasibility
• Risk Management – the project management area in
which the team tries to identify the potential trouble
spots that could jeopardize the success of the project
• Economic Feasibility – compare the cost of the project
with the expected benefits
• Determine the organizational and cultural feasibility
• Evaluate the technological feasibility
• Determine the schedule feasibility
• Assess the resource feasibility

15. Assignment:
• System Scope Document
• Gantt Chart