23
Comments
  • 1
    I like the second point a lot, I hear it countless of times like: Ya but we delivered the product on time, we just need to squash those already known bugs
  • 0
  • 0
    Those are golden. I would like an elaboration/example for the 3rd one. Don't we all chase metrics? This website should score X% in performance audit. This application should load in Y milliseconds. This API should target Z p99 latency.
  • 0
    @0and1 That one is more about team/business performance.

    Examples where we make metrics a goal and you can "achieve" them:

    The business wants the team to reduce cycle time. Just reduce quality (eg skip code reviews) and things will "finish" faster.

    The manager wants to see more "story points" delivered at the end of the month. Just double your estimations.

    You have a fever and want the temperature to go down. Jump into a bathtub full of ice.

    These are ways to achieve the metric goals, without actually improving things. Ideally, metrics should be used to reveal whether efforts to improve are being effective.

    So, if you have a fever, take measurement to get better (meds, rest) and use the temperature as an indicator that these are working. If not, maybe you assumed it is just a flu but you are wrong and need other kind of actions.
Add Comment