We have a Kanban process for a product that is currently in MVP development stage.
For maximum visibility for stakeholders, we want to define agile goals / milestones in Portfolio, something like:
These goals depend on multiple stories, or even multiple epics.
What is the recommended way to handle such goals?
And how can we make these goals visible on the timeline view? Generally the stakeholders are not interested in detailed stories or epics. They just want to know which feature is available when.
Thanks in forward for support.
That is a great question. Releases is a good way to visualize value shipped for customers. If you have different dates for capabilities completion and releases you could use a creative solution of a parent issue. I.e: If you create a parent issue for all issues that relate to "user able to login" you could visualize it on the timeline with target dates or auto-scheduled dates.
I would love to hear your thoughts,
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG