david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
fidelity-ai-workspace/workspaces/fidelity/project-knowledge/03-context/process/sprint-cadence.md
david.delagneau 1ad707373a Add daily logs and templates for project fidelity 
- 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.
2026-05-21 12:28:07 -06:00

1.5 KiB
Raw Permalink Blame History

type, project, status, people, related, updated, tags
type project status people related updated tags
process fidelity active
quy-mai
../process/index.md
../../04-people/quy-mai.md
2026-04-20
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.
Reference in New Issue View Git Blame Copy Permalink