diff --git a/project-knowledge/03-context/process/index.md b/project-knowledge/03-context/process/index.md index 186d155..25fe90d 100644 --- a/project-knowledge/03-context/process/index.md +++ b/project-knowledge/03-context/process/index.md @@ -29,3 +29,6 @@ Agent operating rules live in `agent-memory/`, not in this project vault. - [pull-requests.md](./pull-requests.md) PR template and framing notes for repositories such as `xflow-for-ios`. + +- [sprint-cadence.md](./sprint-cadence.md) + Fidelity-side Scrum cadence, ceremonies, sprint naming, and planning rhythm. diff --git a/project-knowledge/03-context/process/sprint-cadence.md b/project-knowledge/03-context/process/sprint-cadence.md new file mode 100644 index 0000000..669a136 --- /dev/null +++ b/project-knowledge/03-context/process/sprint-cadence.md @@ -0,0 +1,63 @@ +--- +type: process +project: fidelity +status: active +people: [quy-mai] +related: [../process/index.md, ../../04-people/quy-mai.md] +updated: 2026-04-20 +tags: + - process + - fidelity + - scrum + - sprint +--- + +# Sprint Cadence And Ceremonies + +## Goal + +Capture the Fidelity-side Scrum rhythm so work status, planning, and story timing are interpreted correctly. + +--- + +## Current Understanding + +- On the Fidelity side, Quy Mai acts as the Scrum Master. +- Quy manages the Scrum ceremonies. +- Confirmed ceremonies include: + - retrospective + - DSE / daily syncs + - sprint review + - sprint planning +- Retrospectives use Miro. +- Jira is the work-tracking system. + +--- + +## Sprint Model + +- Sprints are two weeks long. +- Sprint naming uses the `PDIAP 26QX.Y` pattern. +- The examples currently captured are: + - `PDIAP 26Q1.1` (`1/01` - `1/15`) + - `PDIAP 26Q1.2` (`1/15` - `1/29`) + - `PDIAP 26Q1.3` (`1/29` - `2/12`) + - `PDIAP 26Q1.4` (`2/12` - `2/25`) + - `PDIAP 26Q1.5` (`2/26` - `3/12`) + - `PDIAP 26Q1.6` (`3/12` - `3/26`) + - `PDIAP 26Q2.1` (`3/26` - `4/09`) + - `PDIAP 26Q2.2` (`4/09` - `4/23`) + +--- + +## Working Implications + +- Story timing and status should be interpreted in the context of the current two-week sprint. +- Quy is a key contact for ceremony timing, sprint structure, and Jira process expectations on the Fidelity side. +- When discussing planning or delivery windows, prefer the explicit sprint label when it is known. + +--- + +## Open Question + +- The corrected examples align with the expected quarter-based naming pattern: year + quarter + sprint number within that quarter. diff --git a/project-knowledge/03-context/systems/confluence.md b/project-knowledge/03-context/systems/confluence.md index b61427c..e34ff1a 100644 --- a/project-knowledge/03-context/systems/confluence.md +++ b/project-knowledge/03-context/systems/confluence.md @@ -3,13 +3,13 @@ type: system project: fidelity status: active systems: [] -workstreams: [] +workstreams: [consumer-integration] people: [] -related: [] +related: [jira] tags: - system - fidelity -updated: 2026-04-17 +updated: 2026-04-20 --- # Confluence @@ -17,6 +17,7 @@ updated: 2026-04-17 ## Role - Internal documentation/wiki surface used across Fidelity workflows. +- Commonly paired with Jira in the Fidelity-side delivery process, but Jira is the more central day-to-day work-tracking tool. --- diff --git a/project-knowledge/03-context/systems/index.md b/project-knowledge/03-context/systems/index.md index da951b7..5dc759d 100644 --- a/project-knowledge/03-context/systems/index.md +++ b/project-knowledge/03-context/systems/index.md @@ -2,7 +2,7 @@ type: system-index project: fidelity status: active -updated: 2026-04-16 +updated: 2026-04-20 tags: - system - fidelity @@ -45,6 +45,9 @@ tags: - [confluence.md](./confluence.md) Internal documentation/wiki surface. +- [jira.md](./jira.md) + Primary work-tracking system for stories, sprint state, and planning. + - [miro.md](./miro.md) Shared whiteboarding/collaboration tool. diff --git a/project-knowledge/03-context/systems/jira.md b/project-knowledge/03-context/systems/jira.md new file mode 100644 index 0000000..70a448e --- /dev/null +++ b/project-knowledge/03-context/systems/jira.md @@ -0,0 +1,39 @@ +--- +type: system +project: fidelity +status: active +systems: [] +workstreams: [consumer-integration] +people: [quy-mai] +related: [confluence, miro, ../process/jira-story-rules.md, ../process/sprint-cadence.md] +tags: + - system + - fidelity + - jira + - tracking +updated: 2026-04-20 +--- + +# Jira + +## Role + +- Primary work-tracking system used in Fidelity. +- Central system for stories, sprint organization, status tracking, and planning flow. + +--- + +## Stable Patterns + +- Fidelity-side Scrum work is organized in Jira. +- Sprint naming uses labels like `PDIAP 26Q1.1`, `PDIAP 26Q2.1`, and `PDIAP 26Q2.2`. +- Jira is part of the day-to-day delivery flow alongside DSE/daily syncs, sprint review, sprint planning, and retrospectives. +- Story IDs and approved titles should remain explicit because they are reused in standups, planning, and stakeholder communication. + +--- + +## Related Context + +- Sprint cadence and ceremonies: `../process/sprint-cadence.md` +- Story framing guidance: `../process/jira-story-rules.md` +- Scrum coordination context: `../../04-people/quy-mai.md` diff --git a/project-knowledge/04-people/quy-mai.md b/project-knowledge/04-people/quy-mai.md index 9d7939f..5fc3dfb 100644 --- a/project-knowledge/04-people/quy-mai.md +++ b/project-knowledge/04-people/quy-mai.md @@ -3,7 +3,7 @@ type: person project: fidelity role: collaborator status: active -updated: 2026-04-16 +updated: 2026-04-20 tags: - person - fidelity @@ -21,6 +21,8 @@ Confirmed Scrum Master / contact point repeatedly involved in backlog and proces - Repeatedly asked for clearer Jira/state management, points, and backlog hygiene - Often confirmed whether work should remain in backlog, be canceled, or be reframed as separate stories - Relevant for sprint structure, story cleanup, and expectation-setting around what counts as production or release-priority work +- Manages Fidelity-side Scrum ceremonies including retrospectives, DSE/daily syncs, sprint review, and sprint planning +- The Fidelity-side sprint cadence currently appears to be two weeks, with sprint names following examples like `PDIAP 26Q1.1` and `PDIAP 26Q2.1` --- diff --git a/project-knowledge/06-daily/2026-04-20.md b/project-knowledge/06-daily/2026-04-20.md index 2dfce90..7acc9aa 100644 --- a/project-knowledge/06-daily/2026-04-20.md +++ b/project-knowledge/06-daily/2026-04-20.md @@ -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. --- diff --git a/project-knowledge/07-maps/fidelity-apps.md b/project-knowledge/07-maps/fidelity-apps.md index 024b041..86a59f5 100644 --- a/project-knowledge/07-maps/fidelity-apps.md +++ b/project-knowledge/07-maps/fidelity-apps.md @@ -34,6 +34,7 @@ Independent notes for internal Fidelity apps and tools that appear repeatedly in ## Collaboration And Documentation - [Confluence](../03-context/systems/confluence.md) +- [Jira](../03-context/systems/jira.md) - [Miro](../03-context/systems/miro.md) - [Discourse](../03-context/systems/discourse.md) - [Slate](../03-context/systems/slate.md)