...

Yamaha Portfolio Board (YPM)

Documentation can be found under: Jira training for 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 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. 

Explanation off used issue types and YPM procedure can be found in the following Presentation: Jira Training material

YPM Issue types

Image ModifiedProgramme is a set of related projects issued by management for implementation to deliver business outcomes and benefits.                                          

Image Modified 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 ModifiedEpics are large bodies of work that need to be completed over several sprints or over a longer period of time.

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

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

Image ModifiedEnhancement

The High Level Design (HLD) and Functional Design (FD) are always linked to the Image Modified Project YPM-Issue (not Image ModifiedProgramme!) 
The Technical Design (TD) can be done under the project (single application), but will be registered under the Image ModifiedEPIC YPM-Issue. 

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 Modified, 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

...

Add-ons used by Information Systems

• Agile Tools & Filters for Jira Software
• Backbone Issue Sync for Jira  Synchronization between PCW (US) Jira and YME Jira for Yamaha Next Stage (YNS) Project. This Jira project is used for the integration of SAP and Informatica. 
• Big Picture Roadmap and resource planning for Portfolio Board.
• Checklist for example used for Custom field DOD in Software projects.
• Doublecheck for Jira Service Management 
• Eazy BI
• Jenkins Integration for Jira Server and Data Center
• ProForma: Forms for Jira
• Status Time Free
• Timesheet Reports and Gadgets
  This addon is used by Information Systems, Business Applications department to log hours spend on Projects, issues. When hours are logged there is more insight in the velocity of teams and specifically projects.
  Secondly we expect to see the exact number of hours that are contract wise in place per person per month. In order to get a clear overview, we also expect hours to be registered to the correct issues.
  As you all will have time which can not be related to a issue/project directly, e.g. a meeting, you can add these to running tickets (as long as they are booked in the correct month it is correct).
  During the hour logging you can indicate in the comment it concerned a meeting or so.
  Specifically for consultants it is important the total hours in Jira correspond to the hours declared, these will be compared to the sign off hour sheet.
  We do not consider time registration limited to consultants only. It is meant for the whole B2B team.
  
• Version manager
• Xray Test Management tool (app)

...