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 | 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) |
...
More detailed documentation for this project can be found under Jira training for Yamaha Applications Support Desk (SD).
Yamaha Portfolio Board (
...
YPB)
...
| Anchor | ||||
|---|---|---|---|---|
|
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 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 initiatives are created within Jira-Project Yamaha Portfolio Board (YPMYPB). After a initiative is approved in the Yamaha Portfolio Board (YPMYPB), 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 (YPMYPB).
Software delivery projects
...
Overview
Content Tools