PM Time Management 0 Why IT Projects Fail
- Slides: 16
PM Time Management 0
Why IT Projects Fail to Deliver on Promises ? Req. The system delivered did not meet the requirements 46% Req. The system was used as intended but did not produce expected benefits 40% Req. The system worked, but the intended users would not use it 38% The technology did not work 37% Time The system met the requirements but was late 37% Time The system met the requirements, but the requirements had changed by the time it was delivered 35% There was a failure in business change management 35% The benefits were obtained but no longer mattered to the business 22% Time Source: "The User's View of Why IT Projects Fail, " February 2005: Report G 00124846 1
6. Time Management Activity Definition Scope Definition Develop Project Management Plan Activity List Activity Sequencing Create WBS Requested Changes Network Diagram Activity Resource Estimating Select Sellers Acquire Project Team Resource Availability Activity Duration Estimating Cost Estimating Risk Management Schedule Development Risk Register Project Schedule Close Project 4 Schedule Control Integrated Change Control
6. Time Management Activity Sequencing Precedence Diagramming Method (PDM) : Box나 Node를 사용해서 Activity들을 표시, 화살표로 연관(의존, 선후)관계를 연결(most common method) § Network Diagram 예 : Activity-on-Node (AON)라고도 함. A B C 시작 D H F I K ES=10/14 E G 종료 J L Task(Activity) name LS=10/19 7 LF=10/22 Duration, TF or FF § 4가지 유형의 연관 관계 • • EF=10/22 Finish-to-Start (Most Common) : 선행 활동이 완료되면 후속 활동 시작 Finish-to-Finish : 선행 활동이 완료되면 후속 활동 완료 Start-to-Start : 선행 활동이 시작되면 후속 활동 시작 Start-to-Finish (사용빈도 낮음) : 선행 활동이 시작되면 후속 활동 완료
6. Time Management Activity Duration Estimating 각 Activity를 완료하기 위해 필요한 기간을 산정 ■ Analogous Estimating : 이전에 유사한 일정 활동을 기준으로 산정 ■ Parametric Estimating : 수행할 작업 양을 생산율(productivity rate)로 곱해서 활동 기간 기준을 산정 ■ 3점 추정 : 전에 수행 경험이 전혀 없을 경우 : Mostly likely, Optimistic(best), Pessimistic(worst) 평균 = (P + 4 M + O) / 6 Tool & Technique Expert judgment Analogous estimating Parametric estimating Three-point estimating Reserve analysis Parametric Estimating 소규모 프로젝트 또는 단위작업 10 Three-Point Estimate Most likely Average Optimistic Pessimistic
6. Time Management Schedule Development : Forward Scheduling 과 Backward Scheduling의 반복적인 프로세스로서 프로젝트 활동에 대해 시작 및 종료 일을 결정 ITO Input Tool & Technique Output Project scope statement Schedule network analysis (일정 네트워크 분석) Critical Path Method Schedule compression (일정 단축) What-if scenario analysis Resource leveling Critical chain method Adjusting leads & lags (선행 & 지연 조정) Schedule model Project schedule Activity list & attributes Project schedule network diagram Activity resource requirements Activity duration estimates 11 Schedule model data Schedule baseline Resource requirements (updates) Activity attributes (updates) Project calendar (updates)
13
- Hey hey bye bye
- Contoh tutup fail putih
- What if you fail ramadan
- People don t plan to fail they fail to plan
- Npv vs irr graph
- Scheduling resources and costs
- Dont ask why why why
- Why did the qing’s self strengthening movement fail?
- Spartacist revolt
- Why aquaponics fail
- A peaceful crusade or campaign for reforms by means of pen
- Leading change: why transformation efforts fail
- Why do the bodys antibodies fail to protect people from hiv
- Why did the italian revolution of 1848 fail
- Abyssinia league of nations failure
- League of nations
- Swoops chips