Add Tradon development backlog workflow

This commit is contained in:
GiorgioCALLIGARO
2026-05-07 18:01:33 +02:00
parent 0be69bc92a
commit 9c791e394d
7 changed files with 577 additions and 13 deletions

View File

@@ -0,0 +1,38 @@
# Tradon Development Backlog
This folder converts assessed Tradon gaps into development backlog items.
The backlog is downstream from:
1. target report specifications in `Reports/`;
2. incoming GAP analysis files retained in `Assessments/Tradon/<REPORT_CODE>/source_documents/`;
3. structured assessment files in `Assessments/Tradon/<REPORT_CODE>/`.
Backlog items should be precise enough to drive development, but they should not invent source tables, SQL joins or implementation architecture before the relevant decisions are confirmed.
## Item lifecycle
| Status | Meaning |
| --- | --- |
| `Draft` | Candidate item derived from an assessment gap |
| `Blocked` | Requires a pending business, mapping or architecture decision |
| `Ready` | Scope and acceptance criteria are clear enough for development |
| `In Progress` | Development work has started |
| `Ready for Review` | Implementation is available for functional or technical review |
| `Done` | Implemented, tested and accepted |
| `Deferred` | Valid gap, not retained for the current delivery scope |
## Required fields
Each item should include:
- backlog ID;
- source report;
- source gap or assessment reference;
- linked open point or decision;
- development scope;
- out of scope;
- acceptance criteria;
- validation or reconciliation checks;
- priority;
- status.