What is Scrum?
Scrum is a structure that enables groups to cooperate. Like a rugby team (where it gets its name) training for the big game, Scrum encourages teams to learn through experiences, to organize themselves while working on a problem, and to reflect on their wins and losses to improve continuously. Software development teams use their knowledge more frequently and their principles and lessons can be applied to all types of teamwork. This is one of the reasons why Scrum is so popular
Why Use Scrum?
According to Eric Naiburg, vice president of marketing for Scrum.org, Scrum is best understood as a general approach to problem-solving that avoids specific details and sets of rigid instructions, step by step. As teams, people and projects change and evolve over time, “having a single path to do something does not allow growth,” says Naiburg. Simplifying: the Scrum is the opposite of a list of tasks. Instead, it is a way to approach group projects with flexibility. Although Scrum provides a solid structure for organizing product teams and scheduling work, it is a structure that can be shaped to accommodate the needs of a team, rather than dictate exactly how a team should proceed.
Roles in a scrum
The view of the software that is going to be built is communicated by the Product Owner. The Product Owner does not focus only on the work that is going to be completed but also focuses on the business and market requirements. The PO interacts with the team and with other interested parties to create and manage the backlog. The role of a PO is to motivate the team to align it with the goal and vision of the project.
The Scrum Master is responsible for organizing meetings, facing challenges and bottlenecks. The Scrum Master interacts with the Product Owner to ensure that the product backlog is ready for the next sprint. He is also responsible for ensuring that the team follows the Scrum process.
The Team Scrum can be composed of 5 to 7 members. In a Scrum team, there are no different roles as a programmer, designer or tester, instead, they all have a set of tasks that they complete together. Time Scrum plans the amount of work they can complete in each iteration.
The product backlog is the most important document that describes all the requirements for a system, project or product. The backlog of the product can be considered as a list of tasks consisting of work items, each of which produces a delivery with commercial value. The elements of the backlog are ordered in terms of commercial value by the Product Owner.
A sprint backlog is the specific list of items obtained from the product backlog that must be completed in a sprint.
An increase is the sum of all the backlog elements of the product that have been completed since the last software version. While it is up to the product owner to decide when an increase is released, it is the team’s responsibility to make sure that everything that is included in an increase is ready to be released. This is also called PSI (Potential Shippable Increment).
The Scrum process encourages professionals to work with what they have and continuously evaluate what is working and what is not working.
The Daily Scrum is a short stand-up meeting that takes place in the same place and time every day. At each meeting, the team analyzes the work that was completed the previous day and plans the work that will be done in the next 24 hours. This is the time for team members to talk about any problems that may prevent the project from being completed.
Sprint Planning Meeting
A Sprint refers to the period of time in which the work must be completed and, generally, is 30 days. Everyone participates in the definition of goals and, in the end, at least one increment – usable software – must be produced.
This is the time to show off the increment.
A retrospective of the Sprint is a meeting held after the end of the Sprint. During that meeting, everyone reflects on the Sprint process. Team training exercise can also be offered.