Professional Documents
Culture Documents
01-2 ITPM Ch01
01-2 ITPM Ch01
1. ________________________________________________________
2. ________________________________________________________
3. ________________________________________________________
Motivation for Studying IT Project Management
IT projects have a terrible track record.
A 2003 Standish Group study (CHAOS) found
that only 16.2 percent of IT projects were
successful in meeting scope, time, and cost
goals.
Over 31 percent of IT projects were canceled
before completion, costing over $81 billion in
the U.S. alone.
Advantages of Using
Formal Project Management
Better control of financial, physical, and human resources.
Improved customer relations.
Shorter development times.
Lower costs.
Higher quality and increased reliability.
Higher profit margins.
Improved productivity.
Better internal coordination.
Higher worker morale (less stress).
What is a Project?
A project is “a temporary endeavor undertaken to create
a unique product, service, or result.” –PMBOK
Attributes of projects
Unique purpose
Non-routine tasks are involved
Temporary
Planning is required
Specific objectives are to be met or a specified project is to
be created
The project has a pre-determined time span
What is a Project? (Cont.)
More attributes
Work is carried out for someone other than yourself
Work require resources, often from various areas or involve
several specializes
Work is carried out in several phases
The resources that are available for use on the project are
constrained
Should have a primary sponsor and/or customer
Project can be large or small and take a short or long time to
complete
Involve uncertainty
Activity: Spot the Project
Read the following list and place a checkmark next to
the items that are IT Projects.
First-line support of mail-merge product.
A help desk or technical worker replaces laptops for a
small department.
A small software development team adds a new feature
to an internal software application .
The University campus upgrades its technology
infrastructure to provide wireless Internet access across
the whole campus.
Activity: Spot the Project (Cont.)
A cross-functional task force in a company decides what
VoIP system to purchase and how it will be implemented.
Update company hardware specification and software
license information.
Implement a new financial software package and integrate
it with existing systems.
Creation of a new Web page to support marketing.
Maintenance of the company reference databases.
A company develops a new system to increase sales force
productivity and customer relationship management.
Activity: Spot the Project (Cont.)
The automobile industry develops a Website to streamline
procurement.
Business application training for new employee.
A television network develops a system to allow viewers
to vote for contestants and provide other feedback on
programs.
A large group of volunteers from organizations throughout
the world develop standards for a new communication
technology.
Note: “IT projects” refers to projects involving
hardware, software, and networks.
Project and Program Managers
Project managers work with project sponsors,
project teams, and other people involved in
projects to meet project goals.
Program: “A group of related projects managed in
a coordinated way to obtain benefits and control
not available from managing them individually.”
Program managers oversee programs and often act
as bosses for project managers.
Reasons for a Project
Every IT project that you do is for a business reason.
In order for a project to make sense in a commercial
context, the business must ultimately gain benefit from
the delivery.
Projects should have a place within the strategic plans of
the organization:
The corporate business strategy
The corporate IT strategy
Projects without clear context can be difficult to
complete successfully.
Activity: The Business Need
Reasons for IT project
Opportunities Problems
The Triple Constraint of Project Management
Every project is constrained in different ways by its:
Scope:
What work will be done as part of the project?
What unique product, service, or result does the customer or
sponsor expect from the project?
How will the scope be verified?
Time:
How long should it take to complete the project?
What is the project’s schedule?
How will the team track actual schedule performance?
Who can approve changes to the schedule?
The Triple Constraint of Project Management
Every project is constrained in different ways by its:
Cost:
What should it cost to complete the project?
What is the project’s budget?
How will costs be tracked?
Who can authorize changes to the budget?
It is the project manager’s duty to balance these three
often competing goals.
The Triple Constraint of Project Management
Successful project
management means
meeting all three
goals (scope, time,
and cost) – and
satisfying the
project’s sponsor!
What is Management?
Management may involve:
Planning - deciding what is to be done
Organizing - making arrangement
Staffing - selecting the right people
Directing - giving instructions
Monitoring - checking on progress
Controlling - taking action to remedy hold-ups
Innovating - coming up with new solutions
Representing - liaising with users
Problems with IT Projects
Manager’s point of view problems:
Poor estimates and plans
Lack of quality standards and measures
Lack of guidance about making organizational
decisions
Lack of techniques to make progress visible
Poor role definition – who does what?
Incorrect success criteria
Problems with IT Projects (Cont.)
Members of team point of view problems:
Inadequate specification of work
Management ignorance of IT
Lack of knowledge of application area
Lack of standards
Lack of up-to-date documentation
Preceding activities not completed on time – including
late delivery of equipment
Lack of communication between users and technicians
Lack of communication leading to duplication of work
Problems with IT Projects (Cont.)
Members of team point of view problems: (Cont.)
Lack of commitment – especially when a project is tied to
one person who then moves
Narrow scope of technical expertise
Changing statutory requirements
Changing software environment
Deadline pressure
Lack of quality control
Remote management
Lack of training
What is Project Management?
Is it worth doing?
How do we do it?
Feasibility study
Do it!
Planning
Project Execution
Activities Covered by Project Management
Feasibility study - decide if project is worth doing
Identifies what the project is
Description of current situation
Problem description
Proposed development
Business and financial aspects
Technical aspects
Organizational aspects
Activities Covered by
Project Management (Cont.)
Feasibility study (Cont.)
Estimated costs
Development costs
Setup Costs
Operational costs
Envisaged benefits
Recommendations
Planning - how you are going do it?
Project execution - do it
Project Management Framework
Identify the Project Stakeholders
Stakeholders are the people involved in or affected by
project activities.
Key questions:
Who are the people who make up the business?
What roles do they play in the organization and in the context
of the project?
What do these people want from the project?
Who is the team that will deliver this project?
Start by identifying the groups that are the project
stakeholders.
Identify the Project Stakeholders (Cont.)
Project Owners
Management and buyers
Engineers and end users
Business departments —managers
Business departments—staff
Marketing and sales
Finance
Production and manufacturing
Identify the Project Stakeholders (Cont.)
Project Participants (Full-time and part-time)
Project manager
Project team
Support staff
Quality team/configuration team/maintenance team
MIS help desk/network operations
Contractors and third parties
Suppliers
Nine Project Management Knowledge Areas
Knowledge areas describe the key competencies that project
managers must develop.
Four core knowledge areas lead to specific project
objectives (scope, time, cost, and quality).
Four facilitating knowledge areas are the means through
which the project objectives are achieved (human
resources, communication, risk, and procurement
management).
One knowledge area (project integration management)
affects and is affected by all of the other knowledge areas.
All knowledge areas are important!
Project Management Tools and Techniques
Project management tools and techniques assist
project managers and their teams in various aspects
of project management.
Specific tools and techniques include:
Project Charters, scope statements, and WBS (scope).
Gantt charts, network diagrams, critical path analysis,
(time).
Cost estimates and earned value management (cost).
Super Tools
“Super tools” are those tools that have high use and high
potential for improving project success, such as:
Software for task scheduling (such as project management
software)
Scope statements
Requirements analyses
Lessons-learned reports
Tools already extensively used that have been found to improve
project importance include:
Progress reports
Kick-off meetings
Gantt charts
Change requests
Why the Project Performance has been
Improved?
“The reasons for the increase in successful projects
vary. First, the average cost of a project has been more
than cut in half. Better tools have been created to
monitor and control progress and better skilled
project managers with better management
processes are being used. The fact that there are
processes is significant in itself.”*
The WBS is shown on the left, and each task’s start and finish dates
are shown on the right. First used in 1917, early Gantt charts were
drawn by hand.
Sample Network Diagram
Each box is a project task from the WBS. Arrows show dependencies
between tasks. The bolded tasks are on the critical path. If any task on
the critical path takes longer to complete than planned, the whole
project will slip unless something is done. Network diagrams were
first used in 1958 on the Navy Polaris project before project
management software was available.
Sample Enterprise Project Management Tool