IS Project Management - Gunadarma Universitylintang.staff.gunadarma.ac.id/Downloads/files/27178/... · IS Project Management Program Pascasarjana, ... Temporary nature of projects

IS Project ManagementIS Project Management

Program Pascasarjana, Universitas Gunadarma, Magister Management , Budi Hermana-1

Introduction Framework&Principles Rational Unified Process SPM Plan Suplement

IS Project Management



Introduction Framework&Principles Rational Unified Process SPM Plan SuplementIn

trodu

ctio

n

What is

a Project ?

A project is a temporary endeavour

undertaken to create a unique product or

service

�The end is reached : Project objectives are achieved, or Project is terminated

�Temporary does not mean short in duration�Temporary does not apply project`s products or services�All temporary tasks are not projects�Temporary nature of projects may apply to other aspects :

The opportunity is temporary and – The project team is temporary

�Doing something which has not been done before

�The project might have repetitive elements�The characteristics must be progressively

elaborated : �Elaboration of product characteristics

must be coordinated with project scope definition

� Ideally the scope of the project should remain constant as the product characteristics change.

Examples:

•Developing a new product

•Changing the structure of

organization

•Implementing a new design

processOperations are not projects:

Operations are ongoing and

repetitive

Project always begin with

Problem (John J. Rakos)




trodu

ctio

n

Progressive Elaboration

� Integrates concepts of temporary and unique

�As the product is unique it should be progressively elaborated.

� The scope of the project should remain constant even as the product scope is progressively elaborated.

� Example:

�Problem analysis

�Requirements specification

�Software design

�Coding

�Testing




trodu

ctio

nRich picture of a general software-development process(Mireles and Jacobo)




trodu

ctio

n

What is a

Project

Management

?

Project management is the application of knowledge, skills, tools, and techniques to project activities in order to meet project requirements

Requires to balance: Scope, time, cost and quality:

Scope/quality

Co

st

Time

� Involves stakeholders with different needs and

expectations

� Involves identified requirements

� Management by projects is not project

management.




Relationship to Other Disciplines

Project Management

Knowledge andPractice

Management

Knowledge and

Practises

Application

Area Knowledge

And Practises

Software estimation

Life cycles

Quality models

Significance of problem domain knowledge

Operations:

Planning

Organizing

Staffing

Executing

ControllingIntr

odu

ctio

n




trodu

ctio

nWhy The Project Fail ? – John J. Rakos

Failure at The Start

�Do not get off the ground (without a plan)

�Unrealistic deadline and budget

Failure in The Development stages

�Analysis and design are not documented

�The responsibilities are not clear assigned to spesific individuals

�Design, testing, and implementation methods are invaluable

�Lack of walk-through’s and review

�Many project failures are blamed on turnover

�Lack of development standard

�Brute force techniques such as add more manpower don’t work

Failure at The End

�Delivery without thorough debugging

�Do not deliver the promised performance

�Maintenance cost is too high

�Overrun in expense and schedule, unhappy users, damaged reputation,

waste expensive talent, etc




Fr a

mew

ork

&P

rin

cip

les

Project Management Framework

Scope

Mgt

Time

Mgt

Cost

Mgt

Quality

Mgt

Project Integration Management

HR

Mgt

Comm

Mgt

Risk

Mgt

Procure

Mgt

To

ols a

nd

Tech

niq

ues

Sta

keh

old

ers n

eed

s

an

d ex

pecta

tion

s

Core Function

Facilitating Function




Project Management Framework

Integration Management

�Plan development�Project plan execution�Overall change control

Scope Management

�Initiation�Scope planning�Scope definition�Scope verification�Scope change control

Time Management

�Activity definition�Activity sequencing�Activity durationestimating�Schedule development�Schedule control

Cost Management

�Resources Planning�Cost estimating�Cost budgeting�Cost control

Quality Management

�Quality planning�Quality assurance�Quality control

HR Management

�Organizational planning�Staff acquisition�Team development

Comm. Management

�Communications Planning�Information distribution�Performance reporting�Administrative closure

Risk Management

�Risk identification�Risk quantification�Risk response development�Risk response control

Risk Management

�Procurement planning�Solicitation planning�Solicitation�Source selection�Contract administration�Contract close-out

Fr a

mew

ork

&P

rin

cip

les




Fr a

mew

ork

&P

rin

cip

les

Definition Analysis Design Programming System Test Acceptance Operation

Requirements

Go/no Go decision

Proposal

Requirement

Document (*)

(userS.O.)

Analysis Proposal

(User buys)

Preliminary

project plan

(resource provider

S.O)

Functional

specification

Development

Proposal

Re-estimate

Functional

Spesification

(user S.O)

Estimates and

Project plan

(re-done)

Top level design

System Design

ATP

Re-estimate

Design specifica.

(walked thru.)

Acceptance test

Plan (user s.o)

Revised estimates

(done)

Module Design

Coding

Module Design

(walked thru)

System test Plan

(Done)

User Documen-

Tation

(started)

Programs

(tested)

Project leader

(S.O)

Integration

Testing

Working/

Debugged

System

(Proj.Mgr S.O.)

Acceptance Test

Test Result

(user S.O.)

User Supported

Cutover

Warranty

Sell next project

Post Project Rev.

Maintenance

New system

Operational

(user satis.)

Proposal for

Next project

(user buy)

AC

TIV

ITIE

S

Project Management

Reviews

Status Reports

Documentation User Training

DO

CU

ME

NT

S A

ND

(MIL

ES

TO

NE

S)

Relative Effort

(PM)

(Total Staff)

(*)

PROJECT PHASE

(*) The requirements Document may or may not be part of the project

John J. Rakos




Fr a

mew

ork

&P

rin

cip

les The Iterative Model graph shows how the

process is structured along two dimensions




Fr a

mew

ork

&P

rin

cip

les




The principles of modern software management

(Royce Walker)

Base the process on an architecture-first approach

Establish an iterative life-cycle process that

confronts risk early

Transition design methods to emphasize component-based development

Establish a change management environment

Enhance change freedom through tools that support round-trip

engineering

Fr a

mew

ork

&P

rin

cip

les




Capture design artifacts in rigorous, model-based

notation

Instrument the process for objective quality control and

progress assessment

Use a demonstration-based approach to assess

intermediate artifacts

Plan intermediate releases in groups of usage

scenarios with envolving levels of detail

Establish a configurable process that is economically

scalable

Fr a

mew

ork

&P

rin

cip

les




Fr a

mew

ork

&P

rin

cip

les Work Breakdown Structure

�Determine how to organize the work breakdown

�Time based, i.e. planning/analysis/design/construct/

test/implement

�Deliverable based, i.e. online application/data warehouse/user

query tools

�Geography based, i.e. Chicago Pilot Test/Midwest

Region/Eastern Region

�Other …

�Any breakdown should end up covering all the work

�Sequencing not important for WBS




Work Breakdown Structure

Fr a

mew

ork

&P

rin

cip

les

SIA PROJECTSIA PROJECTLevel 0

Level 1

Level 2

Level 3

0.0

DEFINITIONDEFINITION

ANALYSISANALYSIS

DESIGNDESIGN

PROGRAMMINGPROGRAMMING

SYSTEM TESTSYSTEM TEST

ACCEPTANCEACCEPTANCE

OPERATIONOPERATION

1.0 2.0 3.0 4.0 5.0 6.0 7.0

Requirement

Document

Requirement

DocumentFeasibility

Study

Feasibility

Study Risk AnalysisRisk Analysis Pre. Project

Plan

Pre. Project

Plan ProposalProposal Negotiate

Proposal

Negotiate

Proposal

1.1 1.2 1.3 1.4 1.5 1.6

InterviewsInterviews Analyse

Existing Sys.

Analyse

Existing Sys.Define New

Sys. Function

Define New

Sys. FunctionWrite Funct.

Specification

Write Funct.

SpecificationNegotiate

Func. Spec.

Negotiate

Func. Spec.

2.1 2.2 2.3 2.4 2..5

Office

Manager

Office

ManagerWarehouse

Supervisor

Warehouse

Supervisor RegistrarsRegistrars

CEOCEO

AccountantAccountant

2.1.1 2.1.2 2.1.3 2.1.4 2.1.5




Fr a

mew

ork

&P

rin

cip

les

When Do You

Stop?

� Some person (or group for larger project) can take responsibility

for the task, or to accomplish the activities involved

� You can get rough estimate of the effort (person days) needed to

perform the activity (or activities involved)

� You can schedule the task

� The task must be small and able to be completed

Estimate (person-day) 2 2 1 1 3 2

Total 11 days

Registration

System

Registration

SystemWarehouse

System

Warehouse

SystemCEO’s

Business

CEO’s

BusinessAccountant’s

Business

Accountant’s

Business DocumentsDocuments Data

Flow

Data

Flow

Analyses

Existing Sys.

Analyses

Existing Sys.




Mind-Mapping Approach










1.0 Concept

1.1 Evaluate current systems

1.2 Define Requirements

1.2.1 Define user requirements

1.2.2 Define content requirements

1.2.3 Define system requirements

1.2.4 Define server owner requirements

1.3 Define specific functionality

1.4 Define risks and risk management approach

1.5 Develop project plan

1.6 Brief Web development team

2.0 Web Site Design

3.0 Web Site Development

4.0 Roll Out

5.0 Support

Intranet WBS in Tabular Form




Intranet WBS and Gantt Chart in Project 2000







Fr a

mew

ork

&P

rin

cip

les The person responsible for the plan (probably the project manager for a small to mid

sized project) then collate all the estimate and precedent, as follows

210TOTAL

Acceptance10Operation

Documentation10Training

System Test, Documentation5Acceptance

Design20Documentation

Program A, B, C10System Test

Design25Program C (Warehouse)

Design30Program B (Registration)

Design20Program A (Control)

Analysis25Design

Definition35Analysis

-20Definition

PRECEDENTSEFFORTACTIVITY

Note:

This example only the progranning had sub-component. If there are any sub-

component of any other major activity avaliable, they would also be listed

Network

Diagram




Fr a

mew

ork

&P

rin

cip

les Network Diagram

STRT

0

DEF

20

ANAL

35

DES

25

PGMB

30

SYS TST

10

ACC

5

OPER

10END

PGMB

30

PGMB

30

PGMB

30

OPER

10Precedence Network

Another Format …..

Activity on Arrow

0

1Activity n

t




Critical Path Method

1 2A

10 day

3

4 5

6 7

B C

G

D

E

F

5 day

3 day

4 day

6 day

3 day

5 day

0 10

0 + 10 15

10 + 5

13

10 + 3

17

13 + 420?

17 + 3

21?

15 + 6

21 26

21 + 5





1 2A

10 day

3

4 5

6 7

B C

G

D

E

F

5 day

3 day

4 day

6 day

3 day

5 day

0 10

15

13 17

21 26

2621

26 - 5

15

21 - 6

1821 - 3

14

18 - 4

11 ?

14 - 3

10 ? 15 - 5

100

10 - 10





1 2A

10 day

3

4 5

6 7

B C

G

D

E

F

5 day

3 day

4 day

6 day

3 day

5 day

0 10

15

13 17

21 26

2621

15

1814

100

Project Duration : 26 day

: Critical path


