You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
In the intention from The Lean Startup, a Minimum Viable Product (MVP) is a version of a product which allows a team to collect the maximum amount of validated learning about customers with the least effort. In my company MVP concept was strictly built in a hierarchy: Investments>Opportunities>MVPs>Stories. Different teams started to use different Jira functionalities for managing MVPs. As stories can be grouped to Epics in JIRA, some teams started to treat Epics as MVPs and some teams started to use Versions instead (versions also used for releases). Some teams uses Epics based on Scrum methodology and for them it's an obstacle to use Epics for MVPs tracking, so they ask for additional level in the JIRA issue hierarchy: Investments>Opportunities>MVPs>Epics>Stories. I think we should agree on a common way but hard to decide which way of managing MVPs would be most effective. Please could you share your experience?
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events