Table of Contents
Scrum is a framework for software production (of course, it is also used in other fields) which is based on Agile thinking. We examine Scrum, which is one of the most common software development frameworks.
History of Scrum
Scrum was introduced in 1986 by Ikojiro Nonaka and Hirotaka Takeuchi as a new policy for the production of business software that should have flexibility and speed in production. The name scrum is derived from a type of game in rugby football. It means from the word scrummage. This methodology was first invented in Japan.
Scrum approach in projects
Scrum is an incremental method. That is, with the passage of time and the progress of the stages, the evolution of the project will also increase. Scrum consists of different cycles that help to reduce possible risks and excess costs by ensuring the correct implementation of the project in each cycle.
Scrum’s approach in general is that first, a meeting is held with the participation of the development team and the product owner or customer. During this meeting, all system and non-system requirements, objectives and all requirements that must be implemented should be clarified. All members collectively agree. Next, a large project is defined, it is divided into smaller parts. Each part of it is defined as a specific and limited period of time called Sprint.
Each sprint is usually 1 to 2 weeks in consultation with the team members. Of course, it can be more or less and there is no limit. Spirants have a specific duration. That is, they end on a certain date. Whether the work is finished or not. They are never renewed. At the beginning of each sprint, we hold a meeting where we will plan the current sprint. We get together every day and talk about things. After the end of each sprint, we hold a meeting and review the work results and record how things are done and efficiency. After the end of the sprint, we prepare again for the next sprint.
The relationship between Scrum and Agile
Agile thinking has 12 principles that are very useful in the development of software systems. One of the most basic principles of this thinking is continuous communication with the customer. This has made it important to use it in today’s businesses. In this type of thinking, the software team tries to make the final product according to the customers’ opinion. In other words, we will have a customer-oriented product. In each phase, the obtained results are tested and checked. Ajail consists of 4 main stages, namely recognition.
Agile thinking methods, including Scrum, XP, Kanban, etc., are ways to achieve Agile thinking. Agile is a way of thinking about software development.
In fact, Scrum is an Agile software development framework that uses the incremental iteration method.
Is Scrum a framework or a methodology?
People like Ken Schwaber, who is one of the founders of Scrum, constantly use the word framework and emphasize that everyone should accept this, but others use the word process or methodology for Scrum.
Why Scrum is a framework and not a methodology?
Methodology is a set of methods that, in addition to recommending us to do those processes, but Scrum only recommends us to very simple and practical approaches and thoughts.
Scrum is an incremental methodology for managing software projects and is considered one of the agile thinking methodologies.
Scrum leaves most of that to the team, rather than giving precise details about how things should be done on the project. This will be practical because the team will know how to solve their problem in the best way.
In simple words, in Scrum we don’t have a screw version and we mostly try to discover and expose problems.
3 basic principles of the Scrum framework
Scrum has 3 basic principles, which are known for these three important features in software projects:
- Transparency: It means that all the issues that are done in the team can be checked and controlled by all the members of the scrum team.
- Inspection: Various stages of implementation are checked continuously. If any problem occurs, it is quickly resolved so that the team’s speed does not slow down.
- Adaptation: market changes, changing needs, changing company policies and changing technologies used are among the reasons that make the adaptability of Scrum projects important.
Roles in Scrum
- Scrum Master: is responsible for maintaining and maintaining the processes and correct execution of Scrum in the team.
- Product Owner: who is the representative of project and business stakeholders.
- Team Member: Team Development Members: Members of a multi-functional group, usually between 3 and 9 people. These people perform design, analysis, implementation, testing, etc. operations. In fact, developers, designers, and technical team members are the ones who do the executive work.
Sprint planning sessions:
At the beginning of each spirant, a spirant planning meeting is held. The Product Owner and the Scrum Team discuss the goals and action items. The scrum team selects items to complete by the end of the sprint. Of course, in the order of priorities that have been specified
Daily meeting – stand up meeting:
these short meetings of maximum 15 minutes are held at the first working hour of the day between the scrum team members. It is better that these meetings are standing so that you don’t lose too much time. The team members are very quick to describe what they did the previous day, what they are going to do during the current day, and the problems they encountered. By doing this, we find solutions for current problems and things are done better and with less delay.
Spirint Review Meeting:
It is an informal meeting that takes place after the Spirint is over. Sprint Review Meeting The Scrum Team and stakeholders review what they accomplished during the Sprint. They discuss it. In this meeting, the product owner, team members and scrum specialist are present, in addition to customers, stakeholders, experts, managers and anyone else who is interested.
After the sprint review, the team gathers for a sprint retrospective, which is an opportunity for the team to discuss what was or wasn’t done, and agree on changes.
No matter how successful the Scrum team is, there is always room for improvement. The team must define a goal and proceed according to the plan until the end of the sprint. Because of this, the team always finds ways to improve, and we see this reflected in the Sprint Review event.