I’ve heard that some teams say that they don’t like giving estimates as they feel that it’s often difficult to estimate and once they provide an estimate they fear criticism if they end up spending more time. I can understand that to a point as sometimes the complexity and risk associated with a story may […]

In my previous blog article on this I implied that you can do this in two ways estimating relative size, risk and complexity using a normalised scale For the latter we need to use hours (how else can we normalise?) For the former we don’t necessarily need to use hours to compare relative size, complexity and risk […]

The next Project Challenge will be on 10th and 11th October at London Olympia. It’s free and a great way to see interesting presentations on all aspects of Project Management and to network with other professionals. See here for more details – http://www.projchallenge.com/

Maybe something for a retrospective sometime, how do teams decide on the size of a story? If the answer is so obvious then perhaps your teams are well accustomed to agile practice but also maybe they are churning out the same stuff. The way teams should look at stories is in relative terms – “this […]

One big factor when estimating stories and tasks within stories is to ask yourself the question “have I done this before”? If the answer to this question is “yes” then you should be able to adapt in whatever way is necessary your previous experience to estimate these new stories and tasks – the risk should […]

Having a team self organize is one of the most flexible and challenging aspects in Agile – particularly where there may be several teams working in a scaled agile scenario. The concept of self-organization is related to the Agile Manifesto principle “The best architectures, requirements and designs emerge from self-organizing teams” (see Agile Manifesto – […]

Another one I can think of to add to those from 2008 is “No 9 – Regularly check your work-in-progress/flow”. For Scrum control of flow is implicit, the team have a velocity and this is an indication backed up with historical evidence as to how much work the team are capable of handling within an iteration. Yet, […]