Managing a project so that all team members know what they should be working on, can respond to changes, and can gradually achieve the set objectives is not always easy. This is especially true for projects whose requirements change during the work and where it is not possible to plan everything precisely in advance. This is why we increasingly encounter agile approaches in modern project management, which make it possible to continuously plan, evaluate, and adapt work to the current situation. One of the best-known approaches is Scrum.
What is Scrum?
Scrum is a framework for managing complex work that enables teams to create valuable results incrementally and respond to new information and changes. In contrast to traditional project management, where the entire project is often planned in advance and then followed according to a fixed plan, Scrum works in shorter periods called Sprints. During each Sprint, the team works on selected tasks and should have a usable result at the end. The team then evaluates what worked, what needs to be changed, and what should be addressed in the next Sprint.
Scrum = short work cycles + continuous evaluation of results + team collaboration + the ability to respond to changes.
Scrum is not simply a tool for meetings and planning. It is a way of organizing work based on transparency, inspection, and adaptation.
How does Scrum methodology work?
The basis is a series of repeated work cycles called Sprints.
A Sprint is a time-boxed period, for example, two weeks. At the beginning, the team sets a goal and selects the tasks it wants to work on. During the Sprint, team members collaborate and monitor progress. At the end, they present the result and reflect on the work.
Scrum in practice step by step
- Creating a list of requirements – Requirements and tasks are entered into the Product Backlog.
- Planning the Sprint – The team selects the tasks it will focus on during the upcoming Sprint.
- Working on the tasks – Team members work together to achieve the Sprint goal.
- Continuous monitoring – The team regularly checks progress and addresses any obstacles.
- Presenting the results – At the end of the Sprint, the team presents what has been completed.
- Evaluating collaboration – The team reflects on what worked well and what could be improved.
- Starting the next Sprint – Based on the results and new information, the team plans the next cycle.
The team does not try to predict everything in advance. Instead, it receives new information during the project and adjusts its approach accordingly.
What are the basic principles of Scrum?
W orking in short cycles
Instead of planning all activities months in advance, work is divided into shorter cycles. This makes it easier to monitor progress and respond to new circumstances.
Continuous evaluation of results
The team regularly checks what has been completed and whether the result meets the expected requirements. Problems can therefore be identified earlier instead of only at the end of the project.
Adapting to changes
Customer, market, or project requirements can change during the work. The team therefore continuously evaluates new information and adjusts its next steps accordingly.
Collaboration
Open communication and cooperation between team members are an important part of the work. Sharing information helps prevent misunderstandings, solve problems more quickly, and find the most suitable solutions together.
Self-organization
Team members have greater responsibility for organizing their own work and deciding how best to achieve the agreed goal.
Scrum roles: Who has which role in the team?
There are three main roles, or more precisely accountabilities, within Scrum:
- Product Owner
- Scrum Master
- Developers
The Product Owner is responsible for maximizing the value of the product. One of their key responsibilities is managing the Product Backlog, including prioritizing individual requirements and tasks.
The Scrum Master helps the team use Scrum correctly and helps remove obstacles that could prevent the team from achieving its goals. The Scrum Master is not a traditional project manager who assigns tasks to individual team members. Their role is to support the team, the use of Scrum, and the overall environment in which the team works.
Developers are responsible for creating the product and delivering the results of the work. The term does not necessarily refer only to programmers. The composition of the team depends on the specific project and the competencies required to create the desired result.
What is a Product Backlog?
A Product Backlog is an ordered list of everything that is needed to develop a product.
The Product Backlog may include, for example:
- new features,
- customer requirements,
- product changes,
- bug fixes,
- technical tasks,
- improvements.
Individual items have different levels of priority. The team therefore focuses primarily on the tasks that are currently the most important.
What are the advantages of Scrum methodology?
Flexibility
One of the main advantages is the ability to respond to changes. If requirements change during the project, the team can adapt its priorities instead of being tied to the original plan.
Faster feedback
Because results are presented and evaluated regularly, the team receives feedback much earlier. This makes it possible to identify problems and make changes before they become more serious.
Better overview
Shorter work cycles make it easier to see what has already been completed, what is currently being worked on, and what still needs to be done.
Team involvement
Team members participate more actively in planning and decision-making. This can increase their responsibility for the results and strengthen cooperation.
Continuous improvement
Regular reflection gives the team an opportunity to identify what could be improved and gradually make its way of working more effective.
Does Scrum also have disadvantages?
Scrum is not a universal solution that is suitable for every organization or project.
Problems can arise, for example, when:
- team members are unwilling to cooperate,
- roles and responsibilities are unclear,
- the organization requires a detailed long-term plan with minimal changes,
- Scrum events turn into unnecessarily long meetings,
- the team only uses Scrum terminology formally without following its principles,
- management does not provide the team with sufficient autonomy.
It is therefore important to see Scrum as a framework rather than simply introducing meetings, tables, and new names into the organization mechanically.
Example: Scrum in a marketing team
Scrum is not used only in IT. Its principles can also be applied in marketing teams.
Imagine a marketing team preparing a new campaign. The Product Backlog could include tasks such as:
- creating a landing page,
- preparing advertising campaigns,
- creating a newsletter,
- preparing social media posts,
- analyzing the target audience,
- measuring campaign results.
At the beginning of a Sprint, the team selects the most important tasks. During a two-week Sprint, team members work on them together. At the end, they may already be able to present a finished landing page or the first advertising materials.
Based on the results and feedback, the team can then adjust its priorities for the next Sprint.
This approach helps avoid a situation where a team spends several months following the original plan only to discover later that some of its initial assumptions were incorrect.
What to take away in conclusion?
For a beginner, this approach may initially involve many new terms – Sprint, Product Backlog, Scrum Master, Product Owner, or Sprint Review. However, once you understand the basic principle, the whole system starts to make sense. Work is divided into manageable parts, the team works together toward a defined goal, continuously evaluates the results, and adjusts the next steps based on new information.
Scrum methodology can be a useful tool for anyone involved in project management or team leadership. It is not only about knowing individual procedures. It is also important to be able to plan effectively, set priorities, communicate within a team, and respond to changes.
Project management is an important area of management education. As part of an MBA programme at CEMI, students also focus on project management, change, and innovation, allowing them to apply the knowledge they gain directly in their professional practice. If you are looking for a way to expand your management skills and become better at handling complex projects, knowledge of methods such as Scrum can be one of the useful tools on your journey toward more effective project and team management.
