[Product] Data Visibility | Develop an minimum viable product outline and seek alignment

[bianca-rivera]

What

As the VRO Platform team, we have decided to pursue a new feature that will allow partner teams to query our database. We have received feedback from multiple teams within the portfolio that accessing historical data sets would be valuable. Additionally, our current partner team, Contention Classification, has expressed that requesting data sets from our team can be cumbersome and frustrating.

In response to these concerns, we have selected a tool to address this need: Streamlit. We have reviewed this tool with our team, partner teams, and our ISSO to understand their requirements and assess the associated risks. (See linked ticket below).

The purpose of this ticket is to consolidate all this work into a MVP product outline and seek alignment before we begin the development stage.

AC

• [ ] Product outline for MVP is concise and easy to read
• [ ] Product / Delivery Manager has met with the Enablement Team, VRO Team, CC Team, and ISSO (if needed) to ensure alignment on the path forward
• [ ] Necessary tickets to complete the agreed-upon work have been created and tagged in the Data Visibility Epic

Out of scope

This MVP should only focus on the CC Team and contention events; not other use cases.

Resources

Data Visibility MVP Product Brief

• Data Visibility POC Planning
• Data Visibility Discovery

To Do Tasks to Implement this Ticket

• [ ] Product outline for MVP suggested sections/content:

• Context/background

• Vision and goal

• Business value/value prop

• Features

• Considerations (dependencies, constraints, risks)

• Open questions

• [ ] Create ticket to create Project Plan for Sprint E and pull in information from Product Resources listed in this ticket

• [ ] Attach the MVP outline to the Data Vis. epic

• [ ] Ensure Sprint E is loaded with the next set of tickets needed to begin development

[BerniXiongA6]

@bianca-rivera @meganhicks -- I was able to update the MVP Product Outline with some content that I extracted from other Data Visibility resources and artifacts. We can certainly populate more content on this document as we see fit; however, given the new priority of Silent Failures taking precedence at this time, this product ticket will likely carry over to the subsequent Sprint. Let me know if you have any questions.