What I learned from chopping wood

A lumberjack is chopping wood.

When I moved to a farm, three years ago, I thought I would be able to take what I had learned from consulting and agile and apply it to farming. I soon found out that I was wrong. The true lessons were not in what I could re-apply in farming…

Continue reading

Agile projects requirements breakdown structure

fibonacci series in nature

In Agile projects, when a set of requirements are received from Clients, it may consist of (a mix of) A few needs, objectives, goals and some partial stories (even though it would have come in a structured document). Re-organizing (re-arranging) those into a requirements breakdown structure (RBS) helps ask right questions to…

Continue reading

Combining Traditional and Agile Estimation

Can you combine traditional and agile estimation? There is nothing magical about “classical” estimation. There are a few basic concepts to keep track of:

  • Bottom up versus top down
  • Expert estimation versus parametric estimation
  • Best – worst – expected case

I think the most common method for traditional estimation is to go top-down using successive estimation which means that when something is to big or uncertain, you break it down into component tasks and estimate them recursively. If you are familiar with Planning Poker you can easily combine it with this approach:

  1. Start with your user stories + other backlog items then FOR EACH
  2. Estimate it with PP, if too big or to wide spread it is an Epic. Break it down into smaller stories (this creates your WBS) and GOTO 2
  3. Now that your item is sufficiently small, think about the worst case and estimate it again
  4. Now think about the best case, estimate again
  5. Calculate the weighted average as (best + 4* “normal” + worst) / 6

Not so different from “pure” Planning Poker, is it? There are a few improvements you can do though — instead of using three estimates for each item, you could use the spread of estimates you already have from PP as a basis for your probability distribution.

Agile Estimation Units (revisited)

A team estimating their next iteration using planning poker. What agile estimation units are they using?

Continue reading

Tired of estimating? Try the goat!

Are you tired of estimating all the time but not ready to go all the way to #noestimates? Let the estimation goat do all the hard work of guessing for you.

Continue reading

How to Fail as an IT Purchaser

Caveat Emptor

Update 2014-11-15: This problem is still unsolved. Now contracts are being won with even -11 SEK/h bids for some categories of consultants. Yesterday Computer Sweden revealed how a consultant company had managed to win a bidding competition for providing IT consultants the Swedish social security agency (Försäkringskassan). Their idea was…

Continue reading

Is there any real difference between Burn Down Charts and EVM?

A burn down chart

[bibshow]In the September/October 2010 issue of IEEE Software Hakan Erdogmus discusses the differences between Earned Value Management and current agile practices such as burn down charts. His conclusion is that while similar these two concepts are not the same.[bibcite key=”citeulike:13767577″] I do not agree, I think burn down charts and…

Continue reading