Scrum is one of the project management methods created to increase the success rate of complex software projects. Scrum is a short meeting where team members come together to talk about where they are in complex and difficult software processes, what the next steps are, and what challenges they may face in the future.
Considering that it would be difficult to execute all phases in a planned manner, a method based on repetition is followed in short intervals, in small pieces, in order to reduce this complex order. In this way, each part can be examined individually and necessary changes can be made immediately, and errors can be easily detected.
It has a flexible structure and teamwork is extremely important in Scrum. Scrum is one of the Agile project management methods. It is based on 3 basic principles: transparency, control and adaptation. Scrum is based on values such as commitment, courage, focus, openness and respect.
All types of teams use Scrum, including software development, engineering, human resources, marketing and design. However, Scrum is more common among software development and engineering teams.
Scrum Artifacts
Scrum teams provide planning information to teams with tools called Scrum artifacts to solve problems and manage projects.
Product Backlog – An ordered list of possible changes to the product that are necessary to improve the product.
Sprint Backlog – A Sprint backlog is a list of tasks in the current Sprint cycle that need to be completed by the development team.
Product Part – The final product of the Sprint. It is the sum of the Product Backlog items completed during a Sprint and the values of all past Sprints.
What are the Roles in a Scrum Team?
The Scrum team is the basic unit of Scrum. There are three main roles in the Scrum team: Product Owner, Scrum Master and developers. Scrum teams are self-managed.
Product Owner: Product Owner is the person who maximizes the value of the product created by the Scrum team, thinks about how to do this, decides what kind of product will emerge at the end of the work and what features this product will have. In short, it determines the value of the product and manages the product backlog, which includes all the needs that the product needs and will need in the future.
The roles and responsibilities of the Product Owner are as follows:
- Clearly define the product target,
- Clearly identify the characteristics of the product,
- Create the work list and identify items,
- To follow the work list,
- Ensuring that the value of work is constantly increasing
Scrum Master: The Scrum Master is the person responsible for setting up Scrum as defined in the Scrum manual and following up to deliver things on time. The Scrum Master is also responsible for:
- Organizing the activities of the Scrum team,
- Ensuring that activities are completed on time,
- Ensuring that barriers to Scrum team progress are removed,
- Lead, train and coach the organization in Scrum adoption,
- Planning Scrum implementations,
- Ensure that Scrum values such as courage, focus, commitment, respect and openness are upheld
Developer Team: Developers take on the work specified by the Product Owner for a product or product feature during Sprints and perform it until the end of the Sprint. The responsibilities of the developers are:
- Creating a plan for the Sprint list,
- Completing the sprint on time,
- Adapt your plans to the Sprint goal
Scrum Events
Sprint
Sprints are inclusive for all other activities. Sprints are time periods of one month or less that mark the completion of a task. Once a Sprint is completed, a new Sprint begins.
It covers all other work such as Sprint planning, daily Scrums, Sprint review and Sprint retrospective. Sprint durations usually vary over 2 or 4 weeks. When this time is longer, there may be complexity and risks may increase. Therefore, shorter Sprints are used to reduce cost and eliminate risks.
Sprint Planning
Sprint planning is the events that determine the work to be done for the Sprint, describe how the work will be accomplished, and start the Sprint. What can be done with the Sprint is discussed by the Product Owner, the development team and the Scrum Master. Tasks are broken down into small pieces by the development team.
Daily Scrum
The Daily Scrum is a communication meeting lasting up to 15 minutes in which each team member tells what stage they are in. The purpose of the Daily Scrum is to review progress towards the Sprint goal and where we are on the backlog.
It is usually held every day, at the same time and place. Because it is held every day, it improves communication, reduces risks and eliminates long meetings.
Sprint Review
A Sprint review is an evaluation at the end of each Sprint, which is a review of the Sprints. The purpose of the Sprint review is to examine the outcome of the Sprint and correct any errors.
Sprint Retrospective
A Sprint Retrospective is a meeting to evaluate how the last Sprint went, what went well during the Sprint, what problems were encountered and how these problems were solved. In other words, its purpose is to plan ways to improve quality. These meetings are attended by the development team and the Scrum Master.
What are the Benefits of Scrum Implementation?
The Scrum approach usually provides many benefits. To realize the benefits of Scrum, Scrum team members must perform their tasks properly. So what exactly are the benefits of using Scrum?
- High quality: Since the Scrum method involves testing and version control, bugs are detected early and eliminated. The earlier this testing starts, the easier it is to find and fix problems. This results in a high quality and stable product.
- Lower costs: With the implementation of the Scrum method, productivity increases and the cost of the project is reduced to the same extent as unwanted problems will not grow.
- Less risk: One of the benefits of Scrum is the reduction of risk. Scrum offers the opportunity to reduce risks with features such as coordinated teams, flexibility against changes and continuous feedback.
- Fast adaptation to change: An important benefit of Scrum is its ability to respond quickly to change.
- Team cohesion: In Scrum, teams work in a coordinated manner.
- Productive Scrum teams: Scrum involves self-managing and self-organizing teams. It increases the overall motivation of teams by creating an environment of support and trust.
- On-time delivery: Well-defined Sprints ensure that the steps are followed accurately. This helps deliver the product on time, without delays.
Scrum Training
Trainings attended by Scrum and Agile users are called Scrum trainings. Scrum trainings are divided according to their levels. There are a wide variety of books, online Scrum courses and videos about Scrum. There are also organizations that provide Scrum certification. In the training, topics such as Scrum team, Product Backlog, Sprint and Sprint planning, Scrum roles, Scrum meetings are mentioned.
References:
https://www.scrum.org/
https://tr.wikipedia.org/wiki/Scrum
