View Source

YAMAHA TEAMS

Single select field needed on sub-task/story/epic level. Projects will keep the old label field.

Create custom field in Jira, single select: Yamaha Team Bianca van der Meer
Add field options from BigPicture = Bianca van der Meer
Link to screens = Bianca van der Meer
Change Board filters to add new field in the selection.
Migrate data for story level items - for matching options (bulk update) Bianca van der Meer / AJ van Spanje [AgileVisor]
Implement only for YIS, later for other projects. Remove Team Yamaha label field, copy all first selected teams to new field
23-08-2022
- DMS - story
- DAYCARE all issues
- YAMALUBE = story only
- Correct issuetypes with Yamaha Teams
- Reindex
- IN PROGRESS AJ: DMS all, SF all, daycare, marvels, wolverine, b2b-as400
- NO CONTENT: HIQ
Migrate data for epic level items = PO's to deduplicate team options
BigPicture interface mapping to new field Bianca van der Meer
Update Confluence, teams and dashboards (procedure) = Bianca van der Meer
Migrate data for story level items - for not matching options = PO's/managers
ServiceDesk issuetypes update Yamaha team add to fields
- ServiceDesk issuetypes process update, single select instead of multi select Bianca van der Meer
YPM multi select for projects Bianca van der Meer
SD link screens to new Team Yamaha field (double maintenance for YIS issues) Bianca van der Meer
YPM - transition move to development board screen etc. Team select screen Bianca van der Meer
Update filters → used in dashboards SD teams Bianca van der Meer
Update automation rules Bianca van der Meer
- SD_B2B Update solution group, Team Yamaha for issues received by email
- SD_B2C Update solution group, Team Yamaha for issues received by email
- SD SD_INFRA Update solution group, Team Yamaha for issues received by email
- SD Create Onboarding tickets for departments
- SD Update Epic Link and yamaha team based upon application choice user (create issue event)
- SD Update solution group, Yamaha Team based upon application and wrong department
- SD User Offboarding Update issue fields when request received by email
- SD User Onboarding Update issue fields when request received by email
- SD - Create JSOX-CHANGE authorization tickets out of Infra for management
- SD - Create JSOX authorization tickets out of AS400 for management
- SD - Create JSOXM / TASK / INC authorization tickets out of AS400 for management
- SD - YAMS and YMPACT deployment approval requests
- SD Auto close unauthorized e-mail requests and categorize authorized senders
- PFB - Move deliverable to development board
NEW: Task type this is no new Yamaha Team field on creation, for Story, Spike types its in place (Dzmitry) Bianca van der Meer / AJ van Spanje [AgileVisor]
NEW: Default Yamaha team on sub-tasks (from Dzmitry) Bianca van der Meer / AJ van Spanje [AgileVisor]

STEP TO STEP GUIDE Team Yamaha to Yamaha Team:

Edit Yamaha Team field configuration, Add all issue types and all IT project but YPM Project, Programme
Add Yamaha Team field to all screens where Team Yamaha is used.
Bulk updates per team to fill Yamaha team field, same as Team Yamaha. If there are more then 2 removed from selection.
Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty. Fill Yamaha team field if we know team.
Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty, inform team leads to set Yamaha team field.
Connect Yamaha team field in Big Picture for YIS resource planning scrum teams.
Add team members scrum teams (Bianca/René, help of AJ?)
Check workflows/automation rules for Team Yamaha/Yamaha team CAB/YPM
Set Yamaha team field required in YIS configuration scheme
Set Yamaha team field required for other Dev, CAB scheme as well.
Remove team Yamaha from screen in YIS.

RENE REQUIRED

Resolution stop using, set per project/workflow
- Create list per project/workflow YIS & development projects = Done & Canceled Bianca van der Meer / AJ van Spanje [AgileVisor]
- Review list per project/workflow René van der Pal
- SD resolution list = Rene, also to be discussed with BAU team/ SD Infra René van der Pal / Bianca van der Meer
Remove/change resolutions from reporting
Jira admin changes communication = review Bianca van der Meer / René van der Pal
SQL results now logged under ticket Change result logging (30 min meeting) Bianca van der Meer / René van der Pal / Nico Meijer
Big Picture PROG-6 changes to assign only teams via Big Picture Home -Root Bianca van der Meer
Big Picture check teams for members and availability in Big Picture Home -Root René van der Pal
- Onboarding/offboarding → teams BP authorization check global teams Bianca van der Meer

YIS IMPROVEMENTS

NEW: Add Jira rights for PO & BA to set sprint goal (From SF)
- YIS PO/SM/Dev access rights draft - AJ: project roles exist and are assigned to logical rights in permission scheme.
- User groups - Bianca van der Meer
CLEANUP / USABILITY
- YIS default screen config clean up
- YIS field config clean up
- NEW: on closing pop-up, add mandatory fix/version field (from AJ) AJ van Spanje [AgileVisor]
- Disappearing comments pop-up
- Split error YIS: solution group, Yamaha team
- BEW: Subtask to inherit team name!!!
- custom fields to local contexts
DoD required / UAT / on epic?
- Only on issue type when used (scheduled for deployment) AJ van Spanje [AgileVisor]/ Bianca van der Meer
- DOD project = team → Confluence Bianca van der Meer
- DOD Projects= review Bianca van der Meer / AJ van Spanje [AgileVisor]
Epics process
- create meaningful epics WF (Arthur) AJ van Spanje [AgileVisor]
- Epic points / WSJF op epics (Arthur) AJ van Spanje [AgileVisor]
- where should we create epics? YPM or YIS? (Arthur, Benjamin) Bjorn says there is no standard. B2B uses YPM, B2C uses B2C. And no owner who can decide on this. AJ van Spanje [AgileVisor]
- can we have a Yamaha-Team for PO's per product, to prioritise/prepare work? (Arthur, Benjamin) Salesforce-POs Bianca van der Meer / AJ van Spanje [AgileVisor]
Reporting request from Vladislav addon Approved by René AJ van Spanje [AgileVisor] / Bianca van der Meer
- https://marketplace.atlassian.com/apps/1222051/status-time-free?hosting=datacenter&tab=overview install addon Bianca van der Meer
- Reporting /addon use instructions
YIS board transitions - AJ van Spanje [AgileVisor]
- Ympact team kanban board
  - Fix Ympact board filter to include team name
  - Create new Ympact kanban board
  - Remove old Ympact kanban board
  - Create Ympact scrum board ON HOLD
- Logistics team kanban board
  - Fix Logistics board filter to include team name
  - Create new kanban (template)
  - Remove old kanban (non-template)
  - Create Ympact scrum board ON HOLD
Installation instructions
- Location of installation instructions → impossible. Let's remove the default text instead AJ van Spanje [AgileVisor]
- Installation instructions local context? Does Ympact use this? - AJ van Spanje [AgileVisor] (Rob de Vries rob.devries@yamaha-motor.nl) → Ympact does use this. Cannot limit to local
- NEW: Rename "Installation instructions" to "Code/Configuration Details" (From SF) Check with Ympact team, EPAM - AJ van Spanje [AgileVisor]
Releases:
- NEW: Can we have a "target release date" field in Jira? (SF team) - AJ van Spanje [AgileVisor]
- Release numbers in versions = Marcel/AJ
- Naming convention versions, in Confluence Release numbering procedure Marissa Smit / AJ van Spanje [AgileVisor] Release preparation
- Target release date global context? Marissa Smit
- NEW: Make Release preparation easy to find in Confluence
- Release documentation condensation in Confluence Marissa Smit
- Fix/version use? Limit to release managers? - Marissa Smit
- Affected version/s System Field add to screens for YIS AJ van Spanje [AgileVisor]
Test types/screens investigation AJ van Spanje [AgileVisor]
- Investigation AJ van Spanje [AgileVisor]
- NEW: Test types clean up?: sub-test execution & test setAJ van Spanje [AgileVisor]
- NEW: Standardise field order on test screens?AJ van Spanje [AgileVisor]
- NEW: Remove fix/version from test screens? (Alexa) AJ van Spanje [AgileVisor]
YMPACT OMS move for issuetypes bug/defect Bianca van der Meer / AJ van Spanje [AgileVisor]
Worklog permissions
Add validation for deploymentapprovers group for status to done deployment Bianca van der Meer
YIS- integrate Infrastructure, including J-sox approval workflow (currently included in SD Default Workflow) Bianca van der Meer AJ van Spanje [AgileVisor]

JIRA IMPROVEMENTS

Issue type description update
Component as systems remove from screens Bianca van der Meer
- Empty component fields, move to custom field Portfolio Bianca van der Meer
Bigpicture cleanup: team only setup in Root, then assigned in PROG Bianca van der Meer
Req. SQL approval, new issue same like req. job change request & add functionality to DEV projects Bianca van der Meer
NEW: on B2C project fix/version isn't mandatory? Bianca van der Meer
Jira-test Incoming/Outgoing mail settings change : Bianca van der Meer / Daan Delpeche [X]
EPIC used for operational support, deployments, user authorization, Jira activities, J-sox, gdpr, sql approval, job change request, replace by SD classification list = Bianca van der Meer / AJ van Spanje [AgileVisor]

- List epics
- Change to field to single select SD classification or components field Bianca van der Meer
  - Start with new tickets
  - Automation rules; create, copy from etc.
  - Workflows
  - Filters
  - Dashboards
  - Boards
  - Bulk update outstanding tickets, old Epic link, new SD Classification

ARCHIVE OF WORK DONE

YIS:
- Workflow cleanups YIS:
  - NEW: Defect has Generic Test WF assigned, instead of Generic Bug WF. Correct this? (From Diego email) - AJ van Spanje [AgileVisor]
  - NEW: "Done deployment" resolution is set for status "Done" illogically (From SF) - Bianca van der Meer
  - NEW: Spikes: can we please skip statusses in WF? (From SF) - AJ van Spanje [AgileVisor]
  - Move bug & defect to Development flow - needs communication AJ van Spanje [AgileVisor]
  - Move Test issuetypes to Subtask flow - needs communication AJ van Spanje [AgileVisor]
  - Move Epics to Subtask flow - needs communication AJ van Spanje [AgileVisor]
  - Rename Subtask flow to Simpe 4-step flow AJ van Spanje [AgileVisor]
- Location of acceptance criteria → impossible. Let's deactivate acceptance criteria for this reason, and use Description instead. AJ van Spanje [AgileVisor]
- Create/correct new YIS boards (template/filter) - AJ van Spanje [AgileVisor]
  - B2B bord transparancy = Mohan - AJ van Spanje [AgileVisor]
  - Scrum & Kanban template AJ van Spanje [AgileVisor]
    - Marvels epic needs to be removed → Show Rene first AJ van Spanje [AgileVisor]
    - Marvels old scrum needs to be removed → Show Rene first AJ van Spanje [AgileVisor]
  - Create kanban board template = HIQ → REVIEW Bianca van der Meer
  - Java kanban board needs template + filters → move to template AJ : New board AJ van Spanje [AgileVisor]
  - B2B-apps java kanban needs to be removed - Check with Valentina - AJ van Spanje [AgileVisor]
  - All test boards need to be made standard or removed - investigation Andrzej - confirmed - AJ van Spanje [AgileVisor]
  - Setup Wolverine scrum for Tania https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=107&view=planning&issueLimit=100 AJ van Spanje [AgileVisor]
  - Setup Daycare scrum for Tania https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=108&view=planning.nodetail&issueLimit=100 AJ van Spanje [AgileVisor]
  - Java kanban board - remove old board: https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=97&view=planning.nodetail&issueLimit=100 - Check with Valentina & Tania
PMO:
- NEW: business value activeren op stories (Arthur) - AJ van Spanje [AgileVisor]
- NEW: business value activeren op epics (Arthur) - AJ van Spanje [AgileVisor]
Other JIRA-projects
- New Issue type Defect and Change Request for all development projects, yes = Bianca van der Meer
  Issue type Defect and Change request added to
  
  Already used in YIS
- Workflow had to be changed, resolution must be empty for Bitbucket/ Jenkins pull request else a warning is generated. Bianca van der Meer
  - Generic Bug Workflow Added status Scheduled for deployment, Added transition To scheduled for Deployment, condition added empty resolution field.
  - Generic Development Workflow V2 Generic Development Workflow V2 Transition To scheduled for Deployment: changed condition to empty resolution instead of adding resolution Scheduled for deployment.
    
    Example warning YIS-614 bug fix
Sample software project, not used - delete= YES = Bianca van der Meer
Big Picture:
- Bigpicture cleanup: team only setup in Root, then assigned in PROG Bianca van der Meer