CAPM Practice: Determine how project methodologies influence business analysis processes

'Minimum viable documentation' is a deliberate, context-specific decision: what documentation does this team in this context genuinely need? The answer varies — regulated industries need more; co-located agile teams may need less. The principle is intentionality, not elimination.

**Why not A:** Agile practitioners do produce documentation — the Agile Manifesto values working software over comprehensive documentation, not working software over any documentation. Minimum viable documentation is a deliberate choice about what documentation adds value, not an elimination of all documentation.

**Why not B:** One-page summaries are an arbitrary format constraint, not the principle behind minimum viable documentation. The appropriate documentation level varies by context — regulated industries may need extensive documentation while co-located teams may need less. The principle is intentionality, not a fixed format.

**Why not D:** Agile projects do not always produce the same documentation level as traditional projects. The whole point of minimum viable documentation is to calibrate documentation effort to what genuinely adds value in the team's specific context, which is typically less formal than traditional approaches.