Q1 January - March
Q2 April - June
Q3 July - September
Q4 October- December
Application | Subject | Jira Issue | Planning | Status | Current situation |
General | AFOS migration Jira/Confluence/Bitbucket | Q1, Q2 |
Project canceled. | ||
General | Migrate Jira/Confluence/Bitbucket to Yamaha AWS environment | Q3,Q4 | Impediment: support required from Support Partner | ||
General | Servicedesk redesign including portal (Jira SD project) | Q3, Q4 | |||
General | YMES use Jira/Confluence Service management project including support portal or different project setup? |
| Q2 | Preparation start Q2, 13-04-2023 meeting with Eva Bonilla and other YMES stakeholders | |
General | YME (Technical) Service Division, New Jira Service management project including support portal | Q4 | Intro meeting with team has taken place. | ||
General | License renewing Jira/Confluence/Bitbucket including addons. Most licenses expire March 2023 and some in June/July 2023. Licensed need to be requested before the end of January 2023 at Avisi. | Q1 | Licenses renewed for 1 year, new expire date 16-03-2024 | ||
General | SSO Setup and new ADFS user sync for Jira, Bitbucket, Confluence (SAML addon) | Q2 | SSO Jira in TEST environment, in TEST | ||
General | Two factor authentication | Q3 | |||
Jira | P&A Customer Support Service management project including support portal | Q1 | P&A Customer Support project (PACS) | ||
Jira | Jira Addons to be discussed, for example usage of Big Picture or use different addon for resource planning/roadmap (also to be discussed further with Bjorn) | Q2, Q3 | Information provided to PMO team: Big Picture license expires on 15-03-2023 one year renewal USD: $ 9.400,00 / € 9.063,29 Advance Roadmaps information: https://www.atlassian.com/software/jira/features/roadmaps?tab=advanced | ||
Jira | Jira Align Usage? To be discussed for PMO planning. | Q2 | Jira Align will not being implemented the coming year, to expensive/advanced for current phase in Agile Transformation. | ||
Jira | Jira ISMS project for (recurring) tasks and policy and procedure development | Q1, Q2 | ISMS Project created, working on Configuration in close collaboration with Harold Renssen | ||
Jira | New Jira Project for Compliance, archive Jira-Project IA. | Q2 | |||
Jira | Support agile teams in usage of Jira and finetuning YIS project. | | Q1, Q2, Q3, Q4 | Continues support during Agile transformation
| |
Jira | Migrate Jira development projects YM, BA, BI, B2C to YIS | Q1, Q2 |
| ||
Jira | Integrate Infra in YIS project or separate project but no changes made via SD. | Q2, Q3 | Cloud-Rangers team started working in YIS Infra Board is being setup | ||
Jira | Coaching ambassador Distributors (key users) usage of Jira and Confluence | Q2, Q3 | |||
Jira | Jira/Confluence onboarding/ training
| Q1, Q2, Q3, Q4 | Creation of Basis training material : In progress under Space: Atlassian | ||
Jira | (EU) YNS project support, Backbone Sync - continues support and troubleshooting | Q1, Q2, Q3, Q4 | Continues support for troubleshooting Sync errors and new user registration | ||
Jira | Jira permissions -> move to authorization per role and groups for global permissions? | Q3, Q4 | Can only being started after finalizing Agile transformation, new roles | ||
Jira | Jira project cleanup for field configurations and screens | Q1, Q2, Q3, Q4 | YIS Cleanup in progress PMO Cleanup started | ||
Jira | Alignment Jira usage IS-Business forward requests between projects? | Q2 | IT <-> Ecommerce | ||
Jira | User Onboarding process (including alignment HR, Facility, reception) | Q1 | Onboarding procedure is aligned, Jira Process and configuration in place. Released on 1-4-2023. | ||
Jira | User Offboarding process (including alignment HR, Facility, reception) | Q2 | |||
Jira | User Application access process (including Admin rights) | Q2 | |||
Confluence | User Manuals (Public) Space redesign, include permissions redesign (distributors, YME, third parties, dealers etc.) Redesign based upon product instead of division/department |
| Q3 | ||
Confluence | Simplify permissions and introduce space owners |
| Q2, Q3, Q4 | Space Owners are being appointed and added to the Space description. Simplify permissions step 2. Will already being done for new Spaces. 3 levels: RO,RW and SEC. SD can be requested to add members to the groups. |