Plan and mitigate the risks of computer projects

1.0 INTRODUCTION

The purpose of the plan: mitigation, monitoring, risk management and identification of many potential dangers?
Analysis to identify and avoid any specific product hazards?
RMMM best plan group jon ion to perform risk mitigation, monitoring, and management in order to produce a quality product.

2.0 PROBLEM RISKS

Organizational Role of Risk Management
Each member of the organization will undertake risk management.
The development will continuously monitor the progress and the project for every possible risk
Risk management falls on each member of the group.

PROBLEM RISKS

Group members willing to use the software process
Numerous backups of the software
Changes in Requirements
Timely delivery of the software
The database is stable
Good Quality Documentation

Dangers affecting the business

Delivery deadline
Negative impact on business by software development
Completion of all conditions and business needs
Build a product that does not fit the business
Build a good product that can not be sold
Pass over the budget set

Dangers of the process

Staff members willing to use the software process after being agreed upon before the work is done

Members do not have a description of the software process that will be used in this project

There may be dangers that can be detected after a good analysis of the development environment

Risks that may occur but their prediction is almost impossible

Technical problems

They threaten the quality and the lifespan of the project

Identify design, implementation, interface, verification and maintenance issues.

Technical problems occur because the problem that has been taken is actually more difficult than it was supposed to be

Technological hazards

The emergence of new technologies is a feasible factor for these risks

The system should provide high scalability with respect to the number of users

The technology used does not meet the expectations

risks                             category		probability	Impakti
Poor evaluation of the project's sizeThe weakness of the project	PP	60%	2
Number of users bigger than forecast	PP	30%	3
With less reuse than the forecast	PP	70%	2
Shortening the time limit	IB	50%	2
			2
			2
Lack of training in the tools used	MZ	80%	3
Staff without a try	PS	30%	2

Facilitation, monitoring and risk management

3.1 Risk mitigation risk m

The result of non-delivery of the product over time

The cost will be high if a late delivery occurs

3.2 Risk monitoring m

Changes to be made to the product should be taken seriously

Schedules will be monitored more carefully during the development phase

3.3 Risk Management m

If a previously used method did not prove effective it would have to be sought for other methods

It would be required to extend the deadline for submission

The team would have meetings to add new topics or remove unnecessary topics from the documentation