
ALT As the author of the article, a few raw thoughts: 1. It's more important that a team/company solve for *their own, specific* pain points, and to operate using their own strengths (and within their own constraints), than to follow any frameworks, however popular or well-known that framework is. 2. Different companies have different strengths and constraints. Something we talk very little about is how the top of the market tends to compensate much better: and thus hires people of whom they can expect more: more self-starter attitude, more autonomy, more "thinking outside the box." They also line up outsized rewards around all of this! See https://blog.pragmaticengineer.com/software-engineering-salaries-in-the-netherlands-and-europe/ 3. Sketching out a plan before starting, Scrum, Kanban, TDD, XP: these are all tools that any one team can use. The best teams have a broad set of tools and use whatever makes most sense for their context. 4. The Agile Manifesto is 22 years old. A lot has





















