I am a regular user of Jira and/or Confluence as part of one or more UKHSA projects, business or customer processes or work teams.
I have a vested interest in the success of this migration in order to avoid disruption to my day-to-day work and delivery commitments.
About me
My role:
- I play a key role in the day-to-day activities within a project or business process
What is important to me:
- Intuitive and efficient tools that support the day-to-day management of the project
- Active collaboration across the team with minimal risk of version control issues, confusion or duplication of effort
Preferred channels:
- Teams channel
- Confluence
- Direct engagement where required
Impacts
What's in it for me:
- Increased productivity through enhanced collaboration
- Quicker and more efficient sign-on process through SSO
Impacts I may experience:
- There will be changes to drop down options, icons, project key, status or naming ahead of the main migration – the specific impacts will vary project-to-project
- Further instances of drop-down and icon changes at migration to align with broader UKHSA ways of working
- Dashboards, filters or local analysis solutions fed by Jira may change
- Behaviours within workflows and/or Jira Service Management
- Minor functionality or user experience changes as a result of some apps being replaced
- General look and feel changes related to the Cloud version of the tools
| View file | ||||
|---|---|---|---|---|
|
The specific impacts to functionality will depend on which team you work within.
Using the impact assessment materials will be key to understanding which changes will be applicable.
...
Work with your local Administrator to identify any specific use cases that will require testing in UAT (e.g. dashboards, reports, service desk project requirements)
...
Attend the Thursday drop-in sessions with any questions and to provide feedback
...
Complete the training
...
Engage with the Pulse Check Surveys to help us track readiness
...