In February, I published the article Skilling Up Development Teams on Agile Alliance. In it, I argue for the need to consciously and structurally improve the people who build and maintain software. I explain how adopting the right practices can help bridge the gap between the needs of development teams and broader organizational goals.

By focusing on practices, small containers of knowledge, skills, and mindset that help you perform a specific job well, we can make skilling up more tangible. Instead of vague ambitions like “we need better quality” or “we should innovate more,” we can talk about adopting or improving specific practices, such as continuous integration or organizing innovation sprints.
The article triggered several interesting discussions. One of them was with my colleague Dion Nicolaas, an agile coach and Scrum Master. Dion pointed out that, rather than adopting new practices, there is another option that I overlooked. Sometimes teams improve by doing less. In his article Breaking Eggs, he explores the power of deliberately dropping practices.
You can read the article on the agile alliance site: Breaking Eggs: The Case for Dropping Practices

















