Versions Compared

Key

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

...

FieldValue
WorkstreamEU XXXXX
ComponentYNS
TeamDrop down list
Ticketgroup(s)Optional, advised to use for QRP planning, managed by PO's. The options to use: QRP-Year-Q(uarter)

These fields are expected to be filled out. If you forget either of them, you will not be seeing your issue in the roadmap overview.

...

  • AVENGERS
  • B2C-CDP
  • B2C-DIGITALUM
  • B2C-EPAM-DEVOPS
  • B2C-EPAM-MOTORS
  • B2C-EPAM-WAVERUNNERS
  • CLOUD-RANGERS
  • CRM-KANDO
  • DRAGONBALL
  • EU Accounting
  • EU S&L (P&A)
  • EU S&L (Units)
  • EU S&L (WTY)
  • LIGHTBEAM
  • MARVELS
  • QUICKSHIFTER
  • TRANSFORMERS
  • TRICITY
  • WOLVERINE
  • YAMALUBE


CREATING an EPIC

An EPIC is ALWAYS created in the YIS project. YNS EPICS are the responsibility of the PO's and WS leads to maintain. They are the owners.

Creating an EPIC is considered to be a basic skill for members (via CREATE). See also the Jira Basics Training. You need to follow that training first, before you continue this manual.

For YNS there are some specifics one must be aware off. 

Image Added

Here you see the component being filled with YNS, you see a correct parent link to the feature and the workstream is correctly filled out (EU S&L (UNITS)). 

To plan for a QRP, PO's will also set the TICKETGROUP(s) to the quarter of delivery (e.g. QRP-2024-Q1). This helps to create a special advanced roadmaps filter solely focusing on what teams have committed to for a quarter.

Anchor
CreateEpicParentlink
CreateEpicParentlink
CREATE an EPIC parent link to a FEATURE 

One important thing to understand is the place in the project structure before you make a link towards a FEATURE. Check the YNS roadmap, find your PDD and milestone under it and not the feature YNEU number you want your EPIC to be linked to.

  • EDIT  the EPIC
  • Go to PARENT LINK
  • Type the name of the feature and save the change.

Image Added

Result should be something like this: 

Image Added

CREATING a STORY or TASK and LINK it to the correct EPIC

CREATE an EPIC parentlink to a FEATURE 

...

A story or task should always be tied to an EPIC. You will not see them in the project org structure if you forget to do that. 

Connecting may only be done by creating an EPIC LINK. That is a particular link field that you can see when you edit a story or task. Type the name of the epic in the epic link field, select it and a story is connected.

Image Added

When you create a story directly out of an EPIC, you do not need to do this, then the link is instated automatically. 

Image Added

CREATE a FEATURE parent link to a MILESTONE

Usually this is only done by PMO or WS leads, and means we are specifying the project better. The action is similar to making a parent link within an EPIC

The difference is you need to first create a FEATURE or find an existing FEATURE and know to which MILESTONE it needs to be connected.