In software development work, a design pattern is a description of a solution to a recurring problem. It outlines the elements that are necessary to solve the problem, including context and the consequences of certain actions, without prompting the reader to solve the problem a specific way, leaving them with the agency to write code […]
The story of an Agile/Scrum Team and the problems they run into. In this episode the ScrumMaster spots the number of interruptions from outside the team…
Smaller stories tend to get more accurate estimates. This is my guidance for new Scrum teams, and ScrumMasters, trying to decide on Story size.
Development teams ask for case studies about agile, but didn’t before adopting their existing process. This blog post collects 14 Scrum case studies.
Four team building exercises that teach developers the value of process improvement, early delivery, small batches, and issues with specialization.
While Test Driven Development is challenging to learn on your own, TDD has tangible benefits that can’t be achieved by writing tests after the fact.
A response to objections about multiple return statements in my recent post on Minimal Coding Style, covering the history and my thoughts on methods.
While researching “Are there weaknesses with Collective Code Ownership?” for InfoQ, I was struck by the number of myths around Collective Code Ownership.