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 Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Working Agreements.
Agile
Working Agreements
Paper illustration for Team Charter.
Facilitation
Team Charter
Purposedifferent
When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
60-90 min pro Feature20-40 min initial, dann laufend45-90 min2-4 h
Participantsdifferent
3-63-153-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Example Table, Acceptance TestsROAM Board, Owner ListWorking Agreements, Team Norms, Review CadenceTeam Charter, Working Norms, Role Notes
Tagsno overlap
AgileRequirementsExamplesBehavior-Driven Development
RiskAgileTrackingAlignment
TeamCollaborationAgile
TeamAlignmentCollaboration
Add more methods