Improving Partner Team Experience

[bianca-rivera]

Description

This large epic consists of smaller epics that relate to the goal of improving VRO's partner team experience, which includes designing the what, how, and why of VRO's direct and indirect dynamic, interaction, processes, and communication with our partner teams.

Why

To capture at a macro view all of the work that pertain to increasing our DevEx maturity through the application of service design and design thinking methodologies. Also, this epic ensures that VRO has a customer-centric model where the needs, desires, and expectations of our partner teams are at core of how we make decisions and improvements.

AC

• provide meaningful impact for our partner teams
• consider or involve how changes, ideas, and recommendations will affect VRO team engineers and should strive to be co-created with VRO engineers
• catalyst for work should be data-driven and based on high calibre design and research best practices
• monitored and updated as variables change and evolve over time (i.e. team makeup, new partners, new capabilities, etc.)

[metrics/KPIs/OKRs to be developed and added here]

Notes

The smaller epics are the following:

1. Partner Team Support Model (Partner Team Support Model #2477) - strategic thinking and direction of how we provide support and deliver VRO as a service
2. Partner Team Engagement & DevEx (MVP) (Partner Team Engagement & DevEx (MVP) #2670) - tactical implementation of tangible improvements to the partner team experience and VRO operations
3. Partner Team Feedback (Partner Team Survey #2965) - recurring research initiatives that gather formal feedback on a consistent basis