Team | Dojo Consortium

Team agreement on conditions that must be met before work is considered complete, ensuring consistent quality standards

2 minute read

Team-agreed criteria that defines when work is ready to begin, helping manage uncertainty and set clear expectations

2 minute read

Reduce context switching and improve flow by limiting started-but-unfinished work, helping teams focus on collaboration and completion

2 minute read

Regular team practice for inspecting and adapting how work gets done, critical for continuous improvement and preventing entropy

5 minute read

Practices for managing team workflow, making work visible, and optimizing flow from backlog to done

4 minute read

Making work visible through visual workflow boards to increase ownership, accountability, and stakeholder transparency

2 minute read

Lean code review practices prioritizing small changes, team-wide capability, and fast feedback loops with review as second-highest priority

less than a minute

Team ownership model where everyone takes responsibility for code quality, reducing process overhead and improving delivery

less than a minute

Time the build stays broken before being fixed - measures team discipline and CI commitment

less than a minute

Breaking stories into smallest independently deployable changes that implement acceptance criteria and maintain flow

less than a minute

Tag: Team