# TDP - PM Coverage - Bridge Plan
## Overview
This document serves as a guide post for the coverage plan and break up of responsibilites relating to management of the TDP team and associated workflows.

*Steve jumping into: Prod sync, retro, weekly check-in w/ dev team*

---
## Sections
### ***Daily Stand Up***
**Owner:** Miles

**Current State:** Daily stand up to discuss workflows completed the prior day, planned work for the current day, call out any blockers to progress and align on priorities as a greater team.

**Key considerations:**
- Miles to facilitate overall flow, Andrew to lead Dev discussion / implications and Miles to lead UX
- UX Tickets, traced via Miles to ensure relevant updates to all in progress work
- Dev Tickets, traced via Andrew to ensure relevant updates to all in progress work

**Resources:**
- [Sprint Board - primary, follow along to ensure update for each ticket](https://app.zenhub.com/workspaces/sprint-board-5f18ab06dfd91c000f7e682e/board)
- [Product Board](https://app.zenhub.com/workspaces/product-board-5f2c6cdc7c0bb1001bdc43a5/board)
---
### ***Backlog Refinement***

**Owners:** Jan, Andrew (support and prioritization), Eric (support + RM management)

**Current State:** Cross-function cadence to review new tickets, refresh tickets aging in backlog before pulling into the next sprint, and allow for technical walk-on discussions with key stakeholders.

General flow:
- New Tickets: review **Product Board** and annotate any newly opened tickets as agenda items
- For each Ticket, notate:
- Discussion: Allow ticket opener to introduce ticket, ask key questions to the audience and discuss amongst the team.
- Priority: Given the current push to parity ahead of the approaching deadline, we have to ruthlessly de-prioritize any item that does not directly contribute to achieving parity or unblocking a parity workflow.
- Action: Note the next action assocaited, is it high priority enough to slot in the near term backlog (+add a sticky to RM), is it continuing to collect requirements (leave as WIP/unrefined), is it refined but not high enough priority to be pulled in (refined backlog) etc.

**Key Considerations:** Maintain exteremly high bar for adding scope / folding in new tickets, we need to remain hyper focused on achieving parity and completing the parsing engine asap. Andrew to help guide conversations as well.

**Output:**
- [ ] Document triage of new tickets, discussion on current tickets and any walk on items in TDP Notebook
- [ ] Update Product board (move tickets to appropriate columns)
- Zenhub is a little funky, after updating product board, check out sprint board to ensure everything is aligned

**Resources:**
- [TDP Notebook -> Product -> Backlog](https://gorafttech.sharepoint.com/sites/TDRSResearchDesign/_layouts/15/Doc.aspx?sourcedoc={c9d41a72-bff8-4eba-b245-bb04ba265e12}&action=edit&wd=target%28Product%20Notes.one%7C02afc3cb-1bf8-4117-bd72-1f077c416961%2FBacklog%20Refinement%7Cae1c83b0-c672-4013-b5bd-94518d4ef1c8%2F%29&wdorigin=NavigationUrl)
- [Sprint Board](https://app.zenhub.com/workspaces/sprint-board-5f18ab06dfd91c000f7e682e/board)
- [Product Board](https://app.zenhub.com/workspaces/product-board-5f2c6cdc7c0bb1001bdc43a5/board)
- Discover/triage new tickets from this board

---
### ***Roadmap Management***
Owners: Eric, Andrew for oversight/support

Current State: Planned work to take TDP into parity+ completion is mapped out and we are on track to deliver. Andrew to assist in triaging new tickets to consider, at a high-level we have to be extremely cautious of expanding scope and compelting any work not aligned completion in the next 4-5 weeks.

Resources:
- [TDP Roadmap - 60 day bridge board](https://app.mural.co/t/raft2792/m/raft2792/1675268418098/d56ec0d5415d8cda9c6ae9cae61154bcc4e74bba?sender=ue018dddfca540564eae53907)

---
### ***End of Sprint Ceremony (Review, Retro, Demo, Planning)***
**Owners:** Miles, Andrew to assist on Dev workflows

**Current State:** The TDP team is experienced in our review/retro/planning process and operating at a largely self sufficient model.

**Key Considerations:**
- **Sprint Review:** Walk through the Sprint Board and have every ticket recapped by owner.
- Recap: Background of ticket, work completed, work remaining, expected cycles left.
- Fold tickets with remaining work into next sprint plan. Miles will manage UX sprint plan, Andrew will manage dev sprint plan; coordination between UX-Dev will occur in 1:1 planning session ahead of each retro.
- **Sprint Summary / Velocity**
- Velocity
- Calculate Dev velocity separately and report in review and summary document
- **Demo**
- Internal
- Demo all work completed within the sprint, Andrew to coordiante with Devs day prior to end of sprint, Miles to lead workflow for UX
- External
- Align with OFA on items to present in external demo cadence
- Lauren: TDP IPT Cadence w/ OCIO ended / new cadence conflicts w/ external demo every other week - can adjust external to every other week demo
- [ACTION] - alter invite to accomodate
- **Retro**
- Walk through Retro mural as team: check-in, ice-breaker, (+7min to timer) -> complete Retro verticals via stickies, talk through 1x1 and distill takeaways into action items.
- Review previous retro's action items to discuss if complete or still in-progress
- Check out
- **Sprint Planning**
- Walk-through sprint planning document, Andrew to lead Dev and Miles to lead UX.
- Review planned work and stretch work table to ensure all members are comfortable with what is being asked of them.

**Output:**
- [ ] Document Sprint Review notes in .md and upload to GitHub -> documents, see example resources
- [ ] Sprint Planning Documentation | UX (Miles), Dev (Andrew)
- [ ] Adjust cadence ownership -> Miles

**Resources:**
- [Mural template](https://app.mural.co/t/raft2792/m/raft2792/1655335773503/c2923faa1bb4c920ba379968d559294b1e7d1b57?sender=ue018dddfca540564eae53907) (duplicate for each cadence)
- Retro Notes aggregation
- [Sprint Review document example](https://github.com/raft-tech/TANF-app/blob/develop/docs/Sprint-Review/sprint-81-summary.md)
- [Sprint Summary file path](https://github.com/raft-tech/TANF-app/tree/develop/docs/Sprint-Review)
- [Sprint Planning document template](https://hackmd.io/vvjNiwGTSLyuUnyvd1dHXA)
- UX -> Miles inputs
- Dev -> Andrew inputs

---
### ***Dev Office Hours***
Owners: Jan as meeting driver, Andrew as Tech lead

Current State: Agenda driven sync to promote discussion across development team members and enable a cadence for ad hoc pairing / troubleshooting.

Resources:
- OH Cadence (M/W/F | 2:00-3:00pm EST) managed by Jan
- Office Hours Agenda (see e-mail cadence)

Action:
- Loop in Miles on invite

---
### ***X-Product Sync***
Owner: Miles - Andrew

Current State: Weekly sync to discuss high-priority workflows from previous and upcoming weeks. Steve to establish separate 1:1 cadence with Lauren, bi-weekly initially with opportunity to increase to weekly if preferable.

Output:
- [ ] Notes collected in onenote
- [ ] Adjust ownership to Miles for cadence

Resource:
- [Team OneNote](https://gorafttech.sharepoint.com/sites/TDRSResearchDesign/_layouts/15/Doc.aspx?sourcedoc={c9d41a72-bff8-4eba-b245-bb04ba265e12}&action=edit&wd=target%28Product%20Notes.one%7C02afc3cb-1bf8-4117-bd72-1f077c416961%2FProduct%20Sync%20Notes%7C13a66cb3-b4ad-514a-b8fb-544712b67cc7%2F%29&wdorigin=NavigationUrl)

---
### ***In-flight high priority items:***
- TDP Transition hack.md (Steve owning, coordinate inputs from Miles/Andrew)
- Review weekly in Prod Sync, identify in add-ins from OFA team
- 60-Day Bridge roadmap - clear re-prioritization if tickets are added to backlog | 1:1 in:out
- Security Control Assessment (Dev Support)
- February 8th SME interview (Alex + Andrew)
- February 20th 2nd SME interview (Alex + Andrew)
- 3rd SME interview - to be determined
- [Pen Testing](https://hackmd.io/RF6RT80yQOqMPdwiCrT2VQ)
- Jan to pick up workflow if OFA deems critical before Mo returns 02/12
- [Stub ticket](https://app.zenhub.com/workspaces/product-board-5f2c6cdc7c0bb1001bdc43a5/issues/gh/raft-tech/tanf-app/2824) - Context in hack.md for security concerns
- 02.06 - Alex noted there are 3 findings:
- 1x High Priority (30 days or less to remediate)
- 2x Medium (60 days or less to remediate)
- Recompete submission
- Final submission: 23 Feb
- Expected response: TBD
- [Errors Audit](https://hackmd.io/itv2dcDPRVulWm5mcaJtHQ#Next-Steps)
- Common user pain points / thematic grouping to knowledge center updates for support (UX support)
- Consolidation of UX research and materials (GitHub repo + Knowledge center audit/update)

---
### ***Sprint Cycle*** - 2 week duration (Wednesday - Tuesday)

#### Week 1
| Wednesday | Thursday | Friday |
| ----------------------- | --------- | ------------ |
| Stand Up | DevSecOps | Prod Sync |
| - | - | Office Hours |
| Office Hours / Dev Sync | - | Stand Up |

#### Week 2
| Monday | Tuesday | Wednesday | Thursday | Friday |
| ------------ | ------------------ | -------------- | -------------- | -------------- |
| Office Hours | Backlog Refinement | Office Hours | Async Stand Up | Daily Stand Up |
| Stand Up | UX Sync | Daily Stand Up | DevSecOps | Prod Sync |
| - | - | - | - | - |

#### Week 3
| Monday | Tuesday |
| ------------ | ---------------------- |
| Stand Up | End of Sprint Ceremony |
| Office Hours | Backlog Refinement |