...
Information Systems Division is using the following Jira projects:
ProjectProject | Key | Project type and Purpose |
---|---|---|
SD | Jira Service management - Incident management including Customer Portal | |
B2B-Apps - BA | BA | Software delivery - Cognos, TM1, Cubes |
B2B-Apps - Logistics | BL | Software delivery - YLS, SYS2000, Witron |
B2B-Apps - Ympact | YM | Software delivery - YMPACT |
B2C-Apps | B2C | Software delivery - various products used by B2C/EPAM team(s) |
Change Advisory Board | CAB | Software delivery - management approval |
YamahaISprojects | YIS | Software delivery - Agile teams |
Yamaha Portfolio Board | YPM | Software delivery - Portfolio/Project planning |
Yamaha Motor Next Stage Project | EUYNS | Software delivery - Yamaha Next Stage (SAP/Informatica) |
In a future state for 2023 only the Jira Projects in black text above will remain for Information Systems.
Yamaha Motor next Stage Project (EUYNS) Yamaha Motor Next Stage Projects (YNS) has been setup as supporting platform to check the progress between YMC and PwC at the same time in the YNS project.
In due time, Information Systems teams working in Jira Software projects will be onboarded to the YIS project, so this can become our mutually agreed way of working for Software delivery.
Any team joining will be coached through the (Agile) transition and will be able to provide input on unique ways of working that will need to be integrated. Together we will make it a success.
For now, these Information Systems projects will keep on using their current of way of working. With time and proper preparation, they will migrate into YIS.
The Change Advisory Board will (CAB) captures approval of fixes and creation of a functional/technical conceptional design document , this will be phased out completely as it will be covered by the Yamaha Portfolio Board and and Software project(s).
In paragraphs below you can find a short summary per project and links to the more detailed Jira-project documentation.
...
Anchor | ||||
---|---|---|---|---|
|
In Yamaha Applications Support Desk all operational support (BAU- all operational support (BAU- Business As Usual) requests are registered that relates to IT Application Issues/errors for existing functionality, data correction and authorization requests.
Users can create a new issue via the Yamaha Motor Europe support portal, via this portal you can go to the YME Information Systems Support Portal to submit a IT request.
Instructions of the portal forms can be found here: YME Information Systems Support Portal Guide
Note |
---|
The button should NOT be used for creation of a SD issue. |
If a bugfix is required to deliver a functional/technical solution for the original SD issue a linked Bug and for B2C Incident can be created in a Software delivery project.
The SD issue remains open until the fix has been applied and is used to keep the reporter and participants informed or to collect information from the requester.
More detailed documentation for this project can be found under Jira More detailed documentation for this project can be found under Jira training for Yamaha Applications Support Desk (SD).
Anchor | ||
---|---|---|
|
...
|
Change advisory Board (CAB) project is workflow is used for approval of fixes and creation of a functional/technical conceptional design document.
Note |
---|
This project will be phased out as Bugfix issues can be created in the software delivery projects directly via the SD Workflow. Changes, improvements should be requested via creation of a Project by a YME Portfolio Board Manager via the Jira training for Information Systems. |
One of the two following conditions must be met to create a CAB issue.
...
Under the SD issue the reporter and requested participants can be informed about the change applied/ to be applied but is also used to collect information from the requester.
Function design (FD) and Technical design (TD) documents can be found in Confluence under space Functional Conceptional Designs.
At the main page instructions can be found how a Functional/Technical Conceptional Design document can be created (via standardized template).
Note |
---|
Designs are no longer documented under the Functional Conceptional Designs but under YPM Project and Programme documentation |
More detailed documentation for this project can be found under Jira Training for Change Advisory Board (CAB)
...
Anchor | ||||
---|---|---|---|---|
|
Before work is ready for Before work is ready for development, any initiative (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 initiative 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 initiatives are created within Jira-Project Yamaha Portfolio Board (YPM). After a initiative is approved in the Yamaha Portfolio Board (YPM), development items for implementation will be created by the teams in a Jira Software Delivery Project.
Jira Training documentation can be found under: Jira training for Yamaha Portfolio Planning (YPM).
...
Project | Key | Project type and Purpose |
---|---|---|
B2B-Apps - BA | BA | Software delivery - Cognos, TM1, Cubes |
B2B-Apps - Logistics | BL | Software delivery - YLS, SYS2000, Witron |
B2B-Apps - Ympact | YM | Software delivery - YMPACT |
B2C-Apps | B2C | Software delivery - various products used by B2C/EPAM team(s) |
YamahaISprojects | YIS | Software delivery - Agile teams |
...
Jira project B2C-Apps (B2C) will remain for B2C teams working with Waterfall methodology. Processes are being streamlined with new Yamaha way of working.
Anchor | ||||
---|---|---|---|---|
|
Project YIS is set up as a single space to allow Next to the above projects also Yamaha Motor next Stage Project (EUYNS) is used, only some Information Systems and Business users are having access to this project.
Yamaha Motor Next Stage Projects (YNS) has been setup as supporting platform to check the progress between YMC and PwC at the same time in the YNS project. to align on an Agile way of working, as part of the Agile Transformation.
Together we strive to arrive at a Jira configuration that is usable for all teams, supporting all YME Information Systems processes in a comprehensive, simplified manner.
Documentation can be found on the following page: Jira training for Yamaha Motor Next Stage (EUYNS)
Project YIS is set up as a single space to allow Information Systems and Business to align on an Agile way of working, as part of the Agile Transformation.
Anchor | ||||
---|---|---|---|---|
|
Project B2C is set up as a single space for Consumer Train to work with a Waterfall methodology.
Together with EPAM and Yamaha teams Together we strive to arrive at a Jira configuration that is usable for all teamsB2C, supporting all YME Information Systems processes in a comprehensive, simplified manner.
Documentation can be found on the following page: Jira training for Yamaha IS Projects (YIS)
Project B2C is set up as a single space for Consumer Train to work with a Waterfall methodology.
Anchor | ||||
---|---|---|---|---|
|
Yamaha Motor Next Stage Projects (YNS) has been setup as supporting platform to check the progress between YMC and PwC at the same time in the YNS project.
Only some Information Systems and Business users are having access to this projectTogether with EPAM and Yamaha teams we strive to arrive at a Jira configuration that is usable for B2C, supporting all YME Information Systems processes in a comprehensive, simplified manner.
Documentation can be found on the following page: Jira training for B2C-APPS (B2CYamaha Motor Next Stage (EUYNS)
...