Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Maulia chapter 9 IT BSC jessica keyes

547 views

Published on

Project Risk Mngmnt

Published in: Business, Technology
  • Be the first to comment

Maulia chapter 9 IT BSC jessica keyes

  1. 1. Chapter 9 COMPLIANCE, A WARENESS, AS SURANCE Maulia Jayantina Islami (23510095) maulia@students.itb.ac.idPresented on IT Strategic Planning Class-MCIO ITB 2011
  2. 2. BSC assure IT asset Aligned with Organization’s goaland Well managed so Risk can be minimized assure IT assets aligned well-managed efficient Minimize Risk productive
  3. 3. “Most IT Departments utilize ineffective Project Managemet technique” ~Jessica Keyes~ Survey ‘2000 • 53 % overrun on schedule & budget • 31 % cancelled • 16 % completed on time • 87 % over budget more than half Suceesful IT • 45 % failed (didn’t get the expected benefit) project • 88-92 % over schedule need Project Management Technique
  4. 4. Chapter AgendaHow IT Project Management Fits into the BSC The Proactive Risk Strategy Risk Awareness Risk Assesment Critical Factors to Project Success
  5. 5.  Identify Risk by creating risk item checklist  Customer will change or modify requirements  End Users lack sophistication  Delivery deadline will be tightened  End User resist system  Server may not be able to handle larger number of user simultaneously  Technology will not meet expectation  There is a larger number of users than planned  End Users lack training  The project team is inexperienced  The system (security and firewall) will be hacked
  6. 6. • Categorize Risks (Keil et al, 1998)  Customer will change or modify requirements  End Users lack sophistication  Delivery deadline will be tightened Project Risk  End User resist system  Server may not be able to handle larger number of user Contoh simultaneously  Technology will not meet expectation Technical Risk  There is a larger number of users than planned  End Users lack training  The project team is inexperienced  The system (security and firewall) will be hacked Business Risk  ………………  ………………
  7. 7.  RMMM (Risk Mitigation, Monitoring, and Management)Tabel 9.2 Typical Risk Mitigation, Monitoring, and Management (RMMM) Planx.1 Scope and Intent of RMMM Activities Project ini akan di-apload ke server, dan server ini diekspose ke dunia luar, sehingga perlu dikembangkan security protection….... (dst.)x.2 Risk Management Organizational Role Manajer proyek harus menjaga effort dan schedule team agar sesuai jalur. Menjadi tanggungjawab bersama untuk proactive dalam mengantisipasi resiko yang potensial terjadi selama project berlangsung….. (dst.)x.3 Risk Descriptionx.3.1 Description of Possible Risks Bagian ini akan mendeskripsikan risks yang mungkin terjadi selama project berlangsung Business Impact Risk: (BU) Software yang diproduksi tidak sesuai dengan kebutuhan dan permintaan client. Resiko ini akan berakibat pada bisnis jika produk tidak lagi sesuai dengan keseluruhan strategi bisnis dari perusahaan. Customer Characteristic Risk: (CU) Kurangnya keterlibatan customer dalam project, dan customer tidak dapat bertemu dengan developer pada waktu yang tepat. Pengalaman customer terhadap produk yang dikembangkan dan kemampuan untuk menggunakannya juga termasuk di dalam resiko ini. Development Risk: (DE) Resiko yang diasosiasikan dengan ketersediaan dan kualitas tools yang akan digunakan dalam membuat produk. Peralatan dari sisi client harus compatible dengan software yang akan dibuat.
  8. 8.  RMMM Plan. Risk Table ProbabilityNo. Risks Category Impact (%)1 Customer will change or modify requirements PS 70 22 Lack of sophistication of end user CU 60 33 Delivery deadline will be tightened BU 50 24 Technology will not matc expectation TE 30 15 Inexperienced Project Team ST 20 26 Server may not be able to handle a larger number PS 30 1 of users simultaneously7 System (security and firewall) will be hacked BU 15 2
  9. 9.  Sample RMMM StrategyTable 9.3 Sample RMMM StrategyProject Risk RMMM StrategyBudget sebagian besar dikontribusikan untuk area desain dan development yaitu subsistemdatabase. Oleh karena itu jadwal dan personil akan disesuaikan untuk meminimalisasi efek danmaksimalisasi keuntungan yang seharusnya didapat. (dst…….)Technical Risk RMMM StrategyMenambahkan 2 senior software engineer yang berpengalaman dalam web based application.Untuk memenuhi tenggat waktu yang diberikan dan kesesuaian hasil, maka kemajuan project akandimonitor secara ketat. (dst……)Business Risk RMMM StrategyUntuk mengantisipasi kurangnya dukungan oleh manajemen senior terhadap project team, makateam akan berjuang keras untuk menunjukkan positive attitude selama meeting dengan customer,sama baiknya dengan menunjukkan performa kerja yang professional. (dst……..)
  10. 10.  RMMM Risk Information Sheet (williams et al., 1997)
  11. 11. Avoid the risk by Evaluating the Critical Success Factor (CSF) of business or business lineTable 9.5 CSF Project Chart Critical Success Factor No Business Process 1 2 3 4 5 6 Count QualityP1 Measure delivery performance by suppliers X X 2 BP2 Recognize/reward workers X X 2 DP3 Negotiate with suppliers X X X 3 BP4 Reduce number of parts X X X X 4 DP5 Train supervisors X X 2 CP6 Redesign production line X X X 3 AP7 Move parts inventory X 1 EP8 Eliminate excessive inventory build-ups X X 2 CP9 Select suppliers X X 2 BP10 Measure X X X 3 EP11 Eliminate defective parts X X X 3 D
  12. 12. Divide business process priorityTable 9.5 CSF Project Chart Critical Success Factor No Business Process 1 2 3 4 5 6 Count QualityP1 Measure delivery performance by X X 2 B QUALITY suppliersP2 Recognize/reward workers X X 2 DP3 Negotiate with suppliers X X X 3 BP4 Reduce number of parts X X X X 4 DP5 Train supervisors X X 2 CP6 Redesign production line X X X 3 AP7 Move parts inventory X 1 EP8 Eliminate excessive inventory build-ups X X 2 CP9 Select suppliers X X 2 BP10 Measure X X X 3 EP11 Eliminate defective parts X X X 3 D PRIORITY Figure 9.1 CSF Priority Graph
  13. 13. Being PoliticalProper Standard Technical Critical Factor Effective to prjectCommunication Success Legal Ethics Organization
  14. 14. • Effective Communication  Make people comfort to talk  Understand end-users  Write effectively with proper style  Meaningful presentation  Clear articulations  Mediate disputes  Understand politics & organizations
  15. 15. • Proper utilization of standards
  16. 16. • Ethics fair forthright ETHICS impartial Honest
  17. 17. • Being Political  Identify opposants. Why? How?  Write agreements + report (audit trails)  Speak directly & truthfully  Clarify rumors  Solid rationale decisions
  18. 18. • Technical  Right Technological Skill  adequate resource
  19. 19. • Legal
  20. 20. Thankyou

×