IT Project Management Puspandam katias 2009. Carol, et-all, Managing Information Technology, Pearson Prentice Hall, New Jersey, 2009. 2.

IT Project Management

Puspandam katias2009

Carol, et-all, Managing Information Technology,Pearson Prentice Hall, New Jersey, 2009.

2

Main Points

1. IT portfolio approach for IT investment: to help indentify the right project.

2. Program Management Office structure can ensure the company utilizes best practices for managing approved projects.

3. Two business stakeholder roles (associated with successful project implementation):– Project sponsor– Project champion

3

Main goals

The goals of system projects are:• Implement a quality system that meets the

needs of;• targeted business & its users,• on schedule & • within budged• Requires best practices for managing projects

4

State the project

5

CompetenciesProject Scope Project Time Project Cost

Human Resources Quality Management

Risk Management

Project Communication

Procurement Project Integration

6

Main Points ctd.

4. Planning phase for IT project include:– Project scheduling,– Budgeting,– Staffing

5. To execute & control project team activity, helped by:– PERT charts,– Gantt charts– Project management software.

7

Main Points ctd.

6. Managing IT project risk involves:a. Identifying the potential riskb. Classifying the potential riskc. Assessing the potential consequencesd. Developing response for risk minimizatione. Ongoing risk monitoring.

8

Main Points ctd.

7. Successfully managing business change as part of an IT project

8. requires change management activities throughout the project,

9. also timely responses to unanticipated situation.

9

Main Points ctd.

10.The part of project closing phase:11.Capturing the lesson learned from each

project.12.It can help project managers learn from the

successes & mistakes of other projects in the same organization.

10

Main Points ctd.

13.An important IT capability from the successful management of complex software projects,

14.that often requires outside consulting help.15.Today’s IT project teams are also likely to have

some “virtual” team members working at :a. different company centers,b. countries, c. Working for an IT outsourcing vendor.

11

Main Points ctd.

• Currently:• IT project manager that have repeatedly

delivered quality IT solution, • on-time & within budged, • using project teams of IT & business workers

in different location & time zones, • are therefore especially highly valued.

12

Outline

1. IT Portfolio Management

2. Project Management Roles

3. Project initiation

4. Project Planning

5. Project Executing & Control

6. Project Closing13

Project Mgt. vs Program Mgt.

• Project Management:– Is the application of knowledge, skill, tools &

techniques to a broad range of activities.

• Program Management Office (PMO):– Or Project Office– Is an organizational unit responsible for ensuring

that standard approach to project management are utilized across project and “best practices” are shared across project teams.

14

IT Portfolio Management

• The responsibility of a committee of senior business leaders & IT leaders,

• who approve & prioritize IT project requests for an entire organization,

• & then monitor progress on approved IT projects until they are completed.

15

Practitioners Emphasize

• A senior committee approach, besides project funding is:

• Give better understanding among the organization’s business & IT executives for the reasons:

• why a given IT project was founded, or not founded.

16

Project Prioritization Template

17

Project Management Roles

• Project Manager• Project Sponsor • Project Champion

18

Project Management Roles

19

Project Sponsor• Played by the business mgr. who financially

“own” the project.• Participating in development of the initial

project proposal (assessment of the FS),• Likely to be an officer of the company (CEO,

CFO & CIO)• Provides the funds for the project,• Play an oversight role during the life of the

project.20

Strong Relationship

• From very beginning of the project, • it is critical for the project manager to have a

strong relationship with the project sponsor.• How a project manager can keep a typically

busy executives engaged in an IT project?• See the box, page 423

21

After Project Completed

• After system project has been completed, • the sponsor should also be held accountable

for:• ensuring that the projected system benefits

are achieved after the system is installed.

22

Project Champion

• Is not always a formally designated one,• Although the champion’s contribution to the

project’s success can be critically important.• A business manager with high credibility

among the business users,• this involves continual communications

throughout the project,• about its goals & the milestones achieved.

23

Project Initiation

• The first phase of a project life cycle.• Definition: is the earliest part of a project when

the purpose & requirement are clarified.• “to ensure the project value”1)State the project2)Develop objectives3)Develop work-breakdown structure4)Identify resources requirements

24

State the Project

• To define the purpose & scope of the project:• Ask: What needs to be done?Why are we doing this?When do we need to be finished?How much will/can this cost?• A short statement: action & end result

(performance), time & cost (optional)

25

Develop Objectives• To define the benefits & measured of success

for a project• Ask:At the end of the project, what value will we

have?What benefits do we want?What constrain do we face?What requirements must be met?How will we know when we satisfy each

objectives?26

Develop WBS• To establish specific outputs &

accomplishments to be completed• Ask:• What do we want to accomplish in this

project?• What are the major outputs of this projects?• What are the component parts of…?

27

Identify Resources Requirements• To avoid future resources problem &help

assign responsibility.• Ask (identify the type, amount & cost):What knowledge & skills are needed?What facilities will we need?What equipment is required?What supplies/materials should we have?What special or unusual resources do we

need?28

Project Planning

• Project:1.Scheduling,2.Budgeting &3.staffing

29

Scheduling• Breakdown analysis• Project milestone:• Identified from master schedule, and

developed from detailed work activity list, the task interdependencies, & the time estimates for each task.

• A common pitfall in developing a master schedule is a failure to understand the interdependencies among project tasks & subtask.

30

Budgeting

• The project budget documents the anticipated cost for the total project.

• Like master schedule, the project budget is a living document of anticipated total cost.

• Inexperienced estimators will fall in traps:• Are too optimistic about what is needed to do

the job.• Tend to leave components out &• Do not use a consistent methodology.

31

Staffing

• Involves identifying the IT skill mix for specialists assigned to the projects,

• Selecting personnel who collectively have the skill needed & assigning them to the project,

• Preparing team members for the specific project work &

• Providing incentives for them to achieve the project goals.

32

Planning Documents

33

PERT Chart

34

Status Reporting

35

Managing Project Risk

• One of the goals of project management is to reduce the risk,

• Of failing to achieve the project’s objectives• Risk identification should be undertaken at

the project’s outset,• Based on experience with similar projects

36

Early Warning Sign

37

Risk Management Phase

38

Common Strategies

39

Risk Exposure

40

Managing Business Change

• Unfreezing• Moving• Refreezing

41

Project Closing

• What went right on this project?• What went wrong on this project?• What would you do differently on the next

project, based on your experience with this project?

42