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 Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
90-180 min1-3 Tage3–4 h for initial assessment; preparation and deeper analysis additional30 min Setup, dann laufend
Participantsdifferent
4-121-41 or a small team; particularly suitable for 3–4 people1-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Planning Levels Map, Cadence Model, Planning Artifact InventoryArchitecture Views, Cross-view Notes, RationaleLean 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 checksRAID Log, Status Report Source
Tagsno overlap
CadenceGovernanceExecution
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskAssessmentLean
RiskTrackingStakeholdersGovernance
Add more methods