Roughly one can say that Scrum is an Agile software development focuses on how team members should work (communicate, work, etc. ), to produce a flexible system in a constantly changing environment.
SCRUM's philosophy is to involve, motivate and keep constantly informed about the status of the project to the team and the client.
is a methodology that, to do it, requires a lot of responsibility on the part of the team work. Which consists of a project manager, development team and the client.
Today many companies are adopting this methodology due to its easy implementation and adaptability to change.
is so simple that the most likely (if they have participated in projects at work, university or institute) have tackled a project in a very similar (later publish an "example of how you might implement SCRUM).
below define the roles and concepts of SCRUM.
Roles: Product
- Owner: Understand project priorities brand or product (customer). Scrum
- Master Guide meetings and helps the team to any problems that may arise (Project Manager).
- Scrum Team: They are responsible for implementing the functions or requirements chosen by the Product Owner. Develop the product.
- Stackeholders: People associated with the product or its funding. Participate in the Sprint Review and can provide ideas, suggestions or needs.
- Users: They are the ultimate beneficiaries of the product.
Main activities:
- Product Backlog: Stack requirements or system functions, defined and prioritized by the Product Owner.
- Sprint Backlog: Pile of functionality to develop during an iteration or sprint extracted from the Product Backlog. These developments are advised not to exceed four weeks, thus maintaining control of the project.
- Spring Planning Meeting: Meetings between the Scrum Master, Product Owner and Scrum Team and is planning tasks to be performed in a number of Sprint backlogs. It generates a document stating the objectives of Sprint Sprint called Goal.
- Daily Scrum Meeting: Small meetings between the Scrum Master and Scrum Team, which must not exceed 30 minutes. Performed during the development of Spring Backlog and is to report the status of it, answering the following questions:
- What tasks have you done since the last meeting? (Which I did).
- On what tasks will work on the current day? (I'll do today.)
- What obstacles or risks impede or prevent the normal progression? (What help I need).
- Sprint Review: Meeting of no more than two hours, which reports the progress made in the Sprint the Product Owner and Stackeholders.
- Sprint Retrospective: Activity for reorganizing the work of the Product Backlog. We analyze positive and negative aspects of the Sprint Backlog.
0 comments:
Post a Comment