You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi - My Group is rolling out Jira Portfolio and trying to standardize on terms.
The current plan is to set up 10 Portfolios build across Business functions. Under each Portfolio we have between 10 - 60 different software applications. These teams current use Jira for User Stories and Epics. We want to bundle Epics into MVIs and map the MVIs to Milestones. The goal is to better prioritize work and ensure we are working on things that map to long-term goals.
We are not in agreement on how to define what an MVI is. Some say an MVI can only relate to a single application and ties to a release. Others say that an MVI can relate to a strategic objective that crosses multiple applications and can have many releases at the Epic or Story level before the MVI completes.
I thought I would poll the "Wisdom of the Crowd."