My colleague Michael Brunton-Spall makes an interesting mistake in his latest blog post:
much of our time as developers is being completely wasted writing software that someone has told us is important. Agile Development is supposed to help with this, ensuring that we are more connected with the business owners and therefore only writing software that is important.
Most Agile methodologies actually don’t do what Michael says here. Every one I’ve encountered in the wild treats it as almost axiomatic that there exists someone who knows what the correct business decision is. That person is then given a title, “product owner” for example and then is usually assigned responsibility for three things: deciding what order work is to be done, judging whether the work has been done correctly and clarifying requirements until they can be reduced to a programming exercise.
That’s why it was liberating to come across System…
View original post 275 more words