Browse by letter:
A, B, C, D, E, F, H, I, K, L, M, O, P, Q, R, S, T, U, V, W,
or view all words

R

Retrospective

Retrospectives or ‘retros’ are regular sessions which help teams to reflect on the work that they have been doing. They also give the team chance to find ways to improve the way they work in future.

It is important that retros include a retrospective prime directive

Retros happen every two weeks. When teams are working in sprints they do a retrospective at the end of each sprint.

Retrospective prime directive

A retro facilitator refers to a retro prime directive at the start of a retro to help to set expectations. It helps create a positive culture where everyone can learn and improve without using blame.

Example of a retrospective prime directive:

‘Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.‘

The Prime Directive, Norm Kerth

Robotic Process Automation

Robotic process automation creates processes using software robots or artificial intelligence. It is sometimes called software robotics or just automation.

Roles and responsibilities

Teams often do an exercise to define each member's roles and responsibilities at the start of a new project. This could be part of an Inception or a Point of Departure exercise. A team member might have an overall role, like content designer, and do some service design and research if it helps to support the project.

Feedback.

Want to know more?

Let us know if we can help you or your team apply these ways of working.

Or perhaps let us know how we can improve this website for you.

Include this if you’d like a reply.


Index version 2 Index version 3