The case against iteration based re-estimation

I’ll say up front that I have some major issues with the idea of estimation in agile processes. There are plenty of alternatives to traditional time/manpower estimation which are at least as useful in delivering real, useful results. However, if you are working in a context which values estimation, Adrian Wible has some interesting points …

Continue reading ‘The case against iteration based re-estimation’ »

Chickens and eggs, with a slice

It’s a common software development situation. In front of you is a problem which seems to require a large solution. It has several parts which may be deployed separately, or may just need to be swapped out or independently managed. It has infrastructure bits and business-specific bits, servers, services and clients. Now imagine that you …

Continue reading ‘Chickens and eggs, with a slice’ »

Agile: When is a story done?

Anyone who has worked with me in the past will probably recognize my standard response to vague or unclear requirements – “how will I know when I’m done?”. I use it so much becuase the simple trick of changing viewpoint to view work in terms of acceptance criteria is key to enabling sensible discussion, estimation, …

Continue reading ‘Agile: When is a story done?’ »

A structured way to work with user stories

For someone steeped in the traditional idea of requirements and features, working with agile user stories is often hard to handle. I have invested a lot of time over recent months attempting to build a good understanding of what a user story is, and how it differs from a feature, a change or a requirement. …

Continue reading ‘A structured way to work with user stories’ »