DEV Community


Discussion on: Great User Stories for Continuous Deployment

v3rtti profile image
Janne Sinivirta Author

You are right that this thinking could be abused. I'll make two points on this:

  • We trust our developers and encourage them to include technical-debt reduction and refactoring in to the stories. So if doing thing A properly requires that I start by improving the existing code base then you do it, we won't question you.

  • "What will I have to show" is just one way of teasing out the essence of what you are doing, it should not be the defining metric for prioritising your work.

But like with all in agile, we need to focus on honest communication between product needs and responsible development. Maybe I've been lucky but with the teams I've used it with it has worked well and people were not afraid to still pick "invisible" tasks when they considered them important.