Technical Backlog: An Instruction Manual
summary
Covers how to create and manage a technical backlog for software projects, including which technical tasks to record and how to prioritize and integrate them with product work. Describes practical rules and processes for maintaining the backlog so engineering debt and infrastructure work are visible and actionable.
AI-written summary · about
chapters (8)
- 0:00Technical backlog intro
- 3:33Non-functional requirements
- 9:13Backlog vs technical debt
- 13:04Product vs technical split
- 16:54Backlog elements
- 23:22Backlog sources
- 26:34Selling to team
- 30:56Prioritization & sprints
related talks
56mHow to Work with the Backlog
01h 02mBacklog.md Hands On
01h 36mWorkshop: Tackling Technical Debt: An Analytical Approach
44mWriting Technical Documentation in a Lean Style
35mTechnical Debt: When Interest Eats Your Code
25mTechnical Writing for Developers and Engineers
42mSlaying the Backlog Beast: A #NoBacklogs Approach to Product Management
42mTechnical Debt - Why the Term Causes More Confusion than Clarity
