I love the conclusion - Finish the thing and measure the outcome. Too often, measuring the outcome is not one of the given requirements. Whoever gave the requirement knows what they're talking about. They don't think they need it to be measured.
In a story from my Microsoft days, a Program Manager requested a new feature to improve performance (the HiPPO in this story). I did the analysis of use cases to argue that in most cases the feature would either reduce performance or have no effect. There were some corner cases where it would help. The HiPPO said those corner cases were important but agreed that the feature should be off by default and only turned on by those users who really needed it.
To have the conclusion to this story, I wish I had also implemented a way to measure how often the feature was used. That feedback would have been concrete information we all would have learned from.
I love the conclusion - Finish the thing and measure the outcome. Too often, measuring the outcome is not one of the given requirements. Whoever gave the requirement knows what they're talking about. They don't think they need it to be measured.
In a story from my Microsoft days, a Program Manager requested a new feature to improve performance (the HiPPO in this story). I did the analysis of use cases to argue that in most cases the feature would either reduce performance or have no effect. There were some corner cases where it would help. The HiPPO said those corner cases were important but agreed that the feature should be off by default and only turned on by those users who really needed it.
To have the conclusion to this story, I wish I had also implemented a way to measure how often the feature was used. That feedback would have been concrete information we all would have learned from.