View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ScrumRequest for CommentsLASR (Lightweight Approach for Software Reviews)Assumption Surfacing
| Criterion | ![]() Agile Scrum | ![]() Architecture Request for Comments | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-20 Reviewer | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | AgileIterationCadence | ArchitectureDecisionAsyncGovernance | ArchitectureQualityRiskAssessmentLean | AssumptionsRiskDecisionDiscovery |



