feat: Update standup and work item documentation for clarity and story prioritization

This commit is contained in:
2026-04-10 07:42:03 -06:00
parent dcd2bcf3cc
commit 26f54ed302
6 changed files with 47 additions and 6 deletions

View File

@@ -9,6 +9,7 @@
- Created `PDIAP-15836` for dismissal delegate lifecycle sequencing in pure SwiftUI (`8` points)
- Aligned `PDIAP-15838` scope with REST migration cleanup and feature-flag removal
- Confirmed XFlowViewMaker `0.5.0` is already in Fid4
- Updated the root cause document for the AccountLink dismissal sequencing issue tied to `PDIAP-15836` and got approval on the proposed wording
---
@@ -26,6 +27,7 @@
- Prepared clearer wording for Jeff
- Focused on context, observation, and action instead of vague comparison language
- Proposed a root cause document update and got confirmation on the revised wording
---

12
ai/logs/2026-04-10.md Normal file
View File

@@ -0,0 +1,12 @@
# 2026-04-10
## Clarification
- `PDIAP-15838` should not be framed as directly tied to the UIKit-removal spike.
- Avoid wording that implies `PDIAP-15838` is dependent on or part of the dismissal-sequencing / UIKit-removal spike.
- Standups should prioritize updates directly tied to active work items and omit side questions such as version reminders that were only for internal context.
- Current focus for today is to finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately.
- Omit standup items that are not directly related to a story.
- Use the approved title `Remove Apollo for iOS` for `PDIAP-15838`.
- When a documentation or root cause update directly supports a story, report it under that story instead of as a separate standup item.
- In standups, format Jira references as `ID - Title` or `ID Title`, not `ID, Title`.

View File

@@ -7,6 +7,7 @@
- Debug Discourse and AO issues
- Prepare better updates for the current manager or stakeholder through Mattermost
- Follow up on `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838`
- Finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately
---
@@ -25,8 +26,17 @@
## Communication Priorities
- Standups should reflect the latest technical state, not generic progress
- Standups should prefer updates directly tied to active work items over one-off memory refreshes or side questions
- Standups should include story titles whenever a reported update maps to a Jira item
- Standups should use bullet points for each item, but avoid dash-separated title formatting inside the sentence body
- When pairing a Jira ID with a title in standups, prefer a simple hyphen after the ID or omit punctuation instead of using commas
- Standups should omit side questions or manager-only context refreshes unless they materially changed story work
- If a root cause document or other documentation update directly supports a story, it should be reported under that story instead of as a separate standalone item
- Standups should omit items not tied to a story unless they are real blockers
- Manager updates should be short, precise, and natural in English
- Mattermost messages should make scope and next action explicit
- Standups should be written as David's external progress report and should not mention Jeff by name
- Standups should never mention Mattermost because it is internal-only communication
---

View File

@@ -7,10 +7,10 @@ Update it only with explicit, project-relevant information that is useful for fu
## Current
- `PDIAP-15765` - AO DOB field error not showing investigation
Current note: issue was moved back to In Progress temporarily and should move to Done after the new sprint starts.
Current note: root cause was documented; the DOB validation issue was confirmed on TeenIdentityCheck for authenticated users, and Jeff approved moving the story to Done once the new sprint starts.
- `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
Current note: story created, sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, and meant to cover SwiftUI dismissal sequencing validation.
Current note: story came out of the AccountLink root cause investigation and related root cause document update; it was sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, and is meant to cover SwiftUI dismissal sequencing validation.
- `PDIAP-15838` - REST deprecation / remove GraphQL networking layer
Current note: approved at 8 points to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains.
- `PDIAP-15838` - Remove Apollo for iOS
Current note: approved at 8 points; description and ACs were filled in and Jeff approved the scope to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains.