INTRODUCTION
SCRUM is an agile methodology that emerges as an alternative to the traditional ones. Agile methodologies propose a framework for project management more pragmatic and less bureaucratic. Emerged in the mid-80's in Japan, based on the premise that the value added is in the people and especially the ability to self-organization of people.
Following are the assumptions on which it is based SCRUM, called "Agile Manifesto":
Value more individuals and their interaction with the processes and tools.
Rate the product that works more than full documentation.
Value more collaboration with the customer contract negotiation.
Rate change response more than following a plan.
The word means the same as SCRUM in rugby, that is, the sport adopts a figure of play in which a team has to act very coordinated and constant force to achieve the ball. To the extent that you learn and practice this approach is taking the word meaning.
In short what is SCRUM proposes a framework, a simple and clear way with a series of artifacts, roles and rituals that allow foot traffic based on iterations inspect and adapt based on where each time one ends must have reached a product itself has ROI for the customer.
ROLES
Scrum Master: This is run by an individual, he is responsible for providing everything you need to meet project goals. Its fundamental role is to enforce the methodology.
Product Owner: It is also run by one person, it is usually someone who knows well what is the ROI of each of the requirements that the project has. That is, should know very well the product to be obtained.
Team: The team, who comprise it will implement the project. It is recommended that no less than 5 members nor more than 9.
PROJECT LIFE CYCLE
The life cycle of a Scrum project is based on repeating units must have a fixed time in which plans, develops and approves the result of that iteration. These repeating units are called sprints. It is suggested that Sprint has a minimum duration of one week and a maximum of four.
RITUALS
They are called rituals established SCRUM meetings that must be met in this methodology.
Sprint Planning: When starting a new Sprint should take the list of requirements (Product Backlog) and from the priority of each one should select a set of these requirements which will be executed by the Team. This subset of requirements have to create value for customer ROI and should be a potentially shippable product. The meeting involved the SM, PO and Team. The maximum duration is 2 hours.
Sprint Meeting Daily: Daily Team must conduct a meeting where each member has 2 minutes to answer the following questions:
What tasks performed involved?
What impediments detected when performing these tasks?
What tasks is committed to making tomorrow?
This meeting should involve the Team and MS. It can be done at any time of day, that is defined by the Team, once defined should not be modified.
Sprint Review: At the end of a Sprint should conduct a review of the product designed in that Sprint. This should meet the Team, the PO and MS. This meeting should result in an approval or disapproval of the product by the customer. We recommend a maximum of 2 hours.
Sprint Retrospective: After making the Sprint Review should make another meeting between the SM and the Team. The purpose of this analysis is to see how they applied the methodology and to evaluate the outcome where it should take into account the corrections to be applied for the next iteration.
APPLIANCES
Product Backlog: A list of requirements that define the product the customer needs. Each requirement is called the Product Backlog Item.
Product Backlog Engaged: A subset of the ItemProductBacklog who are committed to a particular Sprint.
Charts: Scrum proposes a series of reports and graphs that let you make project indicators, some of them are:
REFERENCES
