[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"term-s\u002Fsprint-archaeology":3,"related-s\u002Fsprint-archaeology":60},{"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":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Fs\u002Fsprint-archaeology.md","Sprint Archaeology",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",{},"You open a ticket from four sprints ago trying to figure out why a feature works the way it does, and the description just says 'per discussion.' There's no discussion linked. There's no discussion anyone remembers. Sprint archaeology is digging through old boards, closed tickets, and half-finished comment threads hoping to unearth the actual reason a decision was made, like an archaeologist reading pottery shards instead of a decision record.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Sprint archaeology is the practice of investigating historical sprint boards, closed tickets, and past PR discussions to reconstruct the reasoning behind an existing implementation, usually because the decision was never formally documented. It's a common time sink on teams without disciplined architecture decision records or changelogs, and it tends to worsen the longer a project runs without one.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"I spent the morning on sprint archaeology trying to figure out why this flag exists.\" \u002F \"Save someone future sprint archaeology, write the why in the ticket, not just the what.\"",{"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},"vibecoding","You open a ticket from four sprints ago trying to figure out why a feature works the way it does, and the description just says 'per discussion.","beginner","md","s",{},true,"\u002Fterms\u002Fs\u002Fsprint-archaeology",[49,50,51,52,53],"Architecture Decision Record","Tribal Knowledge","Ticket","Backlog","Documentation",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fs\u002Fsprint-archaeology","WOotv86rKExo-kGG8VevnhQ9PjywKgunrB1eivtoCUM",[61,66,69,72,75],{"title":49,"path":62,"acronym":6,"category":63,"difficulty":64,"description":65},"\u002Fterms\u002Fa\u002Farchitecture-decision-record","general","intermediate","An ADR documents WHY you made a technical decision, not just what you decided. Why PostgreSQL over MongoDB? Why microservices over monolith?",{"title":52,"path":67,"acronym":6,"category":63,"difficulty":42,"description":68},"\u002Fterms\u002Fb\u002Fbacklog","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.",{"title":53,"path":70,"acronym":6,"category":63,"difficulty":42,"description":71},"\u002Fterms\u002Fd\u002Fdocumentation","Documentation is written explanation of how your code works and why.",{"title":51,"path":73,"acronym":6,"category":63,"difficulty":42,"description":74},"\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":50,"path":76,"acronym":6,"category":40,"difficulty":42,"description":77},"\u002Fterms\u002Ft\u002Ftribal-knowledge","Tribal knowledge is the stuff that only exists in people's heads — the undocumented rules, workarounds, and 'you just have to know' context that's never wr...",1792528125995]