...

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.
In Jira these ideas are created within Jira-Project Yamaha Portfolio Board (YPM)

Jira Training documentation can be found under: Jira training for Yamaha Portfolio Planning (YPM).

Yamaha Portfolio Board is a collection of programs and projects that together should execute the strategy of the organization and contribute to its goals and objectives.
Enhancements, improvements and new functionality requests are raised via the Yamaha Portfolio Board (YPM) and can only be raised by YME Portfolio managers, these are the Directors and Division managers.
Functional Design (FD) and Technical Design (TD) activities and approvals are done in the Yamaha Portfolio Board (so no longer CAB).
Planning activities for YPM is done in Jira via Big Picture, by the Project Owner.

All project related documentation can be found under Confluence space Yamaha Portfolio Board. In here you can find Procedures, Training material, report outs, processes etc. 

...

YPM Issue types

...

Image Removed A Project is a set of activities to deliver one or more outputs in accordance with a specific business case. A particular project may or may not be part of a program. 

Image RemovedEpics are large bodies of work that need to be completed over several sprints or over a longer period of time.

Image RemovedDeliverables are generic output that is similar and required for each project and epic (FD, TD, HLD)

Image RemovedTest  If needed, the deliverable for testing is moved to Issue type Test upon working on the issue.

Image RemovedEnhancement

...

Documentation for FD and TD is written in Confluence under  Project and Programme documentation and needs to be linked to the YPM project and respective EPIC.
A HLD should always be documented under the MAIN project Image Removed, so highest level. Depending on the complexity of a project (as soon as 2 or more applications are affected) EPICs will be the key to record TDs under.
Although recorded under the EPIC, all TDs should refer/link to the HLD or HFD.

It can be that a project belongs to a Programme (multiple projects delivering functionality of value, e.g. the e-bike programme). If that is the case (recognizable on project level by checking the TICKET GROUP),
documentation of the project should be under the Programmes section in the project documentation section under of the portfolioboard. All non-programme projects are documented under YME Portfolio Projects.

Software delivery projects

...