david.delagneau
1ad707373a
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
1.0 KiB
1.0 KiB
type, project, status, systems, workstreams, people, related, tags, updated
| type | project | status | systems | workstreams | people | related | tags | updated | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| system | fidelity | active |
|
|
|
|
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, andPDIAP 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