Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

Page Contents:

  • Description
  • Scope
  • Background
  • User Journey
  • Scenarios
  • Field Validation
  • Related JIRA ticket links
  • For Discussion & Assumptions
  • Agreed Next Steps


Description

The management and recording of any absence undertaken by a learner or trainer.

Component TIS-632


Scope

Request Leave (Trainee)

Approve Leave

Approve Leave (Study Leave)

Manage Leave Approvers

Track Study Leave Allocation & Funding (by Trainee)

Track Study Leave Allocation & Funding (by Trust)

View Consolidated Leave Information (by Team)

OOP


Background

Current Usage

LocationIntrepid UsedVolumes of Request (per month)No UsersComments
London & South East No  N/A  N/A 
East MidlandsYes 115050 (ad-hoc)
  • Leave Manager Plus used
  • Leave approvers use this primarily to approve requests that have come in
  • TPDs are exception approvers, in addition to rota coordintator
  • Allows automated approval
West MidlandsNo   N/A N/A 
East of EnglandNo  N/AN/A 
North EastNo   N/A N/A 
Yorkshire & HumberNo   N/A N/A  
North West No   N/A N/A  
WessexMaybe TBC TBC 
Thames ValleyMaybe TBC TBC 
South WestMaybe TBC TBC 



Recommendation

  1. Develop leave management tool
  2. Teams continue as they are
  3. Develop Hicom advanced tool for all teams


User Journey


JIRA Tickets

https://hee-tis.atlassian.net/secure/RapidBoard.jspa?rapidView=13&projectKey=TIS&view=planning&selectedIssue=TIS-360&quickFilter=41&selectedVersion=11700


Discussion & Assumptions

#QuestionCommentOwner
1










Agreed Next Steps

  • map user journey
  • review scenarios and write up in detail
  • specify field validation changes & rules
  • refine stories to reflect user journey, scenarios and field validation
  • No labels