You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is a follow-on of #94098 where A/Cs were not fully completed by the close-of-sprint date 12/18/24. Context: we drafted thorough high-level documentation, have designs, and have nearly implemented the AC-API alerts on the My HealtheVet on Va.gov landing page. We set up a sync to socialize this work w/ affected health tool team POs, but none were able to make that meeting time save for Don McCaughey (VAHB mobile app).
This spike ticket intends to cover two remaining tasks: 1.) communicating this work to the remaining stakeholders & getting feedback, and 2.) Understanding how to get into PI planning schedules in January to get this work prioritized asap.
User story
As a Cartography team member, I want to communicate the importance and outstanding work necessary to implement the AC-API and help minimize the load on Veterans to get access to health tools that rely on the MHV-API backend.
Socialize this work with remaining POs who were not able to attend the scheduled sync on 12/16/24:
Kay Lawyer
Patrick Bateman
Marci McGuire
including Kaitlin Fink and Robyn Singleton as needed
Get clarity from POs on clear next steps to get this work incorporated into roadmaps as part of PI planning in early January
Acceptance criteria
Important information has been communicated with remaining stakeholders
Stakeholders have had a chance to review the documentation, provide feedback, and share any relevant information about how to work with their PI planning processes to get this work prioritized in January 2025.
We are prepared to move on to the next ticket: drafting the implementation strategy
The text was updated successfully, but these errors were encountered:
Update: held stakeholder sync 2 on Thurs, Dec. 19 and Kay, Robyn, and Kaitlin attended. We have not directly discussed w/ Marci or Patrick, but the other OCTO leads let us know that the documentation would suffice and we can move forward with timelines for getting this work into PI planning. @wesrowe followed-up the meeting with a Slack thread that included a meeting recap and some clarification on next steps, which includes needing to get information about this work to teams by EOD today (12/20).
Description
This ticket is a follow-on of #94098 where A/Cs were not fully completed by the close-of-sprint date 12/18/24. Context: we drafted thorough high-level documentation, have designs, and have nearly implemented the AC-API alerts on the My HealtheVet on Va.gov landing page. We set up a sync to socialize this work w/ affected health tool team POs, but none were able to make that meeting time save for Don McCaughey (VAHB mobile app).
This spike ticket intends to cover two remaining tasks: 1.) communicating this work to the remaining stakeholders & getting feedback, and 2.) Understanding how to get into PI planning schedules in January to get this work prioritized asap.
User story
As a Cartography team member, I want to communicate the importance and outstanding work necessary to implement the AC-API and help minimize the load on Veterans to get access to health tools that rely on the MHV-API backend.
Notes
Possible tasks:
Acceptance criteria
The text was updated successfully, but these errors were encountered: