App to help prepare for development kickoff...

Pitch
A highly-opinionated guide that will walk a Product Manager/Product Owner/Program Manager/Project Manager (can we boil these personas down to one commone one?) through the necessary and best-practice gates to prep a backlog of work (new product or new version of existing product) for execution (kick off development).

Imagine walking the user through the following steps in preparation for development kickoff.

WHAT IS THE PROBLEM WE ARE TRYING TO SOLVE?

1. What is the question we are trying to answer? What is the hypothesis we are testing? What problem are we trying to solve for the user that we are going to do better than their current solution. Personas, users vs. purchasers, decision makers? WHAT ARE WE NOT DOING ON PURPOSE?

MVP: Walk user through answering the above questions
MVP: Store these values for re-use in later steps
MVP: Output a summary page that stakeholders and team would consume

HOW DOES SOLVING THIS PROCESS MAKE US MONEY? HOW MUCH MONEY?
2. Business case, conops, concept case, KPIs, goals, targets - This formalizes the above a bit more and creates a consumable document
MVP: Enable user to fill in templates of one or more of the above
MVP: Ouput a summary page that stakehoders and team would consume

WHAT IS THE MVP?
3. Requirements to hit MVP, remind user of YAGNI, refocus on #1, fight scope creep, help developers make hard decisions quickly, don't worry so much about how it works specifically but broad strokes what problems it must solve for the user, what analytics to include, feature flag A/B testing requirements, session replay and heatmap tools, Moscow

MVP: Populate epics and user stories in Jira
MVP: guide users towards the "user story" format
MVP: guide users towards multiple user stories for each requirement/feature as there are different personas using each feature in a different way
MVP: guide user to be clear on what the user story is NOT doing
Future: ML or something quasi-smart to better word/describe requirements?
Future: ML words to mockups or mockups to words?

WHAT "MOSTLY FINE" ARCHITECTURE IS REQUIRED TO HIT MVP?
4. "Good enough architecture," Don't need full containerized micro service deployment to answer #1 as long as #1 is tightly defined, Make it work then make it fast, Use existing platforms...i.e. Spotify marketplace, Salesforce marketplace
MVP: Guide user through creating a basic architecture diagram
MVP: Store said diagram in documentation bundle
MVP: Guide users towards building something quckly first then making it fast or scalable to future requirements

HOW WILL THE APP SOLVE THE PROBLEM IN AN ELEGANT WAY?
5. Design/mockups/user research

WHAT IS THE HIGH-LEVEL PROCESS TO GET MVP DONE?
6. Agile fundamentals, Kickoff, release grooming, sprint kickoff, sprint demo, sprint retro..rinse and repeat...UAT, Hardening
MVP: Educate newbie PO on agile ceremonies and artifacts
MVP: Simple output of agile schedule (ceremonites and artifacts):

WHAT ARE THE HIGH-LEVEL WORK ITEMS NEEDED TO CREATE THE MVP?
7. Initial release backlog grooming, scoping and prioritization
MVP: help user create a release in Jira
MVP: loop through and repeat steps in #3
MVP: educate user as to why they should include tech debt and bugs if this is not the first release of a product (get input from dev team/leads)
MVP: walkthrough prioritizing (get input from dev team/leads)
MVP: ouput prioritized backlog in Jira

KICKOFF
8. Start Iterative Execution - THIS IS WHEN DEVELOPMENT STARTS - $$$$ start to get spent here - do work before starting this - fight the temptation to hurry up and start
This is where Kickoff drop the user off into Jira-land to do the execution