-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop MVP Document for 2022 #447
Comments
Closed issue #430 as it was a duplicate of this issue. |
Note from PM meeting with Bonnie on 02/19/22: As the MVP proposal stands-packaging software and giving it away for jurisdiction to manage- can be an issue because it creates bad competitors and overpopulates the market. |
2022 BallotNav MVP Draft: https://docs.google.com/document/d/12GSnVQXIQcKiu4nElbzos9mL5RvxyS6STLC1OD9NiuI/edit @yoursgayathri Please see the link above, specifically the section "DevOps Questions". These are some questions that I believe should be answered in order to further develop the MVP, and may be pertinent to your conversation with Drew. Please add or comment on anything that you think should be changed or included. |
@yoursgayathri Adding Gayathri to this issue. There needs to be a deeper understanding of where the backend is in order to further develop the MVP. I'd like to collaborate on this as this also connects with #480, to be conducted by the UX team. Upon discussion during PM meeting on 03/14/22, I am removing myself from this issue, and deferring to Gayathri's expertise in software development, as it pertains more closely to the direction the MVP is moving towards. |
Issue is being closed as it will be the new year and we no longer need an MVP for 2022. |
Overview
Create a more finalized version, including the team's comments.
Action Items
Resources/Instructions
2021 Proposed MVP
The text was updated successfully, but these errors were encountered: