Versions Compared

Key

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

Logistical things: pre-start date, or first few days

...

Before their first day

1Request an HEE Office365 email address/account by completing

Step

Coordinator

Who

Complete the new starter form here. This will also inform IT of equipment requirements, request an HEE M365 email address / account and facilities

for

will then be automatically alerted to issue a building pass / key fob.

 2Add the new user to the O365 TIS Group and TIS Team3Share the tis.team@hee.nhs.uk calendars (Sprint Ceremonies and Team Availability) with full edit access4Request a Stewart House building pass (London staff) / Manchester access5Fire Drill on Thursday morning 9:30am - meeting point just outside the bottom of the stair well behind our area (London staff)6

  • Decide who is going to be their mentor (and get agreement from the mentor!)

  • Plan a team in-person meetup to welcome the new starter

Line manager

Once the M365 account has been created, shortly before starting:

  • Add them to the M365 TIS Group: “Trainee Information Systems”

  • Add them the TIS Support “Team”

Line manager / Anita Cheng

  • Share with them the Team Availability with full edit access
    [Note that this needs to be done by logging into Office 365 online and opening another mailbox - tis.team@hee.nhs.uk, going to Calendar, then right clicking the calendar in order to edit the Sharing and permissions.]

Anyone with access to shared mailbox TIS.Team@hee.nhs.uk

Slack invite:

  • this can be given in advance of starting (using their private email, which will then need switching over to their work email once they start)

  • add to relevant channels and groups (standard ones will be: hack-day, high-level-estimations, one-team-tis, sprint-planning, sprint-refinement, sprint-retrospective, sprint-review, sprint-stand-up, team-tech-sharings, wall-of-failure, whats-better, fire-fire, tis-team-london/manchester [delete as appropriate], internal-admin-team-general/trainee-team-general [delete as appropriate], monitoring, monitoring-ndw, monitoring-prod, notifications-jira, arbitrary, general, link-sharing, new-starters).

Getting them involved in Slack before starting helps make them feel part of the team / involved / expected / wanted. And it eases them into the work / the range of work / the lingo we use ahead of time.

Any Slack Admin (Rob Pink, John Simmons (Deactivated), Andy Dingley, Joseph (Pepe) Kelly)

On their first day

Step

Coordinator

If the new starter is going to be working from home significant amounts of time, they should look at the Home office equipment ordering page (once they have access to HEE Connect, through an M365 account set up)

Line manager / mentor / Anita Cheng

Follow up with Facilities for a Stewart House / 3 Piccadilly building pass.

Line manager / Anita Cheng

Add to Metabase. And ask James Harris for a quick tutorial.

Any Metabase admin (Joseph (Pepe) Kelly, Andy Dingley, Ashley Ransoo, James Harris, John Simmons (Deactivated), Yafang Deng)

Add to Google Analytics.

Any GA admin (TSS and TIS Support website: Jon Bowlas and his team / Andy Nash (Unlicensed), TIS: Ashley Ransoo or Jon Bowlas and his team)

Create an Atlassian account for Jira and Confluence and add the team member to the Atlassian group 'TIS Team'. If a developer, add to the group 'TIS Developers'.

7Slack invite - this can be given in advance of starting (using personal email, and email amended once the HEE email is set up), and add to relevant channels and groups8Walkthrough Confluence, JIRA and Slack introducing structures and how we use them9Introduce to the rest of the team! including remote/HEE based and during meetings (smile)10

Any Atlassian admin (John Simmons (Deactivated), Andy Dingley, Joseph (Pepe) Kelly)

Ask new user to update the contact

page with

list page with their details and

take/store a 'headshot' photo in the Team Photos page11Update the TIS Team powerpoint, print and replace on wall12Explain how we broker standup attendance through Slack channel - invite to this channel13For technical staff, arrange to have your laptop's MAC address added to the whitelist. This is to bypass content filtering in London

Settling in: 1st Sprint

#StepCoordinator1Sessions on HEE / History

create an avatar in Atlassian / Slack

New user themselves

When possible, and especially in team meetings, Introduce to the rest of the team! (smile)

Whoever is running the meeting / event

Highlight we’re still working from home by default, but will likely be a hybrid working team in time:

  • pros and cons (focus, work life balance, etc / isolation, collaboration, body language)

Alert them to the fact there’s a fire drill on Thursday morning 9:30am - meeting point just outside the bottom of the stair well behind our area (London staff).

Line manager / mentor

Walk the floors - tea points / toilets / meeting spaces / cafés / etc.

Line manager / mentor

Settling in: 1st Iteration

Step

Coordinator

Sessions on HEE / history of the TIS programme / other tech teams in HEE / HR /

AppraisalSimon Meredith (Unlicensed)Alistair Pringle (Unlicensed)

Settling in: 2nd-4th Sprints

...

Sprint # 1 (to ensure he's fully occupied, we'd need to be quite structured in scheduling the following, and probably have some 'go to' things for him to do / take away actions from these sessions for when we are necessarily unavailable during that first Sprint)
  1. sessions with you on HEE / history of TIS / other tech teams and tech portfolios in HEE / HR / Appraisal
  2. sessions with Phil and I on Agile / Scrum / LeSS / OKRs / culture / remote working
  3. sessions with Andy and Pepe on tech stack / standards / technical side of the team culture / Code reviews etc
  4. ? sessions with Rob / Elisa / James / Jon / James H / prog team on the wider landscape ?
Sprints # 2-5

...

appraisal.

Line manage / mentor

Sessions on Agile / Scrumban / OKRs / remote working / team culture.

Line manager / mentor / Delivery Manager

Line manager / mentor / Delivery Manager

  • Walkthrough Confluence, JIRA and Slack introducing structures and how we use them.

Line manager / mentor / Delivery Manager

Sessions on the wider HEE / NHS landscape? With James Freed / Jon Howes / Rob Pink / Elisa Lakhan-Hector / James Harris / others…

Line manager / mentor / Delivery Manager

Introduction to the Work In Progress (WIP)

Lead dev (for the Product Team the new starter is in) / Line manager / mentor

Settling in: 2nd-4th Iterations

Step

Coordinator

Embed new starter for an Iteration or two in each Product Team / run through of the distinct areas of the codebase: TIS, TIS-ESR, Reval, TSS.

Lead dev (for the Product Team the new starter is in) / Line manager / mentor

Actively review progress (day-to-day, week-to-week). More formal ‘sit-down’ after new starter has been embedded in each Product Team for an Iteration or two, to discuss first impressions / questions and ideas they have / where they are best deployed to begin with.

Lead dev (for the Product Team the new starter is in) / Line manager / mentor

Assign access to Pre-prod and Prod for the apps within their Product Team, as needed.

Lead dev / Line manager / mentor

Attachments:

Induction Checklist https://connect.hee.nhs.uk/Interact/Pages/Content/Document.aspx?id=4114&SearchId=1569276&utm_source=interact&utm_medium=general_search&utm_term=induction+checklist

Employee benefits

https://healthservicediscounts.com/

https://www.hee.nhs.uk/about-hee/work-us/staff-benefits