Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011)

Lack of top management commitment

Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management.

Failure to gain user commitment

In Scrum, the team constantly show working software to the users, which increase the commitment and feedback.

Misunderstanding the requirements

Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements.

Lack of adequate user involvement

Constantly working software makes the users more involve in the process.

Lack of required knowledge/skills in the project personnel

In Scrum, the teams are cross-functional and responsible for all the task. This generate knowledge transference, increasing the skills of the project personnel.

Lack of frozen requirement

Scrum freezes the requirements in each sprint, this give the stability needed every iteration.

Changing scope – objectives

Scrum knows about this and embraces change. The key is in prioritization of the objectives. The team develop first the functionalities that gives more value to the clients.

Introduction of new technology

The introduction of new technology is well handled in Scrum, it is allowed only when it will increase the value for the clients.

Failure to manage end user expectations

The user is satisfied through working software, transparency and the delivery of value in each iteration.

Insufficient or inappropriate staffing

Scrum propose a cross-functional team compose by 5 to 9 full time people committed to the project. This warranty appropriate staffing for the project.