Someone must have thought of this before but I have not read this anywhere so I thought I would jot it down. I recently ran a retrospective that I thought went really well, and apparently so did everyone else...
Measure with Check-in and Check-out
if you don't measure something how can you know if it improving? It is a staple of development so why shouldn't we apply it to our meetings as well. It is really easy.
- At the start of the retrospective ask everyone to write down a single word (or phrase) that sums up there feeling about how things are going
- Ask if anyone would like to share what they wrote down (can be more than one or even everybody)
- Do your retrospective
- Repeat step 1 at the end of the retrospective and see if anything changed
CategoriesAgile DevOps Leadership Life Project Management Software Development Tools
.NET .NET Core Agile API Design AppVeyor Architecture ASP.NET 5 ATDD Azure BDD C# C4 Cake Canopy CI Clean Code Client generated ID Collections Datadog DDD Design Patterns Diagrams Distributed Systems DNX Docker Extreme Programming F# Fennel FsAdvent FSX Functional Functional Modeling General Git Github Pages Hyper V Idempotent Java Learning c# Life Maven Meditation Messaging Mindfulness Modeling Morality MVC 6 Nuget Observability OOP OSX Paket Pascal Powershell Pretzel Productivity Programming Prometheus Reliability Science Selenium SOLID TDD Team Lead Temporal Modeling Testing Tutorial Ubuntu Unit Testing Visual Studio Visual Studio Online VS Code