Tag: agile estimating

Estimating a backlog of 100 items in 1 hour? Challenge accepted.
The situation The agile team was working in a still mostly project-based environment. Over the period of several months, they had created backlog items, both with nice business value and also items to get rid of some technical debt they had piled up, getting to a situation where they had about 125 backlog items, of which only a dozen were estimated and refined, ready for...

How to fix Scrum teams that are terrible at estimating and forecasting?
First of all, we should ask ourselves: "Why do we estimate?". In a lot of cases it's because of the wrong reasons, but let us assume we are in a context where estimates are needed. What would that context look like? A Large-Scale setting where a Rolling Wave Plan is used by other parts in the organization (sales, marketing, heck even customers), increasing the complexity IT teams are...

Popcorn time: 3 must-see videos on agile estimating!
You’re still struggling with estimations or you think you’ve completely mastered it? I highly recommend the following 3 videos. Get some popcorn, sit back and enjoy the show! Video 1: Agile estimating Summary: the basics on agile estimating. Tagline: estimate size, derive duration Star: Mike Cohn Duration: 58:21 Event: Norwegian Developers Conference, 6 June 2012 Topics covered: ideal time story points planning poker. Video 2:...
Most common mistakes in scrum ceremonies 2/7: estimating stories
Spending too much effort in estimating stories People have the tendency to spend too much effort on estimating the incoming work. Having some basics skills available, like high/low showdown, deal and slide and planning poker will help the team to make well educated estimates they feel comfortable with. These techniques are also designed to maximize the return on investment of your time when it comes...
Most common mistakes in scrum ceremonies 1/7: grooming the backlog
No prioritization Although there is a product backlog that contains almost all the work that can be planned, there is no real prioritization and things get picked up ad hoc, purely based on reactionary prioritization. In most cases this is a symptom of a number of possible underlying diseases. More often than we like to, we see product owners not really equipped for reaching their...
Agile estimating 4/4: Kanban approach to estimating
Now I also promised you a second option of using a range of numbers instead of one number. This is something we use in a typical kanban implementation. I’ll explain how we would go about it. In kanban we would start by collecting historical data. Using this data we can discover several types of work that have significantly different cycle times, time to complete a...