{"id":5003094,"date":"2015-12-16T21:05:56","date_gmt":"2015-12-17T05:05:56","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&p=5003094"},"modified":"2023-03-08T16:00:13","modified_gmt":"2023-03-09T00:00:13","slug":"heartbeat-retrospective","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/heartbeat-retrospective\/","title":{"rendered":"Heartbeat Retrospective"},"content":{"rendered":"
\n
\n

The team meets regularly, usually adhering to the rhythm of its iterations, to explicitly reflect on the most significant events to have occurred since the previous meeting, and take decisions aiming at remediation or improvement.<\/p>\n

This is often a facilitated<\/a> meeting following a set format. Several distinct formats have been described, depending in large part on the time set aside for the meeting, typically between one and three hours. One important reason to use a facilitated format is to give all team members an opportunity to speak up.<\/p>\n

Also Known As<\/h2>\n

The term \u201cretrospective\u201d, popularized by Norm Kerth (see below), has gained favor in the Agile community over better-known ones such as \u201cdebriefing\u201d or \u201cpost-mortem\u201d, for its more positive connotations.<\/p>\n

This is also known as the \u201csprint retrospective\u201d, or \u201citeration retrospective\u201d, often abbreviated, e.g. \u201csprint retro\u201d.<\/p>\n

The term \u201creflection workshop\u201d from Alistair Cockburn is encountered less often, though it appears to have influenced the Agile Manifesto\u2019s<\/a> wording of the corresponding principle.<\/p>\n

Common Pitfalls<\/h2>\n