Top Use Cases: New Feature Requests - Research and Ideation

[bianca-rivera]

Description

Currently, the VRO's Intake Form on Github is being used for different types of requests - new features, releases, and deployments. The original intent of the form was to log new feature requests into our backlog. The CC team are the main users of the form, whereas the EE team leverages the #benefits-vro-support Slack channel. There is a need to create simple workflows that differentiate the documentation and management of immediate tactical needs (i.e. releases and deployments) vs. strategic wants (i.e. new features) that both partner teams consistently follow.

Why

Designating the proper usage of the form will help streamline defined pathways for partner teams engineers in particular to receive consistent and appropriate support from VRO for different use cases. This effort will also highlight opportunities and gaps in our operations for equitably documenting and distributing responsibilities of assignees per request/ticket.

AC

• [ ] schedule working sessions
• [ ] document current state of how partner teams are have been making deployment requests (i.e. via Slack and Intake Form)
• [ ] highlight pain points and gaps, including the information/context VRO needs to provide and solicit partner teams
• [ ] assessment of if/how partner team engineers are using other non-designated pathways for the same categories of requests (i.e. DM slack messages to POC)
• [ ] develop a refined process that includes SLAs and a lightweight test plan

Out of Scope:

• research/tech spec on ticket management systems

Notes

This ticket is referencing deployment requests partner teams make to higher-level environments.

Resources

reference work completed in #2976 Mural link example of a deployment request made through slack: 7/1: EP Merge to sandbox

[BerniXiongA6]

@bianca-rivera can pair with Eng to work on this during second week of sprint. OK to push out to Sprint 2 if unable to finish. @BerniXiongA6