gainklion.blogg.se - Agile retrospective ideas

#Agile retrospective ideas how to#

One team’s iteration retrospective results It can be conducted fairly easily, making all accomplishments and challenges visible, as illustrated in Figure 1. The last is a conventional method, in which the Scrum Master simply puts up three sheets of flipchart paper labeled ‘What Went Well’, ‘What Didn’t’, and ‘Do Better Next Time’, and then facilitates an open brainstorming session. Simple – Open a discussion and record the results under three headings.

#Agile retrospective ideas how to#

Rating – Rate the iteration on a scale of one to five, and then brainstorm how to make the next one a five.

Conceptual – Choose one word to describe the iteration.

Appreciation – Note whether someone has helped you or helped the team.

Individual – Individually write Post-Its and then find patterns as a group.

There are several popular techniques for eliciting subjective feedback on the success of the iteration (also see, ,, ): The Innovation and Planning (IP) Iteration is a great time to create opportunities for teams to advance their skills in these new domains. Lean-Agile Leaders are responsible for preserving and protecting the time teams will need during each Program Increment (PI) to focus on cultivating these skills, in addition to delivering new features.

Building telemetry and recovery techniques into systems.Decoupling deployment from release (see Release on Demand).Improving architecture and design quality (see Architecture and Design Quality section of Built-In Quality).Test automation (including Test-Driven Development and Behavior-Driven Development) and Continuous Integration.Since many improvement items have a significant scope, the team should divide them into smaller improvement stories, so that they can focus on what they can improve during subsequent iterations.Īs organizations begin implementing DevOps and a Continuous Delivery Pipeline, Agile teams will have a robust list of improvement opportunities, including but not limited to:

Qualitative review – First the team reviews the improvement stories they had identified in the prior retrospective, and then analyzes the current process, with a focus on finding one or two things they can do better in the next iteration.

This data is also the context for the qualitative section that follows. Examples might include team velocity, number of stories delivered, defects addressed, capacity allocation across new work and maintenance and automated test coverage. Agile teams collect and apply iteration metrics for visibility and to help with process improvement.

Quantitative review – The team assesses whether they met the Iteration Goals and this is a binary measure: yes or no.

The team conducts the retrospective in two parts: The whole team participates in the retrospective, with the Scrum Master facilitating and applying the tools and processes for data collection and problem-solving. And it helps ensure that every iteration yields some small improvements.

This helps instill the concept of relentless improvement-one of the pillars of the SAFe House of Lean-in the individuals and the team. The iteration retrospective is used by Agile teams to reflect on the iteration just completed and to derive new ideas to improve the team’s process. When issues have been identified, root cause analysis is performed, potential corrective actions are discussed, and improvement Stories are entered into the Team Backlog. The qualitative part discusses the team practices and the specific challenges that occurred during the last iteration or two. The quantitative review gathers and evaluates any metrics the team is using to measure its performance. Timeboxed to an hour or less, each retrospective seeks to uncover what’s working well, what isn’t, and what the team can do better next time.Įach retrospective yields both quantitative and qualitative insights. The Iteration Retrospective is a regular event where Agile Team members discuss the results of the Iteration, review their practices, and identify ways to improve.Īt the end of each iteration, Agile teams that apply ScrumXP (and many teams who use Kanban) gather for an iteration retrospective. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.