MVP

[Reddy]

How the MVP for a given initiative is measured in JiraAlign?  For example, if there is an Epic created and the Epic item has a number of features attached, is there any way via a display, a report, or any means that would identify the MVP target and the progress made (e.g., roadmap) towards achieving it?

Thank you.

[Reddy]

I found the below answer on MVP but not sure, what Leading indicators should be track in Jira Align to track MVP progress.

"Minimum Viable Product is a concept that breaks down the overall Client/Customer need into smaller batches. But each batch is its own, complete product. By intelligently breaking the functionality into smaller batches, each batch moves through development faster and easier, reducing risk and improving time to market. MVPs are realized by the completion of features and their associated user stories. Each feature builds towards the MVP. Each MVP also has a list of objective measurement criteria, called leading indicators, that measure the progress, in production, towards achieving the MVP. The fulfillment of the MVP is evaluated by the learnings made through customer use to decide whether to continue elaborating the development of the MVP, or stopping. In SAFe, this process is described by the Lean Start-Up Cycle."

Thank you.

[Reddy]

To summarize my question, which features make up the MVP and what the status is in terms of realizing the MVP?

[Tom O'Connor]

Abhi - some great questions.  If an Initiative (Portfolio Epic) is identified as an MVP, then I suggest that  ALL Features/Stories within the work item should be delivered to meet the Minimal Viable Product as Eric Reis describes “The Minimal Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”  Unfortunately the Roadmap does not allow you to filter by the MVP field, so I would recommend using the MVP tag on the Initiative if you want to filter the Roadmap view to show progress of all MVP items.  Remember progress is measured by story acceptance.  

You may have an Initiative that is not and MVP but have several Features under it that could be delivered as MMFs and identified as “The Minimum Marketable Feature is the smallest unit of functionality with intrinsic market value.”. This start small and incrementally build value for feedback may be used to validate some product functionality before building the full product.  

[Reddy]

Hello @Tom O_Connor ,

 That's a great suggestion. Thank you very much!

Regards.

[Reddy]

Hello @Tom O_Connor 

Also, another problem is we already have clients using the tool that contain a combination of work ascribed to a single Epic. The tool doesn’t prevent it. So, we are looking for a way in the tool to articulate progress of some number of features (and possibly enablers) that were intended and funded to meet an MVP, and then if a conscious decision is made to continue, additional features for enhancements.  Some clients also articulate all the feature scope then the LBC is proposed with a set of MVP Features and a set of Additional Features, and because the tool doesn’t limit it, all those work items get included in one Epic. Regardless, we need a way to illustrate this progress on the lifecycle of the Epic, against the initial MVP, since no one remembers the LBC after it’s proposed. Would this be an enhancement request?

Regards.

[Tom O'Connor]

@Reddy Sorry for the delay on your additional question.  Could the MVP work of the Epic be tracked in an OKR?  I could see creating a Program OKR that links the set of features that represent a subset of the Epic.  You can track the progress of the OKR by Key Results and/or the work progress in the objective tree report.  

https://agilecrafthelp.zendesk.com/hc/en-us/articles/360019601434-10X-Create-and-Update-Key-Results

https://agilecrafthelp.zendesk.com/hc/en-us/articles/360019601834-10X-Objectives-Tree