Page History
...
| Project | Key | Project type and Purpose |
|---|---|---|
| SD | Jira Service management - Incident management including Customer Portal | |
| ||
| B2C-Apps | B2C | Software delivery - various products used by B2C/EPAM team(s) |
| YamahaISprojects | YIS | Software delivery - Agile teams |
| Yamaha Portfolio Board | YPM | Software delivery - Portfolio/Project planning |
| Yamaha Portfolio Board | YPB | Software delivery - Portfolio/Project planning |
| Yamaha Motor Next Stage Project | EUYNS | Software delivery - Yamaha Next Stage (SAP/Informatica) |
| Yamaha Motor Next Stage | YNSEU | Software delivery - Yamaha Next Stage project EU rollout High level tracking (SAP/IDMC/Informatica) |
...
The Change Advisory Board (CAB) captures captured approval of fixes and creation of a functional/technical conceptional design document , this has been phased out completely as it has been covered by the Yamaha Portfolio Board and Jira Software project(s).
In paragraphs below you can find a short summary per project and links to the more detailed Jira-project documentation.
...
More detailed documentation for this project can be found under Jira training for Yamaha Applications Support Desk (SD).
...
Change advisory Board (CAB) project 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.
Bug: Bugfix to deliver a functional/technical solution for the original SD issue. SD issue remains open until the fix has been applied.
Story: Non-bugfix for internal improvement, prevent (recurring) issues for the future. SD issue can be closed, user will be informed that current issue is fixed but there will still be worked on in the background to prevent from happening again or improvements.
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)
Yamaha Portfolio Board (YPM)
| Anchor | ||||
|---|---|---|---|---|
|
...
| Project | Key | Project type and Purpose |
|---|---|---|
| ||
| B2C-Apps | B2C | Software delivery - various products used by B2C/EPAM team(s) |
| YamahaISprojects | YIS | Software delivery - Agile teams |
...
Overview
Content Tools