Yes thank you. I think the reality of DSM don&#x27;t live up to their theoretical usefulness.<p>I think even in a small team where everyone keep it short it&#x27;s just too much information. I can already see what everyone is doing on Jira&#x2F;etc and later on git in my IDE, the rest don&#x27;t stick.<p>I have tested people by asking them less than 30mn after a DSM questions about who is doing what and nobody could answer and yet they usually can&#x27;t admit that DSM are mostly worthless.<p>I also hate DSM when I&#x27;m on a long task because I just say the same thing everyday and feel like a slacker. At which point do you start to game the system and only pick short easy tasks ?<p>I guess maybe Scrum and agile appeal more to young devs ? They seem to like the gamification aspect of it, moving post-its, feeling great by under-estimating tasks&#x27; length, the flatness of the team.<p>Myself I would prefer a competent project manager instead of those empowering retrospectives and those velocity charts that could be turning against you by management any day.<p>Over dramatization aside :) and in good spirit about the article I would prefer Kanban to Scrum but it seems way less used (at least in webdev).