HR-Glossar
Scrum
What Scrum is, which roles and events belong to it and where the framework helps – with advantages, limits and tips for employers and employees.
1. What is Scrum?
Scrum is an agile framework for the flexible, iterative development of products and projects. The authoritative text is the Scrum Guide by Ken Schwaber and Jeff Sutherland — it is freely available and the only version that describes the framework bindingly. Originally designed for software development, it is used today across many industries – from product development through to construction and healthcare management.
Scrum rests on short work cycles known as sprints and encourages transparency, regular adjustment and continuous improvement. It follows agile principles that make quick adaptation to market change or new requirements possible.
2. Origin and development
Scrum was developed in the 1990s by Jeff Sutherland and Ken Schwaber. The two coined the term "Scrum" after a term from rugby that stands for close teamwork.
The framework was first presented at a conference in 1995 and later recognised in the Agile Manifesto (2001) as one of the leading methods for agile software development. Since then Scrum has spread well beyond the world of IT and is today one of the best-known approaches to modern project management.
3. Core principles and how it works
Five central values
- Courage – raising challenges openly and honestly and standing up for improvement.
- Openness – transparency is essential for successful collaboration and constant adjustment.
- Respect – every team member brings valuable skills; mutual appreciation is decisive.
- Focus – the team concentrates on the sprint goals and minimises distraction.
- Commitment – every member takes responsibility for their tasks and for the team's result.
Three pillars of empirical process control
- Transparency – everyone involved can see how the work is progressing.
- Inspection – regular meetings to reflect on the way of working and on results.
- Adaptation – continuous improvement based on feedback and experience.
The three roles
The product owner is responsible for the product vision and for prioritisation, creates and maintains the product backlog and makes sure the team works on the most important tasks. The scrum master supports the team, removes obstacles, facilitates the meetings and sees that the framework is followed. The development team is a self-organised group from development, design, testing and other disciplines that delivers the tasks of a sprint on its own responsibility.
Events and artefacts
Scrum has five events – the sprint (a fixed period in which an increment is created), sprint planning, the daily scrum, the sprint review and the sprint retrospective – and three artefacts: the product backlog (a prioritised list of all requirements), the sprint backlog (the tasks selected for a sprint) and the increment (the finished, tested result at the end of the sprint).
4. Who is Scrum relevant for?
Scrum is used by many professions and organisations, particularly in IT and software development, product management and innovation, marketing and creative agencies, construction and architecture, health and social care, and in start-ups. Companies benefit from the ability to adapt quickly, team members from clearly defined processes and roles.
5. How it differs from related terms
Scrum makes particular sense where quick adjustment and regular improvement are needed. Where work arrives continuously rather than in fixed cycles, Kanban is often the better fit; the two can also be combined.
6. Advantages and challenges
Advantages
- Greater flexibility and adaptability
- Better collaboration and transparency
- Faster response to change
- Clear roles and responsibilities
- Higher motivation and ownership within the team
- Regular customer feedback improves the final product
Challenges
- Requires cultural change and discipline
- Not every organisation is suited to Scrum
- Misunderstandings about roles and processes can arise
- Implemented badly, it brings chaos rather than efficiency
7. Best practices for implementation
Make requirements and progress visible
User stories state requirements clearly; burn-down charts make progress visible; a scrum board (in Jira or Trello, for instance) shows the tasks to everyone.
Anchor communication and improvement
Constant communication and feedback are essential; the sprint retrospective is the fixed place to improve processes step by step.
8. Tips for employers and employees
For employers
- Offer training and certification for scrum masters and teams
- Use tools such as Jira, Trello or Azure DevOps for support
- Encourage an agile company culture
For employees
- Gain Scrum certifications (PSM or CSPO, for example)
- Practise self-organisation and taking ownership
- Ask for feedback actively and act on it
9. Conclusion
Scrum is a powerful framework that helps teams work efficiently and flexibly. It encourages collaboration, ownership and continuous improvement. Scrum is not suited to every company – but where adaptability is what counts, it can bring considerable advantages. With training, clear processes and an agile mindset it can be introduced in companies of any size.
Sources
Related terms
Our promise
Software supports. People take responsibility.
Let us talk about your payroll – no strings attached, specific, and with a dedicated contact from day one.