Introduction to Scrum

Scrum draws heavily from agile and the two are often confused. But how are they different and what are the typical principles scrum uses?

Scrum and agile

Scrum draws heavily on agile and the two are even often confused. Agile can be described as a philosophy, an approach of thought that has values rather than rules at its center. Scrum, in contrast, is the concrete application of agile management to project delivery.


Scrum is based on the same values as agile and uses the same elements (sprint, user story, backlog) and rituals (e.g. sprint evaluation and retrospective, standup). But it is more rigorous in doing so. So expect 2 weekly sprints, ongoing feedback and active involvement in the project. Just like in an agile-driven project.


The main difference lies in the different roles in the development team. Unlike Agile, Scrum is based on the role of the Scrum Master, who

  • removes any obstacles in the work of the team members
  • manages the so-called scrum ceremonies
  • ensures that the scrum process is used as it should and brings the desired benefits.


Scrum is often used in internal projects, where the role of the client is represented by the Product Owner, who defines the project and product vision and priorities and acts as the main liaison to the management.

Scrum is suitable for you when:

  • The scope of the project is uncertain. In other words, you are not sure what exactly you want from the product. If you decide to go with scrum, we will proceed in small parts, which we will consult together and gradually arrive at an idea of the whole project.
  • Regular demonstrations as the software development progresses allow us to incorporate changes flexibly.
  • A working product is the measure of progress.


Principles

With scrum, you’re not trying to get the perfect product right from the start. The goal is to launch the MVP as soon as possible, gather feedback from customers, and then continuously improve the product. That’s why the following principles come in handy:

  • IKIWISI =I know it when I see it
  • YAGNI = You’re not going to need it (we often remind this to our clients during the MVP development)
  • KISS = Keep it simple, stupid (don’t overcomplicate things is a general rule on how to manage complex projects).

If you think of any questions while reading, please do not hesitate to leave us a message. We will be happy to answer them and update the article.