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.
This commit is contained in:
33
workspaces/fidelity/project-knowledge/04-people/quy-mai.md
Normal file
33
workspaces/fidelity/project-knowledge/04-people/quy-mai.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
type: person
|
||||
project: fidelity
|
||||
role: collaborator
|
||||
status: active
|
||||
updated: 2026-04-20
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
---
|
||||
# Quy Mai
|
||||
|
||||
## Role
|
||||
|
||||
Confirmed Scrum Master / contact point repeatedly involved in backlog and process management.
|
||||
|
||||
---
|
||||
|
||||
## Known Context
|
||||
|
||||
- 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`
|
||||
|
||||
---
|
||||
|
||||
## Guidance
|
||||
|
||||
- Treat Quy as an important source for process expectations, backlog cleanup, and story framing
|
||||
- When drafting notes or prompts, refer to Quy as Scrum Master rather than a generic stakeholder
|
||||
- If future context clarifies the formal title/team, update this file directly
|
||||
Reference in New Issue
Block a user