Many software developers working in a Scrum environment see Scrum as a “company tax” — additional overhead they need to adhere to because their company expects them to. Dailies, reviews, refinements, and retros are seen as ceremonies; something you have to endure that don’t really add much value to your work. If this is how Scrum feels to you, you’re not alone. In this article, I want to explain w
![“Why Scrum” for Software Developers](https://cdn-ak-scissors.b.st-hatena.com/image/square/94cef9ba0db93f3fb6716e8e63ba2c1826873872/height=288;version=1;width=512/https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A1024%2F1%2Ahy3Wj-XEgfLS1e7O7GR2Bw.png)