ImprovTeam

Team sessions

Sessions that use your work, not a case study

Facilitated, practical sessions for software teams. The material is your backlog, your code and your habits.

Illustrative image: city view through a large window with a plant

Common themes

  • Flow: why work waits, and how to keep it moving
  • Slicing: breaking work into pieces that can actually finish
  • Quality: tests, reviews and the habits that prevent rework
  • Planning: forecasts the team can stand behind
  • Legacy code: making safe changes to code nobody likes
  • Onboarding: helping new joiners contribute sooner

What a session is not

It is not a lecture, an assessment of individuals or an accredited course. Nobody receives a certificate. It is a facilitated working session where the team tries changes on real work and decides what to keep.

We plan each session with the team lead, run it, write up the agreements and check in a few weeks later.

Quick team check

For each statement, choose how true it is for your team today.

Everyone could explain this sprint or cycle goal in one sentence
Work items are small enough to finish in a couple of days
Code review happens within a day of being requested
The team decides how it works, not only what it works on
A bug found in production leads to a change in how we work
New joiners ship something useful in their first fortnight

Answer the statements to see where a session would probably focus.