DEV Community

Discussion on: Technical stories, a miscast artifact of agile development

Collapse
 
learnitmyway profile image
David • Edited

Great article!

The number of technical stories is a useful fitness function

Would going into detail here be worth another blog post for someone who doesn't know where to start?

Notice that I haven’t talked about the tension between including user stories and technical stories in an iteration. That relates to building a technical backlog and assessing the health of a system. I plan to dig into that on its own post.

Really looking forward to this. The team I am currently on does tech debt days once every two weeks, which is better than completely ignoring it (this was the case before), but I find it severely lacking.

Collapse
 
sirech profile image
Mario Fernández • Edited

I track the technical stories in the backlog and see if the number is growing over time, nothing very scientific.

Getting tech debt stories into the sprint is a hard one. I think my biggest success has been when my PO trusts me and I can pull stories into the sprint without too much discussion. I've tried variations of reserving a budget for tech that don't always work that well. It's a topic for a whole article, though!

Collapse
 
learnitmyway profile image
David

I track the technical stories in the backlog and see if the number is growing over time, nothing very scientific.

Ah, that easy! Thanks :)

Getting tech debt stories into the sprint is a hard one. I think my biggest success has been when my PO trusts me and I can pull stories into the sprint without too much discussion. I've tried variations of reserving a budget for tech that don't always work that well. It's a topic for a whole article, though!

That makes sense. Looking forward to the article!