#Why[Some Tool]
▻https://hackernoon.com/why-some-tool-57f4c3df2be7?source=rss----3a8144eabfe3---4
I was having a heated discussion with someone recently about story points. It was one of those standard “that’s not the fault of story points” arguments that goes nowhere. I realized a very common pattern — one that I have found to signal an opportunity for “refactoring” common approaches. It is age-old…basic decoupling and separation of concerns.The QuestionWith every process, tool, methodology, and framework you adopt…ask:What job(s) are we hiring [the thing] to do?List them out. What you’ll find, is that you are frequently asking [the thing] to do more than one job. Let’s take a simple example: story points.Example: Story Point JobsEstimate duration for a projectKeep track of progress towards a bigger goal OR deadlineKnow how many stories to “pull” into a sprintCalculate some sort of productivity (...)