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.

Selected:PARA MethodSprint RetrospectiveStart Stop ContinueMad Sad Glad
Criterion
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h Setup, laufendUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-60 min30-60 min
Participantsdifferent
1Scrum Team3-123-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveImprovement actions, Team agreementsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
KnowledgeProductivityOrganization
RetrospectiveImprovementLearning
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods