methodatlas
All topicsTopic

team

15 methods with this tag.

Related topics
Operations

Accountability Ladder

Turns workflow, data, causes, and improvements into a tangible result by describing the situation, identifying the current accountability level, and agreeing on follow-up.

Core question: Which stage of the ladder does the behavior in this concrete situation sit on, and which conditions would enable a step upward?

Operating practiceLowWorkshop + async
20-45 min
1-8

Run sheet · visual · session plan

Agile

Start Stop Continue

Turns backlog, sprint work, and team flow into a tangible result by setting context and timeframe, collecting start ideas, and prioritizing actions.

Core question: What should the team start, stop and deliberately continue to work noticeably better?

Facilitation methodLowWorkshop
30-60 min
3-12

Run sheet · visual · session plan

Agile

4Ls Retrospective

Turns backlog, sprint work, and team flow into a tangible result by setting the timeframe, collecting liked and learned items, and selecting actions.

Core question: What worked well, what did the team learn, what was missing, and what does the team want for the future?

Facilitation methodLowWorkshop
45-75 min
3-12

Run sheet · visual · session plan

Agile

Sailboat Retrospective

Turns backlog, sprint work, and team flow into a tangible result by defining the destination island, collecting drivers and anchors, and agreeing on actions.

Core question: What moves the team toward the goal, what holds it back, what risks lie ahead, and which actions follow?

Facilitation methodLowWorkshop
45-90 min
4-12

Run sheet · visual · session plan

Agile

Starfish Retrospective

Turns backlog, sprint work, and team flow into a tangible result by explaining five categories, collecting inputs, and formulating experiments.

Core question: Which practices does the team keep exactly as they are, reduce, strengthen, start anew, and stop completely?

Facilitation methodLowWorkshop
45-90 min
4-12

Run sheet · visual · session plan

Facilitation

Team Charter

Turns group input, selection, and decision into a tangible result by clarifying team purpose, capturing goals and stakeholders, and reviewing the charter over time.

Core question: Why does the team exist, how does it measure success, and how does it collaborate so everyone knows what to expect from each other?

Operating practiceMediumWorkshop
2-4 h
3-12

Run sheet · visual · session plan

Agile

Working Agreements

Turns team flow, expectations, and delivery rhythm into a tangible result by clarifying work context, collecting expectations, and setting a review cadence.

Core question: Which concrete behavior expectations make collaboration easier, and which of them does the team want to commit to?

Operating practiceLowWorkshop
45-90 min
3-12

Run sheet · visual · session plan

Facilitation

Responsibility Poker

Turns group input, selection, and decision into a tangible result by choosing tasks or decisions, explaining the responsibility scale, and capturing the agreement.

Core question: What expectations do team members have for responsibility per task, where do they differ, and what agreement do we make?

Facilitation methodLowWorkshop
45-90 min
3-10

Run sheet · visual · session plan

Facilitation

Delegation Poker

Turns group input, selection, and decision into a tangible result by collecting decision areas, explaining delegation levels, and capturing the agreement.

Core question: Which delegation degree per decision area matches maturity and context, and which differences between lead and team do we need to negotiate?

Facilitation methodLowWorkshop
45-90 min
3-10

Run sheet · visual · session plan

Facilitation

Expectation Mapping

Turns group input, selection, and decision into a tangible result by clarifying stakeholders and scope, collecting expectations silently, and deriving agreements.

Core question: Which expectations do participants bring to outcome, collaboration, and behavior, where do they differ, and which agreements resolve the differences?

Facilitation methodLowWorkshop
45-90 min
3-12

Run sheet · visual · session plan

Agile

Planning Poker

Turns backlog, sprint work, and team flow into a tangible result by presenting the item, clarifying questions, and discussing deviations before estimating again.

Core question: How large is this item relative to our reference stories, and which assumptions or risks drive variance within the group?

Decision methodLowWorkshop + async
2-5 min je Item
3-9

Run sheet · visual · session plan

Team Design

Team API

Moves team boundaries, interfaces, and collaboration toward a concrete result through "provide the template", "clarify responsibilities and non-responsibilities", and "anchor it visibly in the wiki".

Core question: What does our team offer other teams as service, how do they interact with us, and what can they expect?

Operating practiceLowWorkshop + async
Half day initial, dann laufend
Ein Team plus Stakeholder

Run sheet · visual · session plan

Team Design

Team Cognitive Load Assessment

Moves team boundaries, interfaces, and collaboration toward a concrete result through "explain the scale and categories", "run an anonymous team survey", and "derive and track actions".

Core question: How high is our team's cognitive load in three categories, and which structural measures reduce it?

Operating practiceMediumWorkshop + async
60-90 min
3-12

Run sheet · visual · session plan

Team Design

Team Topologies Interaction Modes

Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare the team list", "explain the three modes with examples", and "document agreements per pair".

Core question: Which interaction mode fits per team pair, and how do we agree modes bindingly to reduce interface friction?

Mapping toolMediumWorkshop
Half day
Team-Leads plus Architecture

Run sheet · visual · session plan

Team Design

Spotify Model Mapping

Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare a template with the four structures", "place current teams as squads", and "derive actions".

Core question: How is our engineering org actually structured into squads, tribes, chapters and guilds, and where do friction or gaps emerge?

Mapping toolMediumWorkshop
90-180 min
5-15

Run sheet · visual · session plan