# Connor Coverage Plan (01 - 05 May) ## Recurring Meetings * Daily Stand Up * Diana to drive day to day * Resources to support: [Spr 72 planning doc](https://hackmd.io/FYmQb_hGRtSpjvsv_VAPVQ), daily stand up notes - no major call outs, Andrew to continue driving Parsing Engine development. KC Videos 1 and 2 to be submitted to ACF YT team 5.1. George has personal situation going on, Andrew to manage directly with him 1:1. If Dev needs to pull in more tickets, Andrew can drive, priority will be 3.2 Parsing as long as 1336 and 2489 are complete for 3.1 release. * Note: Dev to work on cross communiciation, asking for commitment on reviews and timelines from peers during SU * Backlog Refinement * Andrew to lead discussion of new tickets * UX to attend per usual operating process * IPT * Andrew available per usual operating process, typically no inputs from Raft team * Cross Prod - off week * Prod Sync - Andrew * UX Sync - Diana and Miles * Dev Office Hours - Andrew + Dev Team ## Sprint 72 Priorities * [Sprint 72 Planning document](https://hackmd.io/FYmQb_hGRtSpjvsv_VAPVQ) | Champion | Goal | Stretch | |:-------- |:-----------:|:------------:| | Jan | 1113 | 1610 (in review) / pair w/ Andrew, further parsing | | Mo | ~~1122~~, 2369 | 2282 | George | 2115/2116(blocked), ~~2385~~ | 2457 | | Eric | ~~1336~~, ~~2274~~, 2489, 2466 (as of Friday's standup these are both technically still open per Eric) | 2424 | | Andrew | 1613 | | | Miles | 2438 (pending ACF Youtube), 2439 | Transmission Email | | Diana | STT onboarding, 2368 | Vendor Discussions (on hold until after 5/15) | ## Resources * **Stand Up Notes** - ticket by ticket, goals for reviews/TTs * Diana <> Connor to handoff after Friday SU * Tuesday, 5/2: A new Raft SharePoint instance was created because the HHS side has completely blocked us from access * Wednesday, 5/3: Steve will reach out to you about a TDRS case study for internal Rafters when you get back * Friday, 5/5: * overall good progress this week on tickets and dev team running tabletop in the afternoon. * Adding 1610 on your radar - * Which sprint is this slotted for dev? * Before dev starts on this story a coordination between Alex/Dev/UX should happen to better understand the impacts this will have on active users - some initial questions I have... * Initial Questions: * Will the error report link be retroactive? Will they show up for past submissions? Should it? Or will the error report only show up for future submissions? * What if any communication needs should be sent out to active users? * Can the current transmission report handle different send rules? * Requires someone to push a button to trigger the transmission report send to States and Territories?  * STT Submitted Data Files – TDRS Way – Receives current transmission report * STT Submitted Data Files – TDP Way – No Transmission Report but the Error Report is viewable in TDP – Note: how will the Grantee be notified when the Error Report is ready for viewing? ### Helpful Links * [Planning Roadmap](https://app.mural.co/t/raft2792/m/raft2792/1675268418098/d56ec0d5415d8cda9c6ae9cae61154bcc4e74bba?sender=ue018dddfca540564eae53907) * [Sprint Board](https://app.zenhub.com/workspaces/sprint-board-5f18ab06dfd91c000f7e682e/board) * [Product Board](https://app.zenhub.com/workspaces/product-board-5f2c6cdc7c0bb1001bdc43a5/board) ### Additional Notes: For any urgent matter feel free to message me at 605.252.0376