SW Engineering Process/SCRUM

////SW Engineering Process/SCRUM
SW Engineering Process/SCRUM2018-07-25T14:53:30+00:00

Softeco uses the SCRUM method, an Agile methodology for planning and project management, which uses an adaptive approach, as it tries to emphasize the non-linearity of the projects and aims at managing the specifications changes, during the entire process of software development.

SCRUM focuses on the incremental execution of the activities, to be carried out quickly and with great cohesion among all project participants. Essential in this type of methodology is then the communication, which is made agile during all phases of the project.

One of the assumptions of SCRUM is that, in the course of a project, the customers, for different reasons, may change their minds about what they want. Furthermore, unexpected events cannot be easily managed with traditional methods.

SCRUM adopts an empirical approach, recognizing that a problem cannot be fully understood or defined, so it is best to focus on the ability of the team to quickly deliver working releases, although not complete, and to respond quickly to emerging needs.

SCRUM uses an iterative method which is based on an incremental approach, in order to maximize the predictability and control over risks.

The SCRUM empirical approach is based on three main elements:

  • Transparency: to ensure the visibility of the results and the awareness that the development of the project evolves in the desired direction.
  • Inspection: to ensure control activity, to be implemented with a frequency that can bring out what is in contradiction or outside of acceptable limits.
  • Adaptation: to promote adjustments or changes due to the inspection activity or in order to adapt the development to new needs.

Scrum provides three different types of meetings focused on inspection and adaptation:

  • Daily Scrum, the aim of the meeting is to be able to monitor, on a daily basis, if progress towards the Sprint goal are reasonably adequate
  • Sprint Review and Planning Review, the aim of the meeting is to inspect the progress towards the release goal, in order to decide in advance if it is appropriate to make adjustments to optimize the value of the next Sprint
  • Sprint Retrospective, the aim of the meeting is to review the previous sprint in order to determine which changes have to be made in order to make the next Sprint more productive