Resource Allocation In Software Project ManagementSyed Hassan Ali
Resource Allocation In Software Project Management
what is Resource Allocation In Software Project Management
define Resource Allocation In Software Project Management
how to allocate resource in software project management
This lecture provides short and comprehensive view of software project and risk management. It has basic examples and calculations which is main concern of software project manager. This lecture helps to understand basics of risk management.
Software Project Management: Risk ManagementMinhas Kamal
Software Project Management: ResearchColab- Risk Management (Document-7)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Resource Allocation In Software Project ManagementSyed Hassan Ali
Resource Allocation In Software Project Management
what is Resource Allocation In Software Project Management
define Resource Allocation In Software Project Management
how to allocate resource in software project management
This lecture provides short and comprehensive view of software project and risk management. It has basic examples and calculations which is main concern of software project manager. This lecture helps to understand basics of risk management.
Software Project Management: Risk ManagementMinhas Kamal
Software Project Management: ResearchColab- Risk Management (Document-7)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Excited to share my presentation on Lesson 03 - "Doing the Work" for PMI Authorized PMP Exam Preparation! 📊🌐
In this session, I'll delve into the core aspects of effective project management, aligning your skills with PMI's renowned PMP certification. We'll explore the art of translating theory into practical action, delivering tangible results in complex projects. Join me in unraveling the secrets to success in the PMP exam journey! 💡🚀
#PMPExam #ProjectManagement #PMP #PMI #Certification #ProfessionalGrowth
Risk Mitigation, Monitoring and Management Plan (RMMM)Navjyotsinh Jadeja
Software Risk is an expectation of loss, a potential problem that may or may not occur in the future. It is generally caused due to lack of information, control or time.
RISK – Possible loss or problem (Specifically in S/W development process)
MITIGATION – Efforts or Process to overcome the Risks or reduce the impact. (Comes after Avoidance Scenario)
MONITORING – Check to ensure effective execution (Observation)
MANAGEMENT – The subtle are of dealing with the risk and keep moving forward
Project Risk Register is one of the key elements of a project. Risk Register is a critical tool that is being used throughout the project. A Risk Register records all project risks, probability, impact, owner, initial responses and recorded date.
Excited to share my presentation on Lesson 03 - "Doing the Work" for PMI Authorized PMP Exam Preparation! 📊🌐
In this session, I'll delve into the core aspects of effective project management, aligning your skills with PMI's renowned PMP certification. We'll explore the art of translating theory into practical action, delivering tangible results in complex projects. Join me in unraveling the secrets to success in the PMP exam journey! 💡🚀
#PMPExam #ProjectManagement #PMP #PMI #Certification #ProfessionalGrowth
Risk Mitigation, Monitoring and Management Plan (RMMM)Navjyotsinh Jadeja
Software Risk is an expectation of loss, a potential problem that may or may not occur in the future. It is generally caused due to lack of information, control or time.
RISK – Possible loss or problem (Specifically in S/W development process)
MITIGATION – Efforts or Process to overcome the Risks or reduce the impact. (Comes after Avoidance Scenario)
MONITORING – Check to ensure effective execution (Observation)
MANAGEMENT – The subtle are of dealing with the risk and keep moving forward
Project Risk Register is one of the key elements of a project. Risk Register is a critical tool that is being used throughout the project. A Risk Register records all project risks, probability, impact, owner, initial responses and recorded date.
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
Computer information project planning is one of the most important activities in the modern software
development process. Without an objective and realistic plan of software project, the development of
software process cannot be managed effectively. This research will identify general measures for the
specific goals and its specific practices of Project Planning Process Area in Capability Maturity Model
Integration (CMMI). CMMI is developed in USA by Software Engineering Institute (SEI) in Carnegie
Mellon University. CMMI is a framework for assessment and improvement of computer information
systems. The procedure we used to determine the measures is to apply the Goal Questions Metrics (GQM)
approach to the three specific goals and its fourteen specific practices of Project Planning Process Area in
CMMI.
A novel risk management model in the Scrum and extreme programming hybrid me...IJECEIAES
Risk management in software development has always been one of the necessities of software project management. The logical nature of software projects and products has caused several challenges and risks in these projects. On the other hand, with the emergence of agile methodologies, especially Scrum, and extreme programming (XP) methodologies, in recent years, this issue has become more serious. This is mainly because emphasizing limited documentation in these methodologies has caused these methods to pay little attention to some aspects of project management, particularly risk management. Concentrating on this challenge, the current study has proposed a risk management model in the hybrid methodology, combining Scrum and XP. Using this model in a case study shows this model's success in achieving risk management purposes. The results of this study indicate an appropriate reduction in the number of reworks, change requests, identified risks, and occurred risks. Moreover, the number of eliminated risks and team productivity have increased.
“Scrumbear” framework for solving traditional scrum model problemsjournalBEEI
Software engineering is a discipline that is little understood by people. It defines how software is developed and maintained to meet the clients’ requirements. Software engineers follow certain systems and standards in their work to meet the clients’ desires. It is on this background that engineers follow specific models in coming up with the final product. One of the models highly used is scrum, which is one of the agile methodologies. However, despite being highly used, it has inherent flaws that need to be corrected. Those flaws are product owner continues changing; do not accept changes in working scrum, sprint’s release time limitation, finally wasting team time within each sprint. This paper presents a new framework, which is an updated version of the current Scrum, to overcome the scum models mentioned issues. In this study, a new framework is presented in a way that is understandable and needed by software developer’s team upon the collected qualitative and quantitative data. The implementation was by making some changes to the current scrum model leading to the “Scrumbear”, certain flaws can be corrected. One of the presented changes involve adding the control master rule to ensure controlling the requirements changing.
Similar to Lecture 03 Software Risk Management (20)
Materi webinar yang diselenggarakan oleh PHP Indonesia secara live di Facebook PHP-ID. Topik yang dibahas mengenai Machine Learning dengan PHP, baik sisi konsep maupun implementasinya.
Webinar Data Mining dengan Rapidminer | Universitas Budi LuhurAchmad Solichin
Materi Webinar Data Mining dengan Rapidminer di Universitas Budi Luhur yang diselenggarakan oleh mahasiswa S2 Ilmu Komputer Universitas Budi Luhur pada hari Jumat, 8 Januari 2021
TREN DAN IDE RISET BIDANG DATA MINING TERBARUAchmad Solichin
Presentasi ini menyajikan Tren dan Ide Riset Bidang DATA MINING Tahun ini. Wajib disimak! Disertai juga puluhan Contoh Paper Penelitian Terkini di bidang Data Mining. Saya menjelaskan banyak ide penelitian untuk skripsi, tesis, disertasi, dll. Simak sampe akhir ya.
Materi Seminar: Artificial Intelligence dengan PHPAchmad Solichin
Materi Seminar: Artificial Intelligence dengan PHP ini disampaikan pada Seminar online yang diselenggarakan oleh Lab ICT Universitas Budi Luhur pada hari Rabu, 12 Agustus 2020
Slide ini menjelaskan mengenai konsep dan langkah-langkah Algoritma Depth First Search (BFS) pada Graph.
Slide disusun oleh Achmad Solichin (http://achmatim.net)
Slide ini menjelaskan mengenai konsep dan langkah-langkah Algoritma Breadth First Search (BFS) pada Graph.
Slide disusun oleh Achmad Solichin | http://achmatim.net
Materi seminar ini menjelaskan mengenai konsep dasar computer vision dan aplikasinya di era Industri 4.0. Materi seminar ini disampaikan pada acara Seminar Tahunan IT yang diselenggarakan oleh Lab ICT Universitas Budi Luhur
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
Embracing GenAI - A Strategic ImperativePeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
Biological screening of herbal drugs: Introduction and Need for
Phyto-Pharmacological Screening, New Strategies for evaluating
Natural Products, In vitro evaluation techniques for Antioxidants, Antimicrobial and Anticancer drugs. In vivo evaluation techniques
for Anti-inflammatory, Antiulcer, Anticancer, Wound healing, Antidiabetic, Hepatoprotective, Cardio protective, Diuretics and
Antifertility, Toxicity studies as per OECD guidelines
Francesca Gottschalk - How can education support child empowerment.pptxEduSkills OECD
Francesca Gottschalk from the OECD’s Centre for Educational Research and Innovation presents at the Ask an Expert Webinar: How can education support child empowerment?
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
Synthetic Fiber Construction in lab .pptxPavel ( NSTU)
Synthetic fiber production is a fascinating and complex field that blends chemistry, engineering, and environmental science. By understanding these aspects, students can gain a comprehensive view of synthetic fiber production, its impact on society and the environment, and the potential for future innovations. Synthetic fibers play a crucial role in modern society, impacting various aspects of daily life, industry, and the environment. ynthetic fibers are integral to modern life, offering a range of benefits from cost-effectiveness and versatility to innovative applications and performance characteristics. While they pose environmental challenges, ongoing research and development aim to create more sustainable and eco-friendly alternatives. Understanding the importance of synthetic fibers helps in appreciating their role in the economy, industry, and daily life, while also emphasizing the need for sustainable practices and innovation.
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...Levi Shapiro
Letter from the Congress of the United States regarding Anti-Semitism sent June 3rd to MIT President Sally Kornbluth, MIT Corp Chair, Mark Gorenberg
Dear Dr. Kornbluth and Mr. Gorenberg,
The US House of Representatives is deeply concerned by ongoing and pervasive acts of antisemitic
harassment and intimidation at the Massachusetts Institute of Technology (MIT). Failing to act decisively to ensure a safe learning environment for all students would be a grave dereliction of your responsibilities as President of MIT and Chair of the MIT Corporation.
This Congress will not stand idly by and allow an environment hostile to Jewish students to persist. The House believes that your institution is in violation of Title VI of the Civil Rights Act, and the inability or
unwillingness to rectify this violation through action requires accountability.
Postsecondary education is a unique opportunity for students to learn and have their ideas and beliefs challenged. However, universities receiving hundreds of millions of federal funds annually have denied
students that opportunity and have been hijacked to become venues for the promotion of terrorism, antisemitic harassment and intimidation, unlawful encampments, and in some cases, assaults and riots.
The House of Representatives will not countenance the use of federal funds to indoctrinate students into hateful, antisemitic, anti-American supporters of terrorism. Investigations into campus antisemitism by the Committee on Education and the Workforce and the Committee on Ways and Means have been expanded into a Congress-wide probe across all relevant jurisdictions to address this national crisis. The undersigned Committees will conduct oversight into the use of federal funds at MIT and its learning environment under authorities granted to each Committee.
• The Committee on Education and the Workforce has been investigating your institution since December 7, 2023. The Committee has broad jurisdiction over postsecondary education, including its compliance with Title VI of the Civil Rights Act, campus safety concerns over disruptions to the learning environment, and the awarding of federal student aid under the Higher Education Act.
• The Committee on Oversight and Accountability is investigating the sources of funding and other support flowing to groups espousing pro-Hamas propaganda and engaged in antisemitic harassment and intimidation of students. The Committee on Oversight and Accountability is the principal oversight committee of the US House of Representatives and has broad authority to investigate “any matter” at “any time” under House Rule X.
• The Committee on Ways and Means has been investigating several universities since November 15, 2023, when the Committee held a hearing entitled From Ivory Towers to Dark Corners: Investigating the Nexus Between Antisemitism, Tax-Exempt Universities, and Terror Financing. The Committee followed the hearing with letters to those institutions on January 10, 202
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
Unit 8 - Information and Communication Technology (Paper I).pdf
Lecture 03 Software Risk Management
1. Software Risk Management
Matakuliah Rekayasa Perangkat Lunak (CS215) – Gasal 2015/2016
Magister Ilmu Komputer - Universitas Budi Luhur
Achmad Solichin, S.Kom, M.T.I (achmatim@gmail.com)
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
2. A Small Case Study
Lintang adalah seorang freelancer yang tinggal diTangerang. Sebagai web developer, Lintang sudah 4
tahun berpengalaman membangun berbagai aplikasi berbasis web. Saat ini, Lintang juga sedang
terikat kontrak maintenance sebuah sistem HRIS berbasis web di perusahaan XYZ selama setahun
mendatang. Selain itu, Lintang juga sedang melanjutkan studi di Magister Ilmu Komputer, Universitas
Budi Luhur (semester 3).
Suatu hari, seorang kenalan bernama Mulyanto menawarkan sebuah project untuk membangun
sistem informasi laundry berbasis web. Berdasarkan hasil pertemuan antara Lintang dan Mulyanto,
diperoleh beberapa informasi terkait project yg ditawarkan. Mulyanto memiliki 4 usaha laundry yang
tersebar di sejumlah tempat di Jakarta danTangerang. Sebagai pemilik, Mulyanto ingin mengetahui
dan mengontrol dg cepat bagaimana bisnis laundry dijalankan oleh anak buahnya, melalui sebuah
aplikasi berbasis web. Mulai dari proses penyerahan pakaian oleh pelanggan, proses pengerjaan oleh
pegawai hingga pendapatan untuk setiap pegawai harus tercatat dg baik di aplikasi. Selain
berdasarkan kehadiran, pendapatan masing2 pegawai juga dihitung berdasarkan jumlah pekerjaan
yang dilakukan.
Sebagai seorang lulusan kampus ternama, Mulyanto sudah menyusun rancangan aplikasi yang
diinginkan, mulai dari rancangan layar, rancangan masukan, rumus / perhitungan, rancangan basis data
hingga rancangan laporan. Semua disusun berdasarkan pengalaman Mulyanto menangani bisnis
laundry. Memang, Mulyanto termasuk orang yg sangat perfeksionis dan selektif dlm mengerjakan
sesuatu. Kali ini dia mencari seorang programmer berpengalaman yg sanggup mengimplementasikan
rancangannya menjadi sebuah aplikasi yg dapat langsung digunakan setidaknya 2 bulan mendatang.
Mulyanto menjanjikan kompensasi yang cukup besar untuk pekerjaan ini.
Menurut Anda, Lintang harus menerima atau menolak tawaran project dari Mulyanto? Jelaskan!
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
3. Overview
• What is Software Risk Management?
• Risk Management Process
• Risk Management Strategies
• Risk Metrics (Risk Estimation)
• International Risk Management Standards.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
4. Important Goals of Project Management
• Deliver the software to the customer at the agreed time.
• Keep overall costs within budget.
• Deliver software that meets the customer’s expectations.
• Maintain a happy and well-functioning development team.
[Pressman, 2010]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
5. Project Manager Responsibility
• Project planning. Project managers are responsible for planning, estimating and
scheduling project development, and assigning people to tasks.
• Reporting. Project managers are usually responsible for reporting on the progress
of a project to customers and to the managers of the company developing the
software.
• Risk management. Project managers have to assess the risks that may affect a
project, monitor these risks, and take action when problems arise
• People management. Project managers are responsible for managing a team of
people.
• Proposal writing.The first stage in a software project may involve writing a
proposal to win a contract to carry out an item of work
[Sommerville, 2011]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
6. Risk Management
• Risk management involves anticipating risks that might affect the project
schedule or the quality of the software being developed, and then taking
action to avoid these risks (Hall, 1998; Ould, 1999)
• Three categories of Risk:
• Project risks. Risks that affect the project schedule or resources. Ex: the loss of an
experienced designer.
• Product risks. Risks that affect the quality or performance of the software being
developed. Ex: the failure of a purchased component to perform as expected.
• Business risks. Risks that affect the organization developing or procuring the software.
Ex: a competitor introducing a new product.
[Sommerville, 2011]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
7. Reactive Risk Management
• Project team reacts to risks when they occur.
• Mitigation—plan for additional resources in anticipation of fire fighting
• Fix on failure—resource are found and applied when the risk strikes
• Crisis management—failure does not respond to applied resources and
project is in jeopardy.
[Pressman, 2010]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
8. Proactive Risk Management
• Formal risk analysis is performed.
• Organization corrects the root causes of risk
• TQM (total quality management) concepts and statistical SQA
• Examining risk sources that lie beyond the bounds of the software
• Developing the skill to manage change
[Pressman, 2010]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
9. Principle of Risk Management
• Maintain a global perspective—view software risks within the context of a system in which it is a
component and the business problem that it is intended to solve
• Take a forward-looking view—think about the risks that may arise in the future (e.g., due to
changes in the software); establish contingency plans so that future events are manageable.
• Encourage open communication—if someone states a potential risk, don’t discount it. If a risk is
proposed in an informal manner, consider it. Encourage all stakeholders and users to suggest
risks at any time.
• Integrate—a consideration of risk must be integrated into the software process.
• Emphasize a continuous process—the team must be vigilant throughout the software process,
modifying identified risks as more information is known and adding new ones as better insight is
achieved.
• Develop a shared product vision—if all stakeholders share the same vision of the software, it is
likely that better risk identification and assessment will occur.
• Encourage teamwork—the talents, skills, and knowledge of all stakeholders should be pooled
when risk management activities are conducted.
[Pressman, 2010]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
10. Example of Risks
[Sommerville, 2011]
Risk Affects Description
Staff turnover Project Experienced staff will leave the project before it is finished.
Management change Project There will be a change of organizational management with different
priorities.
Hardware
unavailability
Project Hardware that is essential for the project will not be delivered on schedule.
Requirements change Project and
product
There will be a larger number of changes to the requirements than
anticipated.
Specification delays Project and
product
Specifications of essential interfaces are not available on schedule.
Size underestimate Project and
product
The size of the system has been underestimated.
CASE tool
underperformance
Product CASE tools, which support the project, do not perform as anticipated.
Technology change Business The underlying technology on which the system is built is superseded by
new technology.
Product competition Business A competitive product is marketed before the system is completed.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
11. The Risk Management Process
[Sommerville, 2011]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
12. Risk Identification
[Sommerville, 2011]
• May be a team activities or based on the individual project manager’s experience.
• Six types of common risk:
1. Technology risks. Risks that derive from the software or hardware technologies that are
used to develop the system.
2. People risks. Risks that are associated with the people in the development team.
3. Organizational risks. Risks that derive from the organizational environment where the
software is being developed.
4. Tools risks. Risks that derive from the software tools and other support software used to
develop the system.
5. Requirements risks. Risks that derive from changes to the customer requirements and the
process of managing the requirements change.
6. Estimation risks. Risks that derive from the management estimates of the resources
required to build the system.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
13. Risk Identification
[Sommerville, 2011]
Risk type Possible risks
Technology The database used in the system cannot process as many transactions per second as expected. (1)
Reusable software components contain defects that mean they cannot be reused as planned. (2)
People It is impossible to recruit staff with the skills required. (3)
Key staff are ill and unavailable at critical times. (4)
Required training for staff is not available. (5)
Organizational The organization is restructured so that different management are responsible for the project. (6)
Organizational financial problems force reductions in the project budget. (7)
Tools The code generated by software code generation tools is inefficient. (8)
Software tools cannot work together in an integrated way. (9)
Requirements Changes to requirements that require major design rework are proposed. (10)
Customers fail to understand the impact of requirements changes. (11)
Estimation The time required to develop the software is underestimated. (12)
The rate of defect repair is underestimated. (13)
The size of the software is underestimated. (14)
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
14. Risk Analysis
[Sommerville, 2011]
• Assess probability and seriousness of each risk.
• Probability may be:Very Low (< 10%), Low (10-25%), Moderate (25-50%),
High (50-75%) orVery High (> 75%).
• Risk consequences might be: Catastrophic (threaten the survival of the
project), Serious (would cause major delays),Tolerable (delays are within
allowed contingency), or Insignificant.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
15. RiskTypes and Example
[Sommerville, 2011]
Risk Probability Effects
Organizational financial problems force reductions in the project budget (7). Low Catastrophic
It is impossible to recruit staff with the skills required for the project (3). High Catastrophic
Key staff are ill at critical times in the project (4). Moderate Serious
Faults in reusable software components have to be repaired before these
components are reused. (2).
Moderate Serious
Changes to requirements that require major design rework are proposed
(10).
Moderate Serious
The organization is restructured so that different management are
responsible for the project (6).
High Serious
The database used in the system cannot process as many transactions per
second as expected (1).
Moderate Serious
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
16. RiskTypes and Example
[Sommerville, 2011]
Risk Probability Effects
The time required to develop the software is underestimated (12). High Serious
Software tools cannot be integrated (9). High Tolerable
Customers fail to understand the impact of requirements changes (11). Moderate Tolerable
Required training for staff is not available (5). Moderate Tolerable
The rate of defect repair is underestimated (13). Moderate Tolerable
The size of the software is underestimated (14). High Tolerable
Code generated by code generation tools is inefficient (8). Moderate Insignificant
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
17. Risk Projection
[Pressman, 2010]
• Also called Risk Estimation
• Risk Projection steps:
• Establish a scale that reflects the perceived likelihood of a risk.
• Delineate the consequences of the risk.
• Estimate the impact of the risk on the project and the product.
• Assess the overall accuracy of the risk projection so that there will be no
misunderstandings.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
19. Risk Planning
[Sommerville, 2011]
• Consider each risk and develop a strategy to manage that risk.
• Risk strategies:
• Avoidance strategies.The probability that the risk will arise is reduced.
• Minimization strategies.The impact of the risk on the project or product will be
reduced.
• Contingency plans. If the risk arises, contingency plans are plans to deal with that risk.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
20. Risk Management Strategies
[Sommerville, 2011]
Risk Strategy
Organizational financial
problems
Prepare a briefing document for senior management showing how the
project is making a very important contribution to the goals of the business
and presenting reasons why cuts to the project budget would not be cost-
effective.
Recruitment problems Alert customer to potential difficulties and the possibility of delays;
investigate buying-in components.
Staff illness Reorganize team so that there is more overlap of work and people therefore
understand each other’s jobs.
Defective components Replace potentially defective components with bought-in components of
known reliability.
Requirements changes Derive traceability information to assess requirements change impact;
maximize information hiding in the design.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
21. Risk Management Strategies
[Sommerville, 2011]
Risk Strategy
Organizational
restructuring
Prepare a briefing document for senior management showing how the
project is making a very important contribution to the goals of the business.
Database performance Investigate the possibility of buying a higher-performance database.
Underestimated
development time
Investigate buying-in components; investigate use of a program generator.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
22. Risk Monitoring
[Sommerville, 2011]
• Assess each identified risks regularly to decide whether or not it is becoming
less or more probable.
• Also assess whether the effects of the risk have changed.
• Each key risk should be discussed at management progress meetings.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
23. Risk Indicators
[Sommerville, 2011]
Risk type Potential indicators
Technology Late delivery of hardware or support software; many reported technology
problems.
People Poor staff morale; poor relationships amongst team members; high staff
turnover.
Organizational Organizational gossip; lack of action by senior management.
Tools Reluctance by team members to use tools; complaints about CASE tools;
demands for higher-powered workstations.
Requirements Many requirements change requests; customer complaints.
Estimation Failure to meet agreed schedule; failure to clear reported defects.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
25. Risk Exposure (RE)
[Pressman, 2010]
𝑅𝐸 = 𝑃 ∗ 𝐶
Dimana:
• RE = Risk Exposure
• P = Probability of occurrence for a risk
• C = cost to the project should the risk occur
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
26. Risk Exposure (RE)
[Pressman, 2010]
• Risk identification. Only 70 percent of the software components scheduled
for reuse will, in fact, be integrated into the application.The remaining
functionality will have to be custom developed.
• Risk probability. 80 percent (likely).
• Risk impact. Sixty reusable software components were planned. If only 70
percent can be used, 18 components would have to be developed from
scratch (in addition to other custom software that has been scheduled for
development). Since the average component is 100 LOC and local data
indicate that the software engineering cost for each LOC is $14.00, the
overall cost (impact) to develop the components would be 18 x 100 x $14 =
$25,200.
• Risk exposure. RE = 0.80 x $25,200 ≈ $20,200.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
27. Risk Information Sheet (RIS)
[Pressman, 2010]CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
28. International Risk Management Standards
• COSO ERM (2004)
• Applies to management, directors, regulators, academics and others who are
interested in better understanding enterprise risk management
• COSO ERM is a framework providing integrated principles, common terminology and
practical implementation guidance supporting entities' programs to develop or
benchmark their enterprise risk management processes.
• This standard is voluntary.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
29. International Risk Management Standards
• ISO 31000: Risk Management (2009)
• Applies to any public, private or community enterprise, association, group or
individual.Therefore, it is not specific to any industry or sector.
• ISO 31000 provides principles and generic guidelines on risk management.Applies to
any type of risk, whatever its nature, whether having positive or negative
consequences.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
30. International Risk Management Standards
• ISO/IEC 31010: Risk Management – Risk AssessmentTechniques (2009)
• Applies to any public, private or community enterprise, association, group or
individual.Therefore, it is not specific to any industry or sector.
• ISO 31010 assists organizations in implementing the risk management principles and
guidelines provided by the recently published ISO 31000:2009, itself complemented by
ISO Guide 73:2009 on risk management vocabulary.This standard deals with risk
assessment concepts, risk assessment process, and selection of risk assessment
techniques.This standard is not intended for certification, regulatory or contractual
use.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
31. International Risk Management Standards
• ISO/IEC Guide 73: Risk Management Guidelines (2009)
• Applies to those engaged in managing risks, those who are involved in activities of ISO
and IEC, and developers of national or sector-specific standards, guides, procedures
and codes of practice relating to the management of risk
• The guide provides the definitions of generic terms related to risk management. It
aims to encourage a mutual and consistent understanding of, and a coherent approach
to, the description of activities relating to the management of risk, and the use of
uniform risk management terminology in processes and frameworks dealing with the
management of risk.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
32. International Risk Management Standards
• BS 31100 (Risk Management)
• Applies to any organization of any size
• BS 31100 provides a foundation for organizations to understand, create, integrate and
maintain risk management programs by giving recommendations on its model,
framework, and process with the goal of increasing the organizations chances of
meeting its objectives.
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
33. References
• Roger S. Pressman, 2010, Software Engineering: A Practitioner’s Approach
7th edition, McGraw-Hill.
• Ian Sommerville, 2011, Software Engineering 9th edition, Addison-Wesley.
• Other references
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur
34. Thanks
• Achmad Solichin, S.Kom, M.T.I
• achmatim@gmail.com
• Twitter: @achmatim
• Facebook: facebook.com/achmatim
• Web: http://achmatim.net
CS215 – Rekayasa Perangkat Lunak – Magister Ilmu Komputer Universitas Budi Luhur