OCTO-DE Portfolio Roadmap

MickinSahni commented 1 year ago

What are we building

Develop a roadmap into the work happening across the OCTO-DE portfolio

Why are we pursuing this opportunity/problem

Leadership lacks visibility into what work is currently happening, which makes planning for people and resources harder. And this lack of visibility makes communicating priorities with other parts of VA more difficult.

DE's tried to solve this problem in different but not consistent ways:

MHV transition roadmap on Zenhub
A prototype built using the new GitHub Projects product
Individual team Murals

Questions to answer:

What level of granularity is necessary?
What scope is appropriate e.g. VFS, DE (VFS + Platform), all of OCTO?

Tasks

[ ] Lorem

Definition of Done

[ ] identify existing versions of each item within the various components of OCTO (ask everyone in product ops to weigh in and then put out a question with list we have in the #product channel.
[ ] use CoP meetings to review status and get feedback or competing version from product people
[ ] identify the processes and docs in place that use existing versions
[ ] identify any work currently underway to update related docs or processes
[ ] coordinate with the product ops team to create a single, OCTO version of each item
[ ] update doc links, archive old docs, and update processes to direct users to the new version
[ ] ensure the new version is listed in onboarding docs and processes

How to configure this issue

[ ] Review issue with the Product Ops team
[ ] Prioritize
- label accordingly:
- Low Priority - 🟢
- Medium Priority - 🟠
- High Priority - 🔴
[ ] Add Assignees (who will do this work?)

MickinSahni commented 1 year ago

2/21 Internal PrOps

Who's the target audience? is the primary question bc this might take a large effort if we're not careful.
Could we scope to specific efforts i.e. if there are 10 OCTO-wide and 6-7 DE, what are those?
- @lkoenigsberg can point us to them (on the digital experience products)
What are some of those questions e.g. Chris is getting? And, could we manually address until we need to scale?

Next steps: see what's produced by the Crews coming out of the DE off-site

lkoenigsberg commented 1 year ago

FY23 Priority Initiatives that touch or are owned by DE @MickinSahni

MickinSahni commented 1 year ago

@raywangoctova could you drop a screenshot or copy of your roadmap improvements slide?

update: shared in slack

lkoenigsberg commented 1 year ago

@MickinSahni , here is the schedule for weekly staff meeting focused presentations by crew/team. I'll dig up some example decks for you to take a look at.

2023 Team Meeting Schedule January • 1/5: Innovation @agantcurtis

• 1/12: Sitewide @Dave Conlon

• 1/19: Account experience @Chante

• 1/26: Data @Varoon Mathur (He/Him)

@Marian Adly

February • 2/2: Mobile @Chris Johnston

• 2/9: Health @Lalexanderson (health care, she/her)

@Leah Bannon (she/her) • 2/16 OFF – Washington’s Birthday • 2/23: Platform @mchelen

March • 3/2: Innovation @agantcurtis

• 3/9: Benefits @Zach Goldfine (he/him, DC) Goldfine (he/him - DC) @Matt Self

@Premal

@Emily Theis