david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
869 B
869 B
type, project, role, status, updated, tags
| type | project | role | status | updated | tags | ||
|---|---|---|---|---|---|---|---|
| person | fidelity | collaborator | active | 2026-04-16 |
|
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
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