Versions Compared

Old Version 18

changes.mady.by.user Bianca van der Meer

Saved on

compared with

New Version 19

changes.mady.by.user Bianca van der Meer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project YIS is a Software delivery Project used by agile teams working Scrum or Kanban.

YIS Issue types

YIS: Scrum Issue Type Scheme contains the following Issue types:
Image RemovedImage Added


Issue types have a hierarchy to them:

Items in YIS Jira-project are build on the Programmes orProjects created Projects created in YPM (Yamaha Portfolio Board) . More detailed information about YPM setup can be found here: Jira training for Portfolio Planning.
AnEpic  Epic should always be linked to one of these, so it is clear which strategic initiative it's part of.


Explanation per  issue type used in YIS:

AnEpic is a large feature, that is broken down into its component Stories by a scrum team.

...

  • YIS Field Configuration, this is used by default
  • YIS sub-task Field Configuration, used by Issue type Subtask.

YIS Specific Fields

Story exampleExample Fields overview for Issue type Story and Sub-task:

Image Modified   Image Added

All used issue fields in YIS are explained below:

  • Type: Issue type used, see list under under YIS Issue types

  • Priority: By default issues in YIS are set to priority Medium


  • Affected Version/s: field is by default empty, can be filled with affected version/s used for releases.

  • Business value:  used to estimate (in a Fibonacci range) the value of that piece of development to the YME business.

  • Labels: tags or keywords that can be added to issues to show whether they possess certain characteristics. If a issue is related to BAU (Business As Usual) activities label BAU is added. 

  • Epic Link: link to epic issue(s) (large feature).

  • Sprint: Multi select field to link the issue to a sprint.


  • Requirement status: The requirement test status by version or test plan, is used by XRAY and applicable for issue type Story and Change request.


  • Application-Module: Single select list of applications (products) and modules (programs). 
  • Solution Group : This field is used to select a single department that the Yamaha Team falls under. Based upon this field the ticket will appear in the Dashboard queue/filter of a department (manager).
    When all agile teams are formed this field will be phased out for YIS Jira -project.

    Application-Module: Select list of applications (products) and modules (programs). 


  • Yamaha Team: Yamaha Team is a single select drop down field which is required for all issue types used in YIS. 

    This field includes all teams that exist within YME Information Services. When a new team is founded, an entry is added to this field.

    For example, the entries on 01/01/2023:


    Any team board uses this field to filter on, so it's mandatory to fill in at ticket creation, so that the item will show up on the correct team board.

    N.B.: In the past a free text field "Team Yamaha" was used, in which typing errors caused for tickets to get lost. This old field is in the process of being phased out, so you may still see it on certain screens.


  • Target release date:  is used to track the intended release date aligned with stakeholders.

  • Ticket groups: Used Checkbox field used to group stories and bugs under a YPM Programme. 


  • Story Points: used to estimate (in a Fibonacci range) the complexity, effort, and risk inherent to the story. Story Points field available for issue type Change request, Task, Story, Bug, Defect, Spike Spike. 


  • DOR: DOR is the abbreviation forDefinition of Ready. 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 summarized in a field, "DoR", which allows tracking what an issue needs to become ready for development.

    The generalized DoR steps are:
    1. PBI created
    2. User Story defined
    3. Acceptance criteria defined
    4. Refinement & estimation done
    5. Ready for sprint


    N.B. This is an optional feature. Set the field manually in refinement sessions, in case that makes sense for your team.

  • DoD projects: A Definition of Done (DoD) is a term from the scrum framework, which describes the agreement of what it means when an item is set to "Done" status.
    Within YME the intent it to validate these three organization-wide requirements for each ticket, 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 and for all teams.
    When closing a Story, Bug or Defect, it is mandatory in YIS to full fill the field "DoD projects":



  • Installation instructions: Optional field used by some teams to store details for deployment, for example if configuration is required or run a SQL on production system. Optional field. 
  • Status: Workflow status summary.

  • Resolution: Resolution is set automatically when an issue is closed.

    StatusResolution
    DoneDone
    Done DeploymentDone - Deployment
    CanceledCanceled


  • Fix/version: Mandatory field used to assign completed developments to a release scheduled to go to production.
    Additionally, on Kanban boards, closed items will disappear from the board once a fix/version is closed, not earlier.

...

The steps in italics are shown on the deployment board, while "Ready for Deployment" or Done or Canceled is the final state on development boards.

...

  • Epic created: work has not yet started (this specific status allows easy searching for open Epics);
  • Define business case: the goal of the epic needs to be made clear - what is the current situation, and why do we need to change this?
  • Define acceptance criteria: we can only celebrate the success of an initiative, if we make clear how we will measure success - what is the acceptance criteria?
  • Assign team: only after the business case and acceptance criteria are clear, does   it make sense to involve a development team.
  • In progress: a developer builds & unit tests their own work to meet acceptance criteria;
  • Review: a peer reviews any code & functionality;
  • Done: the work is completed without deployment needed;
  • Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete.

...

Since at the moment YME works with bi-weekly releases (and sometimes in-between hotfixes), this board collects all work across teams that still needs to be released.

Image Modified

At the top of the screen the quick filter for a team can be activated, which limits the work shown to a single team.