PDF version Introduction For something that always seems so fresh and maybe even still trying to find its feet, Agile has a remarkably long history. Rapid Application Development (RAD) emerged from the work of Barry Boehm and James Martin in the 1980s, and Dynamic Systems Development Method (DSDM) in [...]
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Agile Manifesto - Principle 6 Traditional (especially waterfall) delivery methods are generally very document-heavy. Long before a line of code is written, an ocean of ink is spilt in the form of [...]
One of the key questions we face time after time is 'Why would I want a methodology?' The question is usually posed in such a way that you can almost hear the thought process going on behind it: Isn't methodology just another bureaucratic nightmare? Isn't the whole idea of a [...]
“Pro tip: Never assume shared understanding” - Charles Lambdin. Absolutely. In fact, if you’re in a position where a topic is under serious debate (consultancy, coaching, training, change programme, etc.) you should prioritise grasping exactly where your understandings differ, & removing that. From then on, change will be a lot [...]
A key issue with Agile’s high-frequency delivery regime is change fatigue: however promising in principle, there’s a limit to how much change anyone can absorb. But how do you know you’re nearing that limit? Here are Agile201’s Top 10 signals of impending fatigue: Areas being changed resist the latest changes. [...]
All too often I hear people repeating a very old adage about modelling: "All models are wrong, but some are useful." My immediate reaction to this tends to be 'so what?' No, models don't describe the world in detail or provide insight into every facet of it, yet they do [...]
When explaining Agile, it's common to describe it in terms of the basic development-and-delivery process from which Agile (and especially Scrum) began: A single development team. Focused on a single iteration (with occasional references to a multi-iteration release). Limited to software development (with an implied but not described software deployment [...]
A few pieces of entirely gratuitous (although, after 30 years of bitter experience, entirely merited) abuse of waterfall development methodologies. Enjoy.