Page History
...
In a future state for 2023 only the Jira Projects in black text will remain for Information Systems.
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.
...
- Yamaha
...
Three projects are different, and relate to the future YME way of working:
- Yamaha Applications Support Desk (SD) captures all requests from end-users, who experience difficulties with their day-to-day use of IT applications. These items are validated, then if valid resolved as soon as possible.
- Yamaha IS Projects (YIS) captures all work of scrum teams in the Agile Transformation. These processes are being streamlined to support scrum processes, and make Jira a tool for collaboration more than administration.
- Yamaha Portfolio Board (YPM) collects all ideas for IT initiatives, and validates the business case and expected rewards for implementing such initiatives before assigning work to development teams. It's very much about preparing work.
- Other projects capture work for teams that have not yet joined the Agile Transformation.
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 be phased out completely as it will be covered by the Yamaha Portfolio Board and Software project(s).
Jira Yamaha Applications Support Desk (SD)
Issuetypes
Audit: Used for J-sox change requests and IRY issues registered to deliver evidence for auditors.
Authorization request: Elevate user rights request used for Ympact to request YMXXITS1 access to have command line access and to operate in Ympact (Branch specific) Production environment.
Incident: Reporting a incident or outage. Currently all incoming issues submitted via the Jira Customer portal will have Issue type Incident.
RobotJob Change: Robot Job Change request used for Ympact Job scheduling
Deployment request: Triggered by Development software projects used by B2B teams for Ympact,Ympulse, Yamcom deployments.
Incident: Reporting a incident or outage. Currently all incoming issues submitted via the Jira Customer portal will have Issue type Incident.
Service Request: This Request for information, this issue type has previously been used for Information requestis currently not used anymore.
Workflow
Jira YIS for Agile software development
...
- Backlog: work has not started;
- In progress: a developer builds & unit tests their own work to meet acceptance criteria;
- Review: a peer reviews any code & functionality;
- Ready for test: waiting for a QA officer;
- In test: QA officer is performing integration test & regression test;
- In UAT: PO/business validate that the functionality is as required, or provide feedback;
- Done: the work is completed without deployment needed; or
- Ready for deployment: the work is done & documented, but deployment to production is needed;
- Scheduled for deploymendeployment: deployment date is set;
- Done deploymendeployment: the solution is available and working on production.
...
Epics have three additional statusses statuses for Product Owners to prepare the work:
...
Additionally, on Kanban boards, closed items will disappear from the board once a fix/version is closed, not earlier.
...
J-sox compliance
DoD projects
When closing an item, it is mandatory to full the field "DoD projects":
...
Within YME the intent it to validate these three organisationorganization-wide requirements for each ticket, because YME because YME is being audited on these three points. For this reason, it is expected that this field will become mandatory across all YME projects in Jira.
...
Scrum teams generally use a Definition of Ready to clarify whether a Jira issue (Product Backlog Item, or PBI) can be taken into sprint. Within Jira, this process has been summarised summarized in a field, "DoR", which allows tracking what an issue needs to become ready for development.
The generalised generalized DoR steps are:
- PBI created
- User story defined
- Acceptance criteria defined
- Refinement & estimation done
- Ready for sprint
...
Overview
Content Tools