Recommended way of handling agile goals in Portfolio?

[Stephan Dreyer]

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:

• "On February 1st, users are able to login"
• "On June 2nd, users are able to edit their user profile"

These goals depend on multiple stories, or even multiple epics.

What is the recommended way to handle such goals?

1. Use additional versions beneath the software version 1.0, 2.0,..? It seems like multiple releases can not be applied to a story in Portfolio.
2. Use an additional issue level?
3. Is there another way?

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.

[Roi Fine]

Hi Stephan,

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,

Cheers,