Scrum – advantages and disadvantages

scrum board

Scrum is an agile product development framework – a collection of values, team roles, and rituals used in combination to create iterative work products. There’s no limit to the types of businesses that use Scrum for product development, but its usage is the most common in Information technology.

Let’s get into some advantages and disadvantages from our point of view, although the disadvantages are negligible:

Advantages first:

  • The developer is protected from everyday contact with clients. Most developers don’t like the daily level of questions: how does it go with the project, when will you finish it, and so on;
  • A team above the individual. Team spirit is one of the basics of Scrum. It’s also important in sport, and that’s what makes the team stronger than a simple set of individuals.
  • Transparency in work. Although initially, it requires training (especially if you are introvert), it later provides an opportunity to see a wider picture of a developing product, to spot problems earlier, to get to know colleagues and their habits better, etc.
  • Results are visible quickly. Developers and also clients prefer to see some results of the work. It could be the motivation to continue further.
  • Corrective. Scrum is forcing constant retrospectives and reflections on how to improve the product. It gives great results.

Disadvantages:

  • Long meetings (for Product Backlog Refinement or Retrospective) can be very demotivating. Developers prefer to – develop.
  • The focus on the speed of development and iterativity sometimes leads to a decline in quality. Although testimonials are being used on Scrum training, TDD, etc. It also emphasizes that it is important to complete the task within the estimated time frame and without any superfluous code.
  • Scrum cannot be used for projects with strict length and time frame, especially when projects are short.

Depending on the project, it is necessary to adopt scrum framework to specific clients, depending on the complexity, size of the team and the duration of the project. Each project is a story for itself and it is impossible to apply an identical method on each project.