Introduction

Scrum is a popular framework widely used in IT project management. At the latest Solvro Talk, Piotr Malatyński from Intel talked about the challenges of managing a team in international projects and the best practices that can be introduced into student projects. As an example, he cited the application project for Juwenalia, currently being implemented by Solvro.

Basic Work Methods in Scrum

Scrum is based on an iterative approach to project implementation, divided into short work periods called sprints (usually 1-4 weeks). Each sprint ends with the delivery of a functioning, valuable product fragment. Key elements of Scrum include:

https://www.scrum.org/resources/what-scrum-module

1. Sprints – cyclical iterations of work on a specified range of tasks from the backlog.

2. Product Backlog – a dynamic list of requirements created and prioritized by the product owner.

3. Daily Stand-ups – daily, short team meetings where progress, plans for the next day, and any obstacles affecting team members are discussed.

4. Sprint Review – a meeting summarizing the sprint, used to present results and gather feedback from stakeholders.

5. Sprint Retrospective – an analysis of the team's work in the completed sprint aimed at continuous improvement of collaboration.

Key Roles in Scrum

1. Product Owner (PO)

• Responsible for the product vision and its backlog.

• Sets task priorities.

• Maintains contact with stakeholders and ensures clear communication between the client and the team.

2. Scrum Master (SM)

• Ensures proper application of Scrum principles and eliminates obstacles affecting the team's work.

• Acts as a mentor, supporting the team in independently solving problems.

• Organizes Scrum meetings and promotes a culture of continuous improvement.

3. Development Team

• Consists of interdisciplinary specialists responsible for delivering functional product elements in each sprint.

• Self-organizes by planning and executing tasks according to the sprint backlog.

https://www.scrum.org/resources/what-scrum-module

Implementing Scrum in Large Teams

Implementing Scrum in large teams requires dividing into smaller groups (string teams) that execute sprints based on a common backlog. A coordinator, such as a Chief Scrum Master, synchronizes actions and ensures the consistency of processes. Each team conducts its own Scrum ceremonies, and tools like Jira or Asana support transparency, work organization, and progress management. Despite increased complexity, this approach allows effectively carrying out complex projects while maintaining Agile principles.

Summary

Scrum offers many advantages, such as fast response to changing requirements, process transparency, and regular delivery of valuable product fragments. Its iterative approach fosters effective communication, and team self-organization promotes engagement and creativity. As a result, Scrum is especially effective in dynamic IT environments, enabling better utilization of team skills and adaptation to changes that are part of this dynamic environment.

Scrum has limitations, such as reliance on people and maintaining certain discipline. However, the lack of appropriate roles, like Product Owner or Scrum Master, can lead to issues with project vision realization.