I love tech. I love the web. I love building successful products and teams. I work at ASOS doing all these things (but these opinions are entirely my own!)
I have often wondered if a need for tasking suggests that stories are too big
That is also a bad task. Tests are part of the definition of done surely….?
During the lifecycle of a story, it is essential to refactor code but costly to refactor tasks. Why take a double overhead there?
Reasonable assumption on the face of it, but unless users are demonstrating the value through their usage, then I would suggest the answer might be no?