This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

View e-Privacy Directive Documents

You have declined cookies. This decision can be reversed.

You have allowed cookies to be placed on your computer. This decision can be reversed.


sdPP Element Description

Scrum is an agile method of software development. Rather than a full process or methodology, is a framework. So instead of providing a complete and detailed description of how everything has to be done in the project, many parts are left in the hands of the software development team. This is done because the team will know the best way to solve the problem faced. This is the reason why, for example, a sprint planning meeting is described in terms of desired outcomes (a commitment to the number of features to be developed in the next sprint) rather than a set of entry criteria, task definitions, validation criteria, and exit criteria (ETVX) as presented in most methodologies.

Scrum is based on self-organization with MFD. In the scrum team there is a team leader in general that decides which person will do the task or how a problem is solved. These are issues that are decided by the team as a whole.

These agile development teams rely on two individuals: Scrum Master and Product Owner. The Scrum Master can be considered as a coach for the team, helping team members to use the Scrum framework to perform at their highest level. The product owner represents the business, customers or users and guides the team to build the right product.

Scrum projects moving in a series of sprints, which are fixed length iterations of not more than one month. At the start of a sprint, the team members are committed to producing a number of features that are listed in the Product Backlog. At the end of the sprint, these functions are carried out - are coded, tested and integrated into the evolving product or system. At the end of the sprint a review takes place during which the team demonstrates the new functionality to the product owner and other interested parties to provide information that could influence the next sprint.

In the sdPP Model the description is a textual field that provides a short explanation of its use and application, as well as the methodology, reference framework or best practices the sdPP came from.
Copyright © 2017 Diego Martín. All Rights Reserved.