This article describes the decision pattern of anchoring, where your decision is made by taking into account previous decisions. One example of this in our software development domain is if someone has made an estimation, subsequent estimations will be made with the first estimation as an anchor. Highly readable!
When we know of this pattern, how do we do to minimize the effect of this? One example is point estimations and velocity calculations used in the agile community. Since we don't speak of real hours this is a tool to make sure that no-one anchors an estimation in real hours, which will ripple through in all re-estimations of the story in question.
0 kommentarer:
Post a Comment