[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"term-b\u002Fbacklog":3,"related-b\u002Fbacklog":61},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":55,"sitemap":56,"stem":59,"subcategory":6,"__hash__":60},"terms\u002Fterms\u002Fb\u002Fbacklog.md","Backlog",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"The backlog is the master to-do list for a product — every feature, bug, and idea that hasn't been built yet, prioritised by importance. It's always growing, always being refined. The top items are crystal clear; the bottom items are rough ideas for someday.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A product backlog is an ordered list of everything that might be done in a product — features, bug fixes, technical debt, and research tasks. The Product Owner prioritises it. Items at the top are well-defined and ready for sprint planning; lower items may be rough epics.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Add it to the backlog and we'll prioritise it next quarter.\" \u002F \"The backlog has 300 items — time for a grooming session.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"general","The backlog is the master to-do list for a product — every feature, bug, and idea that hasn't been built yet, prioritised by importance.","beginner","md","b",{},true,"\u002Fterms\u002Fb\u002Fbacklog",[49,50,51,52,53,54],"User Story","Epic","Ticket","Issue","Sprint","Kanban",{"title":5,"description":41},{"changefreq":57,"priority":58},"weekly",0.7,"terms\u002Fb\u002Fbacklog","32RZpD4a1g9EEr6G19zV5DokTwD5619rg9uNWYBoe50",[62,65,68,71,74,77],{"title":50,"path":63,"acronym":6,"category":40,"difficulty":42,"description":64},"\u002Fterms\u002Fe\u002Fepic","An epic is a big chunk of work that's too large to finish in one sprint, so it gets broken down into smaller user stories.",{"title":52,"path":66,"acronym":6,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fi\u002Fissue","An issue is GitHub's word for a ticket — a filed report about a bug, feature request, or question.",{"title":54,"path":69,"acronym":6,"category":40,"difficulty":42,"description":70},"\u002Fterms\u002Fk\u002Fkanban","Kanban is a visual workflow system where tasks move through columns — To Do, In Progress, Done. Unlike Scrum with fixed sprints, Kanban is continuous flow.",{"title":53,"path":72,"acronym":6,"category":40,"difficulty":42,"description":73},"\u002Fterms\u002Fs\u002Fsprint","A sprint is a fixed time-box — usually 1-2 weeks — where a team commits to completing a specific set of tasks.",{"title":51,"path":75,"acronym":6,"category":40,"difficulty":42,"description":76},"\u002Fterms\u002Ft\u002Fticket","A ticket is a single unit of work in a project management tool — it could be a bug to fix, a feature to build, or a task to complete.",{"title":49,"path":78,"acronym":6,"category":40,"difficulty":42,"description":79},"\u002Fterms\u002Fu\u002Fuser-story","A user story is a tiny description of a feature from the user's perspective, written in plain English: 'As a user, I want to reset my password, so that I c...",1776518259358]