
One Slide At A Time Episode #27 - Rainbow and Circular Backlogs
07/28/21 • 12 min
Previous Episode

One Slide At A Time Episode #26 - INVESTing in Technical Stories
A technical story is one where the main stakeholders are the engineering/infrastructure team/leadership. The end-user benefits only indirectly from such a story. Technical stories often are non-functional requirements. Non-functional requirements include security, performance, maintainability, usability, refactoring, infrastructure,accessibility, compliance, reusability. (Look up Non-Functional Requirements). https://rgalen.com/agile-training-news/2013/11/10/technical-user-stories-what-when-and-how
Next Episode

One Slide At A Time Episode #28 - How to Payoff and Avoid Technical Debt!
Technical Debt is the accumulation of what is known as enabler and technical stories. It's when you've built the features and not the backend processing, business rules, data and non-functional mechanics that make a story or MVP potentially shippable. Technical debt can be intentional but you can jeopardize your agility when you unintentionally delay it until the end of the development cycle when it's very close to the time you wish to ship. Listen to today's podcast and learn more.
If you like this episode you’ll love
Episode Comments
Generate a badge
Get a badge for your website that links back to this episode
<a href="https://goodpods.com/podcasts/expresso-steam-makers-10-minute-daily-sip-stemulating-information-podc-84827/one-slide-at-a-time-episode-27-rainbow-and-circular-backlogs-15769994"> <img src="https://storage.googleapis.com/goodpods-images-bucket/badges/generic-badge-1.svg" alt="listen to one slide at a time episode #27 - rainbow and circular backlogs on goodpods" style="width: 225px" /> </a>
Copy