methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Paper illustration for Working Agreements.
Agile
Working Agreements
Paper illustration for Team Charter.
Facilitation
Team Charter
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths.When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend45-90 min2-4 h20-40 min initial, dann laufend
Participantsdifferent
3-10 (Scrum Team)3-123-123-15
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalWorking Agreements, Team Norms, Review CadenceTeam Charter, Working Norms, Role NotesROAM Board, Owner List
Tagsno overlap
AgileIterationCadence
TeamCollaborationAgile
TeamAlignmentCollaboration
RiskAgileTrackingAlignment
Add more methods