Versions Compared

Old Version 10

changes.mady.by.user Andy Dingley

Saved on

compared with

New Version 11

changes.mady.by.user Philip Wilsdon

Saved on

Key

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

Welcome

  • Overviews of the iteration

  • Any interruptions / Live Defects

  • Team going through what they’ve achieved during the iteration

  • Feedback from those on the call on what we have done (constructive criticism / praise / questions)

  • Collaboration with those on the call on what to do next

  • Ask questions:

- out loud on the call - really, we’d appreciate you doing this!
- write in the Team meeting chat

Live Issues:

Jira Legacy
serverSystem JIRA
columnskey,summary,created,updated,status
maximumIssues20
jqlQueryproject = TIS21 AND issuetype = LiveDefect AND status in (Backlog, "Being code reviewed", "Check ACs", Documentation, Done, Implementing, "Measure of success", "Ready for development", Refinement, "Released to Prod", "Released to Stage", "Tests/Logs/Monitoring", "Verifying on Prod", "Verifying on Stage") AND created >= 2021-03-01 AND created <= 2021-03-16 order by created DESC
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7

Incident logs

2021-03-03 Person Search Sync Failed [Unable to parse response body]

2021-03-03 Missing Notifications and unreconciled positions

2021-03-01 Legacy Reval: unable to submit revalidation - User Agent/Cloudflare GMC Issue

Dev team demo 'done' work contributing to those goals (no reference to specific Jira tickets, and no reference to work not 'done')

Area

Description

Team Representative

Demo - from Prod URL where feasible

TIS

Update permit to work values to match Oriel

Andy Dingley

Two parts to this
1. Update the values held in the reference table to match Oriel and make them available to edit via the Admin menu - Done
2. Make Bulk Upload and Admins UI use the reference table values instead of outdated, hardcoded, values - Ready to review

Northern Ireland TIS

Reval

ESR

More about Saint Helenes?

Picture of the spec

TIS SS

Fix the FE prod app cognito config so a user can log into TIS Self Service

Retrieve the logged in user's data, rather than a fixed ID

Display message to user when their browser is outdated

Edward Barclay

Demo from stage

Prod Envrionment (combine with above)

Objective Key Results (OKRs) Financial Q4

1st
Iteration

2nd
Iteration

3rd
Iteration

4th
Iteration

5th
Iteration

6th
Iteration

Objective#1

Trainees can access the TIS Self-service app, see their details and be able to fill in their Form Rs, and HEE admins can unlock / un-submit any Form Rs that are submitted from within the TIS app
(i.e. Complete the MVP* for TIS Self-service)

Key Results

  • Onboard the first cohort (c.50) of Trainees so they are set up and using TISSS for submitting their Form Rs - with a 90% preference feedback response compared to how they currently fill out their Form Rs

0.1

0.1

0.1

0.1

  • Identify and address top pain points Trainees have fed back (via support requests, through the Hotjar survey, or other mechanism for feeding back) from using the TIS Self-service app

0.1

0.1

0.2

0.2

  • All Trainees have their current data as managed on the TIS app available within the TIS Self-service app, ready for their onboarding

0.5

0.6

0.6

0.6

  • HEE admins can see and are able to process submitted Form Rs coming in from their Trainees

0.6

0.6

0.6

0.7

...

Info

*TIS Self-service MVP:
Trainees:

  • have a login to TISSS and know what to use it for, and can reset their passwords

  • can access their personal details held on TIS

  • can see their current and future Programme and curriculum membership they are training on

  • can ensure placement details are accurate and have a way of knowing where they are going to be training next

  • have visibility of their assessments including upcoming ones

  • are able to complete their Form R Parts A and B electronically

  • are able to receive support when they have queries regarding using Trainee Self Service or Submitting specific forms

HEE Admins:

  • are able to access submitted Form R's and unlock / un-submit them

Feedback

We really do welcome any feedback you have for us - whether it be negative or positive, or whether it be a suggestion of something we could try/incorporate in a future Sprint Review. We absolutely don’t want to stand still. We’re very happy applying the 12th Agile principle of ‘becoming more productive’ to our Sprint Reviews themselves! Your contributions to this survey are entirely anonymous, should you wish to include anything others might perceive as controversial. We welcome any and all feedback, as long as it is constructive!

...