Retrospective
A retrospective is a structured team meeting at the end of a sprint or project where participants reflect on what went well, what could be improved, and what specific changes to make in the next cycle.
理解する Retrospective
Retrospectives are one of Scrum's five events, held at the end of each sprint. They embody the agile principle of empirical improvement — regularly stepping back to examine the process itself, not just the work output. A well-run retrospective creates psychological safety for honest feedback and produces specific, actionable commitments to change. The classic retrospective format is 'Start, Stop, Continue': what should we start doing? What should we stop doing? What should we continue doing? Many other formats exist — the '4 Ls' (Liked, Learned, Lacked, Longed For), Mad/Sad/Glad, and the Sailboat — each designed to elicit different types of reflection. Retrospective effectiveness degrades when teams skip them under pressure, when feedback doesn't feel safe, or when action items from previous retrospectives aren't followed up on. Facilitating a good retrospective is a skill that significantly affects team culture and continuous improvement capacity. AI tools can support retrospectives by aggregating quantitative data (velocity trends, defect rates, PR cycle times) that provides an objective picture alongside the qualitative team discussion, and by tracking action items from past retrospectives to ensure follow-through.
GAIAの活用方法 Retrospective
GAIA can prepare retrospective inputs by pulling sprint metrics (velocity, completed vs. planned tickets, PR review times, blockers encountered) from connected tools before the retro meeting. GAIA also tracks action items from past retrospectives and surfaces their completion status at the start of each new retro.
関連概念
Scrum
Scrum is an agile framework for managing complex, adaptive work through iterative cycles called sprints, with defined roles (Product Owner, Scrum Master, Development Team) and recurring ceremonies that promote transparency, inspection, and adaptation.
Sprint
A sprint is a fixed-length iteration (typically 1-2 weeks) in agile development during which a team selects, plans, and completes a defined set of work toward a product or project goal.
Kanban
Kanban is a project management methodology that visualizes work as cards moving through defined stages on a board, with limits on work-in-progress to maintain flow and identify bottlenecks.
ワークフロー自動化
ワークフロー自動化とは、繰り返し発生する業務プロセスやタスクをテクノロジーの力で自動的に実行し、手作業やヒューマンエラーを減少させる仕組みです。
OKRs (Objectives and Key Results)
OKRs (Objectives and Key Results) is a goal-setting framework in which organizations and individuals define ambitious qualitative objectives and measurable quantitative key results to track progress toward them.
