40 lines
1.0 KiB
Markdown
40 lines
1.0 KiB
Markdown
---
|
|
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`
|