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 ...
Get Lean from the Trenches now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
