RETROSPECTIVES
CITATIONS IN THE BUTTONS BELOW
Embedded Files
Dictionary
ret·ro·spec·tive
/ˌretrəˈspektiv/
noun
plural noun: retrospectives
an exhibition or compilation showing the development of the work of a particular artist over a period of time.
"a Georgia O'Keeffe retrospective"
Choose languageAfrikaansAlbanianAmharicArabicArmenianAzerbaijaniBanglaBasqueBelarusianBosnianBulgarianBurmeseCatalanCebuanoChinese (Simplified)Chinese (Traditional)CorsicanCroatianCzechDanishDutchEsperantoEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekGujaratiHaitian CreoleHausaHawaiianHebrewHindiHmongHungarianIcelandicIgboIndonesianIrishItalianJapaneseJavaneseKannadaKazakhKhmerKinyarwandaKoreanKurdishKyrgyzLaoLatinLatvianLithuanianLuxembourgishMacedonianMalagasyMalayMalayalamMalteseMāoriMarathiMongolianNepaliNorwegianNyanjaOdiaPashtoPersianPolishPortuguesePunjabiRomanianRussianSamoanScottish GaelicSerbianShonaSindhiSinhalaSlovakSlovenianSomaliSouthern SothoSpanishSundaneseSwahiliSwedishTajikTamilTatarTeluguThaiTurkishTurkmenUkrainianUrduUyghurUzbekVietnameseWelshWestern FrisianXhosaYiddishYorubaZulu
What is a Sprint Retrospective?
What is a Sprint Retrospective?
Learn About the Sprint Retrospective Event
Learn About the Sprint Retrospective Event
As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
During the Sprint Retrospective, the team discusses:
What went well in the Sprint
What could be improved
What will we commit to improve in the next Sprint
The Scrum Master encourages the rest of the Scrum Team to improve its process and practices to make it more effective and enjoyable for the next Sprint. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done” if appropriate and not in conflict with product or organizational standards.
By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself. Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
Search all Resources related to Sprint Retrospectives.
https://www.scrum.org/resources/what-is-a-sprint-retrospective
Retrospective
Retrospective
From Wikipedia, the free encyclopedia
A retrospective (from Latin retrospectare, "look back"), generally, is a look back at events that took place, or works that were produced, in the past. As a noun, retrospective has specific meanings in medicine, software development, popular culture and the arts. It is applied as an adjective, synonymous with the term retroactive, to laws, standards, and awards.
A medical retrospective is an examination of a patient's medical history and lifestyle.
A retrospective exhibition presents works from an extended period of an artist's activity. Similarly, a retrospective compilation album is assembled from a recording artist's past material, usually their greatest hits. A television or newsstand special about an actor, politician, or other celebrity will present a retrospective of the subject's career highlights. A leading (usually elderly) academic may be honored with a Festschrift, an honorary book of articles or a lecture series relating topically to a retrospective of the honoree's career. Celebrity roasts good-naturedly mock the career of the guest of honor, often in a retrospective format.
A retrospective or retroactive award is one which is created and then awarded to persons who would have received it before. Alternatively, a slight change to the criteria of an existing award may result in retrospective awards being presented to persons who would have won the award under present rules. Comparatively few awards are presented retrospectively.
The term is used in situations where the law (statutory, civil, or regulatory) is changed or reinterpreted, affecting acts committed before the alteration. When such changes make a previously committed lawful act now unlawful in a retroactive manner, this is known as an ex post facto law or retroactive law. Because such laws punish the accused for acts that were not unlawful when committed, they are rare, and not permissible in most legal systems. More commonly, changes retroactively worsen the legal consequences (or status) of actions that were committed, or relationships that existed, by bringing it into a more severe category than it was in when it was committed; by changing the punishment or recompense prescribed, as by adding new penalties, extending sentences, or increasing fines and damages payable; or it may alter the rules of evidence in order to make exoneration more difficult than it would have been.
Conversely, a form of retrospective law commonly called an amnesty law may decriminalize certain acts. A pardon has a similar effect, in a specific case instead of a class of cases. An in mitius change may alleviate possible consequences for unlawful acts (for example by replacing the death sentence with lifelong imprisonment) retroactively. Finally, when a previous law is repealed or otherwise nullified, it is no longer applicable to situations to which it had been, even if such situations arose before the law was voided; this principle is known as nullum crimen, nulla poena sine praevia lege poenali.
This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (April 2017) (Learn how and when to remove this template message)
The term is also used in software engineering, where a retrospective is a meeting held by a project team at the end of a project or process (often after an iteration) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects. Retrospective can be done in many different ways.
In agile development, retrospectives play a very important role in iterative and incremental development. At the end of every iteration a retrospective is held to look for ways to improve the process for the next iteration.
In the context of scientific and technical standards, retrospectivity applies current norms to material that pre-dates new rules. An example of a retrospective or retroactive standard is the International Code of Zoological Nomenclature (ICZN Code), a convention which governs the formal scientific naming of animals, of which the 4th edition is effective since 2000. All previous editions of the ICZN Code, or previous other rules and conventions are disregarded today,[1] and the scientific names published in former times are to be evaluated only under the present edition of the ICZN Code.
The dictionary definition of retrospective at Wiktionary
Retrospective
Retrospective
Identify how to improve teamwork by reflecting on what worked, what didn’t, and why. We recommend running a Retrospective with your team every couple of weeks or at the end of a project milestone.
PREP TIME
15 MINS
RUN TIME
60 MINS
PEOPLE
4-8
Retrospectives in action
Retrospectives in action
A team's sticky notes from an offsite Retrospective.
This team used Confluence to summarize the conversation of their Retrospective.
A Retrospective over Zoom using Trello to set ground rules, add thoughts, and guide the discussion.
What you'll need
What you'll need
REMOTE
Video conferencing with screenshare
Digital collaboration tool (see templates)
IN-PERSON
Meeting space
Whiteboard, or large sheet of paper
Markers
Sticky notes
Timer
Optional templates
Optional templates
ATLASSIAN TEMPLATES
Confluence template
OTHER TEMPLATES
Instructions for running this Play
Instructions for running this Play
1. Prep 15 MIN
1. Prep 15 MIN
For remote teams, start by creating a new collaboration document, like a Confluence page or a Trello board. For help, see templates (above)
For in-person teams, find a whiteboard or large paper, and set out Post-It notes and markers in a meeting room.
On the page, board, paper, or whiteboard, create three columns with the headings “What we did well”, “What we can do better”, and “Actions”.
And, if possible, get a neutral third party to help facilitate the meeting. This will encourage greater participation and uncover more insights.
EXAMPLE: CONFLUENCE
Running this Play remotely? Use this free Retrospective template to guide the conversation and capture your session’s output.
Open in Confluence
2. Set the stage 5 MIN
2. Set the stage 5 MIN
Don’t make it personal, don’t take it personally
Listen with an open mind
Everyone’s experience is valid
Set the time period you’re discussing (last sprint, last quarter, entire project, etc.)
Focus on improvement, rather than placing blame
If you’ve run a Retrospective previously, quickly revisit the themes and actions from last time to build a sense of continuity.
TIP: CUSTOMIZE THIS LIST
Modify the rules to fit your team’s unique needs. Add anything you think will help your team improve.
TIP: CREATE A SAFE SPACE
Define how the information will be discussed after the Play. Will it be shared with leadership? Consider adopting the Chatham House Rule.
3. What we did well 15 MIN
3. What we did well 15 MIN
Using either a digital whiteboard or a physical one, have each team member write down what the team did well, one idea per note. Post the notes, and group similar or duplicate ideas together. Discuss each one briefly as a team.
4. What we can do better 10 MIN
4. What we can do better 10 MIN
Have everyone write down what they think can be improved, one idea per note. Post the notes, and group similar or duplicate ideas together. Discuss each theme as a team.
TIP: MAKE SURE ALL ARE HEARD
If the discussion is dominated by one or two people, the facilitator should step in and call on others before moving on.
5. Actions 10 MIN
5. Actions 10 MIN
Have everyone brainstorm actions that can be taken to improve problem areas, one idea per note.
Post the notes and group similar or duplicate ideas. Discuss each idea as a team, and assign owners to these actions and due dates as necessary.
TIP: UPDATE YOUR WORKFLOWS
If any of the action items have corresponding Jira issues, include links to them on the page so it's easy to see their status.
Incorporate actions from the retrospective into your day-to-day, whether it’s in stand-ups, or weekly team status updates.
Follow-up
Follow-up
Challenge takeaways
Challenge takeaways
Are follow-up tasks being completed, or forgotten? Are you getting to the root of your problems? Would a different set of activities help you dig deeper? Retrospectives can be customized—make it your own!
Variations
Variations
Past two-months map
Past two-months map
Create a timeline spanning the past two months and have team members call out significant events. Doing this at the start of the Play helps refresh everyone's memory and sets the stage.
Dot voting
Dot voting
If a lot of ideas emerge in the “Actions” category, vote on which ones you’ll immediately prioritize.
If you’re using Trello, have the team vote on the three ideas they’d like to see at the top of the list by adding their face to the card (shortcut: hover + space). Select owners for the top-voted items.
For in-person meetings, everyone grabs a marker and places a dot on their top three preferences. Tally up the dots and follow same step as above.
CONFIDENTIALITY / COPYRIGHT NOTICE: This site and my information and any attachments contains the PRIVILEGED AND CONFIDENTIAL INFORMATION of Fred Finkelstein & Irondesigner DBA / LLC mutually, Inc., its affiliated corporations or legal entities, and is intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail or invited to this site, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unlawful interception, dissemination, disclosure, printing or copying of this e-mail or site or any attachments is strictly prohibited under the Electronics Communication Privacy Act (ECPA), 18 USCA 2510, 18 USCA 2511, and any applicable laws. If you have received this e-mail or viewing this site in error, please delete or destroy it & close down, including all attachments or copies, and immediately notify us by e-mail at mechanicalengrg@gmail.com
Page updated
Google Sites
Report abuse