Chapter 8Handling Tech Stories
Tech stories are things that need to get done but that are uninteresting to the customer, such as upgrading a database, cleaning out unused code, refactoring a messy design, or catching up on test automation for old features. We call these internal improvements, but in retrospect, tech stories is probably a better term, since we’re talking about stuff to be done with the product, not process improvements.
Tech stories are born in the “Ready for Development” section of the project board and enter development through a “Next Five Tech Stories” section (right below “Next Ten Features”). These are essentially two parallel input queues to development.
As you can see, there are quite a lot of cards under “Ready ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access