Build institutional memory, decision by decision.
Record architectural decisions (ADRs), problems, retrospectives, and learnings across the project lifecycle.
Project History
Why use it
Documented problems and retrospectives.
Timeline of the project's evolution.
Project History
Frequently asked questions
What is Project History for?
To preserve why decisions were made — ADRs, problems, learnings — so mistakes aren't repeated.
Where do retrospectives go?
Here, alongside sprint reviews and learnings, with a timeline view.
How is it different from Wiki?
Wiki is general docs; Project History is the chronological record of decisions and problems.
Keep exploring
Documentation Works well with
TREX / One platform. Many flows.
Start Free Ready to align strategy and execution?
Start free today. Invite your team whenever you're ready.