Somehow this myth persists: Agile means we no longer have to produce any documentation, right? Sorry to disappoint you, but that’s just not true.
If we revisit the Agile Manifesto and read it carefully, what it says is “we have come to value working software over comprehensive documentation“. It says there is more value in working software, but it does not say that there is no value in documentation – there is some value in documentation, and more importantly there is value in the right documentation.
Continue reading “Agile means no documentation, doesn’t it?”
If you have ever tried to solve a complex problem, you probably discovered the benefits of working with someone else – whether that person had more experience than you or could just ask questions that challenged your thinking. Compare that to a time when you were handed a checklist and just ticked things off – which produced the better solution?
Continue reading “Individuals and interactions”
Let’s start with the basics: what is Agile?
It’s an umbrella term, coined in February 2001 when the Agile Manifesto was created. The manifesto starts by saying: We are uncovering better ways of developing software by doing it and helping others do it. It’s important to understand that it says uncovering – it doesn’t claim to be the definitive How To for software development. Sixteen years later, I think it’s safe to say we are still uncovering better ways.
Continue reading “What is Agile?”
Most of the content of this site has been for my curriculum vitae … until now! I’ve seen enough similar challenges across the many teams I’ve coached over the years, so I think it’s time to share some of them.
I’ll use tags to keep them separate (blog and cv) and you’ll also be able to find them in the sidebar.