feat: Add sprint cadence documentation and update related system references
This commit is contained in:
@@ -33,6 +33,9 @@ updated: 2026-04-20
|
||||
|
||||
- The immediate priority is no longer closeout work on the completed stories.
|
||||
- The immediate priority is to investigate why REST is not activating.
|
||||
- David clarified additional Fidelity-side process context: Quy acts as Scrum Master, manages retrospectives, DSE/daily syncs, sprint review, and sprint planning, retrospectives use Miro, Jira is the tracking system, and the Fidelity-side sprint cadence is two weeks with labels like `PDIAP 26Q1.1` and `PDIAP 26Q2.1`.
|
||||
- David corrected the Q2 sprint examples: `PDIAP 26Q2.1` is `3/26 - 4/09`, and `PDIAP 26Q2.2` is `4/09 - 4/23`.
|
||||
- David clarified that Jira should be represented as a first-class Fidelity tool/system because it is used more heavily than Confluence in day-to-day work tracking.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user