Writing user stories for internal technical tasks [closed]

Answer 1

Upgrade the database may be one of the tasks involved in implementing another story that brings direct value to the user, for example I as a user can add a new foo to my bar.

If adding a foo to a bar requires a database upgrade behind the scenes, then you would include that work in implementing that user story.

User stories are worded this way to help ensure that any work directly benefits the end user in some way.

Answer 2

This gets to the forefront of why user stories are so great.

What benefit does upgrading your database give to the end user? None? Then don't spend the time and money doing it. Spend that time and money providing something that will give value to your end user.

If it does? Then think about it the other way. Maybe you can only implement a new feature when you have version x of your database software? In the dependency of the story, you could mention that database upgrade required to provide this feature.

tl;dr Don't just upgrade for the sake of it. Make sure upgrading adds tangible value to your customers.