Retrospective
Agile Scrum

Retrospective

The aim of the retrospective is to discuss and plan possible improvements of quality and effectiveness for the team.
Read more
Get PDF
Tags
Agile Agile Retrospective Agile Retrospective Template image Infographic Picture Poster Retrospective Scrum Scrum Retrospective Sprint Retrospective Sprint Retrospective Meeting Sprint Retrospective Template What Is Sprint Retrospective What Is The Purpose Of The Sprint Retrospective
Article

Retrospective


  • The aim of the retrospective is to discuss and plan possible improvements of quality and effectiveness.
  • The focus of the retrospective is on the team creating the product and this event is for the team to inspect their performance.
  • The last iteration is inspected with regards to individuals, interactions, processes, tools, and their Definition of Done.
  • The most important findings should be addressed as soon as possible to get the advantages coming from the improvement right away.
  • During the retrospective, the three questions are usually discussed: what went well, what problems were encountered, and how those problems were or can be solved.
  • Do not assign blame, instead try to get to the origins and the roots of the problems, that were discovered.

Retrospective

Resources
scrumguides.org

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.