Overview of Scrum Method

Overview of Scrum Method

Scrum is an agile technique that emphasizes openness, close process monitoring, and adaptation. This approach is utilized in the creation of products. Ken Schwaber and Jeff Sutherland co-founded scrum in the early 1990s. The name 'scrum' comes from the sport of rugby.

The goal of establishing a scrum is to achieve high performance within a small team, with everyone working on a specific task and delivering excellent outcomes. The project process has been split down into sprints to keep this principle in mind. Sprints can last anywhere from a week to months, depending on the intricacy. Forecast, To-Do, In-Progress, and Done are the four sections of a sprint log. 

Roles of Scrum Method

The Team

This is the self-improvement group that works together and in a structured manner. It is the core, foundation, and essential team that works in an organized manner and contributes to the development of a product

The Scrum Master

The scrum master is a team facilitator who is knowledgeable about agile approaches and follows the principles. The scrum master is in charge of information cooperation among the project team's many divisions. The scrum master will swiftly bring in any changes in the project stage. The scrum master will be in charge of ensuring high yield and that everything falls into place according to the scrum values and principles. 

Product owner

The scrum product owner serves as a focal point for the agile development project's scrum team. He will ensure that the team's aim is elevated and that they are able to work in sprints. He is also the team's motivator toward a common objective. His vision will be to successfully communicate to the team what they are capable of doing at their best. The product owner might come from any industry, such as marketing or product management, and must be familiar with market and project trends. To operate cross-functionally in the organization, he should be business aware and have excellent communication skills. 


Events of Scrum Method

Sprint Planning

It's the sprint's debut event. The team is engaged in the backlog work that should be completed during sprints. The Team chooses what to work on for the next few months. A Scrum Master, the developer's team, and the product owner make up the team. On the first day of the sprint, this planning step takes place. The next fresh sprint begins only once the preceding sprint's evaluation and retrospection has been completed. New sprint planning is being evaluated based on the previous sprint debate. The objectives are determined using the scope questionnaire, and a delivery strategy is devised appropriately.

Daily Scrum

Every day of the Sprint, the Scrum team meets for 15 minutes to review progress and select what to concentrate on for the next 24 hours. Every day, the daily scrum is held in sprints. The goal is to construct a planned work so that we can comprehend what is going on right now, as well as how and when we can achieve our goal. This also contributes to good team communication.

Sprint Review

The development team presents to the product owner at this point. The team discusses what was accomplished and adjusts the Backlog as appropriate. They present the "completed" job. The sprint has come to an end. The sprint review meeting should last no more than one hour per week at this level.

Sprint Retrospective

The scrum master leads the sprint retrospective segment of the meeting, which takes place after the sprint review. The team talks about what went well, what didn't, and how they can improve in the next sprint. This implies it looks back on previous experiences and suggests methods to improve. It allows the team to provide feedback to the management on the project's progress. This results in a strategy for the next sprint's improvement.

Artifacts in Scrum Method

Product backlog

The scrum team's detailed document is the product backlog. It is to the final document that any information about the product is referenced. The PO owns this, and he utilizes it to convey the most important criteria for any sprint that needs to be completed.

Few rules should be included in the product backlog for ease of use:

  • Priorities should be included in the product backlog. This makes it easier to deliver on time.
  • The product backlog should not include any detailed statements; it is merely a list of requirements.
  • The product backlog must be dynamic, changing as the requirement progresses into more detailed work. The document is updated as requirements change, and a new requirements section is added.

Sprint backlog

In the sprint backlog, there are two key elements to remember.

  • Group decision-making: Each state should be determined and grouped by the entire team.
  • Organize job: The Scrum team should not require the Scrum master's given assignment. They can choose and work on projects since they are self-organized. 

Increases in Product Quality

In general, product increments are the sum of all product backlog commitments made during a sprint. In most cases, this is a piece of software that collaborates throughout the corporation to provide transparency. This might take the form of task boards or charts as well. 

Advantages of Scrum 

  • Scrum may assist teams in completing project deliverables in a timely and effective manner.

  • Scrum ensures that time and money are spent wisely.

  • Large projects are broken down into smaller, more manageable sprints.

  • During the sprint review, software is programmed and tested. This works effectively for fast-paced development projects.

  • Scrum meetings provide the team with clear visibility.

  • Because Scrum is agile, it incorporates feedback from consumers and stakeholders.

  • Short sprints make it much easier to make adjustments based on feedback.

  • During daily scrum meetings, each team member's unique contribution is evident. 

Disadvantages of Scrum 

  • Due to the lack of a defined end date in Scrum, scope creep is common.

  • If they aren't dedicated or cooperative, there's a good probability the project will fail.

  • Adopting the Scrum framework in a big team might be difficult.

  • Only experienced team members can make the framework operate.

  • Team members might become irritated by daily meetings.

  • When a team member departs in the middle of a project, it can have a significant negative impact.

  • Quality is difficult to achieve unless the team goes through a rigorous testing procedure.


Author: Thilini