Jira YPM for portfolio planning

Before work is ready for development, any idea for software development is first vetted by the portfolio management, to understand whether the proposal is of strategic value to YME. Once it is agreed that the idea should be implemented, a selection of what to do first is made based on business case, priority, and urgency. This way we ensure that time is spent on the most valuable topics.

Issuetypes

Issuetypes from YPM start with Programme in case of a large multi-quarter initiative, or start with Project in case of a large single-quarter initiative. A Programme can contain multiple Projects, just like a Project can contain multiple Epics.
An Epic represents high-level initiatives or bigger pieces of work in Jira that need to be broken down.
An Enhancement is a smaller, standalone improvement of existing functionality, that has strategic value on its own.
A Deliverable is used to capture the High Level Design and Low Level Design, created by architects as input for the development team assigned.
A Test is intended to capture UAT planning.

In due time it is expected that Epic, Deliverable, and Test will move into the development projects, away from Portfolio Planning.

Workflows

This project contains four different workflows, which in some cases include a Project Review Board (PRB) or AWG approval flow.

Field configuration

The field configuration is shared between YPM and CAB projects. The screen configuration is unique to YPM and contains a great many fields on screen.

Yamaha Team(s) field

Upon request of PMO team a multi select field Yamaha team(s) for Issue type  Programme and Project, Enhancement and Epic has been created.
This field replaces the old Team Yamaha field for these two Issues types. If assistance for a bulk update is required, please contact a Jira Administrator.

The Yamaha Team single select field is only needed to be filled for the creation of Deliverables or an Enhancement ticket. These issue types triggers a Development ticket creation in another Jira project like YIS, B2C, YM, BA, BL.

Team(s) can be selected via a drop down menu and pressing CTRL to select multiple teams.
When no values are set, select the edit button to add field values.

Responsible Architect field, for Programme and Project

Upon request of Architect Working Group A User Picker field for Responsible Architect has been setup.
This field will be used by the Architect Working Group  to select the Responsible Architect for  Programme and Project.

When no value is set, select the edit button.


This  field works similar as the Assignee field.  When you start typing, suggestions will be made of matching users. Select the user to confirm your choice.

When set it will appear in the people section on the right hand side: