back to top

our blog


agile estimating

Estimating in Points Seems a Bit Stupid!

by Kelly Waters, 24 October 2008

A while ago I blogged about “What’s the Point in estimating?“. To be honest, I didn’t understand the concept of estimating in Points when we first adopted agile. Actually, I thought it sounded a bit stupid! But I get it now, and it makes a lot of sense. I would add to my original blog […]

Tell me more >
Agile Project Planning

by Kelly Waters, 04 August 2008

Projects are a necessary evil 🙂 But necessary they are. Some people really feel the need to understand precisely what the project will cost and exactly long it will take. If this is the basis for investment, of course that’s a completely understandable feeling. For years, traditional waterfall projects have been sold on the false […]

Tell me more >
Agile Release Planning

by Kelly Waters, 25 February 2008

A software release may result from multiple iterations (or ‘Sprints’ in Scrum). Sprint Planning is about planning what’s included in the next iteration. Whereas Release Planning is about planning multiple Sprints, in order to predict when a release (or releases) might be delivered. Release Planning is a very simple way of doing some top-down planning. […]

Tell me more >
What Is The Point In Estimating?

by Kelly Waters, 10 December 2007

One technique used by agile development teams is the idea of estimating product features using points. This has a few distinct advantages over estimating in physical units of time. 1. Estimating is very quick because it’s an intuitive estimate of a feature’s size. 2. An estimate in points indicates a feature’s size relative to another, […]

Tell me more >
Definition of DONE! 10 Point Checklist

by Kelly Waters, 26 July 2007

A key principle of agile software development is “done means DONE!” To be more specific, here’s a 10 point checklist of what constitutes ‘feature complete’… Code produced (all ‘to do’ items in code completed) Code commented, checked in and run against current version in source control Peer reviewed (or produced with pair programming) and meeting […]

Tell me more >