↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

How do I prevent Scrum from turning great developers into average developers?

The question argues that daily Scrum can reward easy work, constant updates, and visible velocity, which may pull strong developers away from hard problems and toward tickets that are simple to report. The replies split between seeing this as a misuse of Scrum and seeing it as a structural tendency when management tracks output too closely.

Reading notes
#

  • The question says daily Scrum can push developers toward the easiest work and make it harder to spend days thinking through difficult problems.
  • One answer says Scrum should not overwhelm everything else and that public velocity and task boards can turn productivity into a simple ranking.
  • That answer also says short sprint focus can encourage cutting corners, weak testing, and architecture that grows from individual tickets.
  • It argues that standups often become a way for management to monitor progress rather than a useful developer coordination meeting.
  • Another answer says the described behavior is not real Scrum, because the Daily Scrum is for the Development Team and outsiders should not direct the meeting.
  • That answer claims Scrum gives the team autonomy and is meant to let experts work without constant interference.
  • A third answer says Scrum can be positive when it helps a cross-functional team share context, raise technical concerns, improve planning, and discover problems early.
  • It also says Scrum works only when management trusts the developers and plays along with the process.
  • One answer says frustration with Scrum is widespread because management often introduces it to regain control and then applies it unevenly.
  • That answer says only strong teams can survive Scrum well, while weaker setups are pushed toward mediocrity.