The Codest
  • Sobre nós
  • Serviços
    • Desenvolvimento de software
      • Desenvolvimento de front-end
      • Desenvolvimento backend
    • Staff Augmentation
      • Programadores Frontend
      • Programadores de back-end
      • Engenheiros de dados
      • Engenheiros de nuvem
      • Engenheiros de GQ
      • Outros
    • Aconselhamento
      • Auditoria e consultoria
  • Indústrias
    • Fintech e Banca
    • E-commerce
    • Adtech
    • Tecnologia da saúde
    • Fabrico
    • Logística
    • Automóvel
    • IOT
  • Valor para
    • CEO
    • CTO
    • Gestor de entregas
  • A nossa equipa
  • Case Studies
  • Saber como
    • Blogue
    • Encontros
    • Webinars
    • Recursos
Carreiras Entrar em contacto
  • Sobre nós
  • Serviços
    • Desenvolvimento de software
      • Desenvolvimento de front-end
      • Desenvolvimento backend
    • Staff Augmentation
      • Programadores Frontend
      • Programadores de back-end
      • Engenheiros de dados
      • Engenheiros de nuvem
      • Engenheiros de GQ
      • Outros
    • Aconselhamento
      • Auditoria e consultoria
  • Valor para
    • CEO
    • CTO
    • Gestor de entregas
  • A nossa equipa
  • Case Studies
  • Saber como
    • Blogue
    • Encontros
    • Webinars
    • Recursos
Carreiras Entrar em contacto
Seta para trás VOLTAR
2019-06-25
Gestão de projectos

Scrum or not to Scrum? Pros and Cons of Scrum

Margo Kosnik

Scrum is a very common framework for project management. It is often used in IT projects. Its main advantages are efficiency in team management, control over the entire process and the possibility of constant monitoring of the progress. The question is, is it an ideal method of project management? Well, that’s a good question.

Scrum has many followers, and I’m one of them. However, you can not be indifferent to the negative rumors you might have encountered about this framework. Recently, I have met with a colleague that has a very disapproving opinion on Scrum. This motivated me to write this article.

This article is addressed to all projeto managers who often face the dilemma of choosing the right gestão de projectos methodology. In the case of Scrum, I appreciate it for the possibility of a relatively quick start of the project, ease of building a equipa and its transparent process. However, I think that the effectiveness of the Scrum methodology is strongly influenced by people who develop the project. Their understanding of the product’s needs, their knowledge and their commitment are the fundamentals for a project’s success.

Before I go into a detailed analysis of the pros and cons of Scrum, I want to remind you about the basic division of roles in this type of projects:

1. Scrum Master – runs and supervises the team and maintains the appropriate motivation of all project members.

2. Produto Proprietário – a person representing the client side.

3. Development team – a team responsible for product delivery.

Ok, we are done with the theoretical part. Now let’s talk facts. I prepared a list for and against the Scrum methodology. I’ve outlined all the advantages and disadvantages of this solution, which should help you make the best decision for your project.

Prós:

  1. Scrum is a framework that can help you manage your project more effectively and make better use of time and budget.
  2. Scrum is a guarantee of transparency of all stages of the project.
  3. It is estimated that Scrum is currently the most effective method of managing IT projects.
  4. One of the principles of Scrum is to focus on minimizing errors. Thanks to this approach (for example, running numerous tests) you can be sure that the project is maintained at the highest quality level.
  5. The implementation of the project using Scrum is divided into so-called sprints. During their lifetime, the team focuses on the development of strictly defined functionalities. Sprints are a great way to achieve progressive and sustainable desenvolvimento de produtos.
  6. Scrum is a very flexible methodology. If the customer wants to make any changes or extend the product with new functionalities, usually there are no problems with that. This kind of elasticity is ensured by sprints.
  7. Scrum provides task prioritization. First, you develop the ticks of the main “to do”, and then you also implement a “backlog task” list. This last one includes tasks that can be described as “nice to have”. In this way, you can be sure that the team is currently working on the most important functionalities.
  8. Scrum is also an effective methodology from the client’s perspective. Thanks to daily meetings, the client can be up to date with all current work. His feedback is also taken into account.
  9. Daily meetings help to identify emerging threats and problems that can be quickly solved.
  10. The Scrum methodology is affordable for the budget. You can regularly control and estimate all expenses.

Advantages of Scrum

Cons

  1. The success of your project may be at risk if a team member is not involved or does his job slower than the others.
  2. The Scrum Master role is critical. If he does not perform his duties duly, it may lead to delays in the project.
  3. Scrum is ideal for 3-9-person teams. In the case of larger teams, there may be problems in management efficiency.
  4. Daily meetings can be frustrating for team members who present the results of their work.
  5. The unexpected departure of one team member may harm the progress of the entire project.
  6. The date of product delivery and the correr time limit shall not apply to Scrum.

Go with Scrum or not?

Scrum is not an ideal methodology for all kinds of projects, but I still recommend you use it. Especially when you are responsible for IT projects. If you plan all the work thoroughly, you have a greater chance to achieve high efficiency and be successful.

Consider all the pros and cons that I have mentioned here and think about whether your project meets the criteria that will allow the effective development of the project using Scrum. If you correctly identify your needs and possible threats, I am convinced that Scrum will help you achieve success.

Ler mais:

  • Delays in your project again? Say ‘never again’! Check how to win the game and deliver in time!
  • Proptech. A fast developing industry. Why is it worth to keep an eye on it?
  • Porque é que é possível construir um MVP com o Ruby on Rails?

Artigos relacionados

Soluções para empresas e escalas

Porque é que a sua empresa precisa de uma equipa de desenvolvimento remoto?

Explore as vantagens e estratégias da integração de equipas de desenvolvimento remotas, destacando a relação custo-eficácia, o acesso global a talentos e a flexibilidade.

The Codest
Agata Waszak Especialista em soluções para clientes
Gestão de projectos

Fundamentos da Adoção Ágil: Um roteiro para equipas técnicas

Saiba como adotar eficazmente as metodologias Agile com os conhecimentos do nosso especialista PM - Jan, para melhorar a eficiência e a colaboração.

The Codest
Jan Kolouszek Gestor de projectos
Gestão de projectos

Da mesa do PM: Técnicas eficazes de gestão de equipas à distância

Aprenda estratégias comprovadas do nosso PM Jan para otimizar a gestão de equipas remotas e aumentar a produtividade. Leia agora!

The Codest
Jan Kolouszek Gestor de projectos
Soluções para empresas e escalas

7 Estratégias-chave para gerir uma equipa de desenvolvimento de software

Este artigo detalha as principais estratégias para gerir eficazmente as equipas de desenvolvimento de software, dando ênfase à comunicação, às ferramentas de gestão de projectos e à compreensão da dinâmica da equipa.

OCODEST
Gestão de projectos

Guia CTO: Gerir eficazmente os programadores remotos

Em todo o mundo, mais de 60% das pessoas trabalham remotamente. Esta tendência é especialmente notória no sector das TI. Cada vez mais programadores apreciam a possibilidade de trabalhar remotamente. Devido a...

The Codest
Kamil Ferens Diretor de Crescimento

Subscreva a nossa base de conhecimentos e mantenha-se atualizado sobre os conhecimentos do sector das TI.

    Sobre nós

    The Codest - Empresa internacional de desenvolvimento de software com centros tecnológicos na Polónia.

    Reino Unido - Sede

    • Office 303B, 182-184 High Street North E6 2JA
      Londres, Inglaterra

    Polónia - Pólos tecnológicos locais

    • Parque de escritórios Fabryczna, Aleja
      Pokoju 18, 31-564 Cracóvia
    • Embaixada do Cérebro, Konstruktorska
      11, 02-673 Varsóvia, Polónia

      The Codest

    • Início
    • Sobre nós
    • Serviços
    • Case Studies
    • Saber como
    • Carreiras
    • Dicionário

      Serviços

    • Aconselhamento
    • Desenvolvimento de software
    • Desenvolvimento backend
    • Desenvolvimento de front-end
    • Staff Augmentation
    • Programadores de back-end
    • Engenheiros de nuvem
    • Engenheiros de dados
    • Outros
    • Engenheiros de GQ

      Recursos

    • Factos e mitos sobre a cooperação com um parceiro externo de desenvolvimento de software
    • Dos EUA para a Europa: Porque é que as empresas americanas decidem mudar-se para a Europa?
    • Comparação dos centros de desenvolvimento da Tech Offshore: Tech Offshore Europa (Polónia), ASEAN (Filipinas), Eurásia (Turquia)
    • Quais são os principais desafios dos CTOs e dos CIOs?
    • The Codest
    • The Codest
    • The Codest
    • Privacy policy
    • Website terms of use

    Direitos de autor © 2026 por The Codest. Todos os direitos reservados.

    pt_PTPortuguese
    en_USEnglish de_DEGerman sv_SESwedish da_DKDanish nb_NONorwegian fiFinnish fr_FRFrench pl_PLPolish arArabic it_ITItalian jaJapanese es_ESSpanish nl_NLDutch etEstonian elGreek cs_CZCzech pt_PTPortuguese