A practical guide to project-level documentation and governance from an enterprise architecture perspective. The author proposes a 'Just-in-Time' documentation approach organized into four areas: Strategy (business case, kick-off docs), Logs (open questions, decisions, constraints, meeting notes), Blueprints (AS-IS/TO-BE diagrams, data models), and Program Management (Gantt charts). The post critiques over-engineered frameworks like TOGAF while advocating for a minimal core set of documents — business case, decision/question logs, TO-BE diagram, and Gantt chart — that scale with project complexity. It also covers how to merge project documentation back into organizational knowledge at project close.
Table of contents
The problem with frameworks and articles like thisMy project toolkitThe most important onesMerging it back into the bigger documentationOrganic documentationSort: