[{"data":1,"prerenderedAt":29},["ShallowReactive",2],{"$f16gax62jiq7ki":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"html":10,"headings":11},"\u002Fdocs\u002Fcontrol\u002Fretrospectives","Retrospectives","Each team looks back on its week and its quarter: what worked, what to change, and whether its charter still holds.",null,true,[],"\u003Ch2 id=\"why-a-retro\">Why a retro\u003C\u002Fh2>\n\u003Cp>\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fself-improvement\">Self-improvement\u003C\u002Fa> makes one task run better. It never asks whether the team should\nstill exist, or still do what its \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fteams\">charter\u003C\u002Fa> says. A retrospective is that second question, asked\non a cadence, by the team itself.\u003C\u002Fp>\n\u003Ch2 id=\"the-weekly-retro\">The weekly retro\u003C\u002Fh2>\n\u003Cp>Every team will run a short weekly retro, usually led by its team lead. Members do not meet: each writes structured\nanswers from the week's runs, and the lead brings them together.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Question\u003C\u002Fth>\n\u003Cth>What it asks\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Went well\u003C\u002Ftd>\n\u003Ctd>What worked this week?\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Went less well\u003C\u002Ftd>\n\u003Ctd>What did not?\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Learned\u003C\u002Ftd>\n\u003Ctd>What do we know now that we did not?\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Unclear\u003C\u002Ftd>\n\u003Ctd>What is still open?\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Actions\u003C\u002Ftd>\n\u003Ctd>What changes before next week?\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>What the team learned goes into its \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">memory\u003C\u002Fa>, where the retro's run is allowed to write. A\nquestion the lead cannot answer comes to you. Actions become work: a scheduled run, a task change, an issue.\u003C\u002Fp>\n\u003Cp>The weekly retro should take minutes, not become a project of its own.\u003C\u002Fp>\n\u003Ch2 id=\"the-quarterly-retro\">The quarterly retro\u003C\u002Fh2>\n\u003Cp>Once a quarter, the team will ask the larger questions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Is the charter still true?\u003C\u002Fli>\n\u003Cli>Is its metric the right one, with the right target?\u003C\u002Fli>\n\u003Cli>Should the team grow, shrink, split, or close?\u003C\u002Fli>\n\u003Cli>What should the rest of the company know?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The answers go into a brief for you. A charter rewrite, or closing a team, waits for your approval: a retro\nproposes it, and nothing changes until you say so.\u003C\u002Fp>\n\u003Ch2 id=\"after-a-retro\">After a retro\u003C\u002Fh2>\n\u003Cp>The lead posts what the rest of the company needs to know. Separate teams that stop telling each other what they\nlearned stop being one company.\u003C\u002Fp>\n\u003Ch2 id=\"until-then\">Until then\u003C\u002Fh2>\n\u003Cp>No retro runs today. A team lead or you can still run a review as an ordinary \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks\">task\u003C\u002Fa> on a\n\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules\">schedule\u003C\u002Fa>, with its questions in the task's skill.\u003C\u002Fp>\n",[12,17,20,23,26],{"id":13,"text":14,"level":15,"planned":16},"why-a-retro","Why a retro",2,false,{"id":18,"text":19,"level":15,"planned":16},"the-weekly-retro","The weekly retro",{"id":21,"text":22,"level":15,"planned":16},"the-quarterly-retro","The quarterly retro",{"id":24,"text":25,"level":15,"planned":16},"after-a-retro","After a retro",{"id":27,"text":28,"level":15,"planned":16},"until-then","Until then",1791124519607]