POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
ry
€ Branch Product Define
[y+] visit Manager workshop
2 meeting
SI Update problem statement catalogue
-)
Update JIRA
as]
a)
= kK kK kK kk
Send for Sendto Move to Sprint Show& Remediation
beer Sallyand deliverables Retro Tell analysis and
review Product folder ideation
Manager workshop
Options elaboration and refinem
Solution ideation
>
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping ‘o be mapping
*
5 Sprint Planning
User/data journey >
1. Ensure tasks/ticketsin JIRA reflect
workin the previous sprint
2._Assign tickets forcurrent sprint
Close
ra)
€ Branch Product Define
o Manager workshop
2 meeting
SI Update problemstatement catalogue
o
Update JIRA
no]
)
xk kK kK kk *
Send for Sendto Move to Sprint Show& Remediation
beer Sallyand deliverables Retro Tell analysis and
review Product folder ideation
Manager workshop
Options elaboration and refine
Solution ideation
>
Green team
Horizon System Improvement Process Guide
Please view in Presentation mode
Red/ Blue teams
Green team
As-is mapping ‘o be mapping
*
Sprint
planning
Map user/data journey/ complete
Branch Product Define
Manager workshop
meeting
Map user/ data journey and complete TC analysis Close
Userjourneys
1. Use information from branch visits, product manager meetings,
define workshops and widerinformation gathering to build out the
usermap using the journey template
2. Capture pinch points and screen-flow diagrams on the map
N.B. Save a new version. Do not overwrite the template in Teams.
kkk kK
Send for Sendto Move to Sprint Show&
peer Sallyand deliverables “Retro Tell
review Product folder
Manager
*
Remediation
analysis and
ideation
workshop
POL00337648
POL00337648
Options elaboration and refine
Solution ideation *
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping ‘o be mapping
*
Sprint
dlanning
Map user/ data journey/ complete TCanalysis
ey Branch Visits fame
£ ,
J Userjourneys only
2 1. Check branch visit schedule/
SI Ur orl the date/ Update problem statement catalogue
o 2. Attend visit
= 3. Afterthe visit, email the branch Update JIRA
oO and area managers to thank them
[4 for theirtime and cc in Oz * tc * * * *
N.B. further details of howto booking Send for Sendto Moveto Sprint © Show& Remediation
a site visit can be found here peer Sallyand deliverables Retro Tell analysis and
review preduch folder ideation
Manager workshop
Options elaboration and refine
Solution ideation *
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
er/ data journey/ complete TCanalysis
1.
w Product Manager meetings Close,
o meeting
2 ed 1. Check Product Manager list to confirm who
o to approach 7
s 2. Setup 15-min meetingto introduce ple EE
a) yourself, workstream objectives and their
= role in reviewing the maps Update JIRA
o 3. Get ahigh level viewof the journey/ pain
= Pants xk * xk &
Main meeting (post branch visit) Sendto _ Moveto — Sprint Show& + Remediation
Diarise longer meeting with product Sallyand deliverables Retro Tell analysis and
manager once more information has been Product folder ideation
gathered Manager workshop
2. Use as opportunity to validate current F
understanding, learn more about pain Rate eraser aie ae etree
points and clarify any outstanding
questions
Solution ideation *
Validate
workshop
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
xk w& FF
wl Define workshop
€ Branch Product DefI
G Manager work) Userjourneys only
2 meeting 1. Confirm the agenda forupcoming
al define workshops with Amaia
s 2. Fillinthe define workshop
a) template based on information
gathered Update JIRA
i 3, Send completed template to Oz
fd EOD Tuesday, for Thursday * * *
working session
ldto Move to Sprint Show& Remediation
N.B. Save a new version. Do not yand deliverables Retro ‘Tell amalysisand
overwrite the template in Teams Huct folder ideation
ager workshop
Options elaboration and refine
Solution ideation *
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
Map
er/ data journey/ complete TCanalysis
xk wk *
2)
€ Product Define
rj Manager workshop
2 meeting
SI Update problem statement catalogue
= Update problem statement catalogue Close
a
> all >
ra) First tab of the problem statement catalogue
[ag * tc * Uploadall relevant points from the pain point catalogue
* Allanalysis from branch visits, define workshops, product manager
Send for Sendto meetings etc. should be captured in this document
Beer Sallyand I painpoints/analysis captured here should be included on the user
review Product journey mapsat their corresponding pinch point (the exact pointin
Manager the process the pain point occurs)
Second tab ofthe problem statement caslonue
* Towards the end of analysis, pain points should be grouped together
a and consolidated to create official problem statements
; Solution ideation
G * Problem statements should be concise, informative and summarise
2 the entirety of the probleminthe title alone
c * Allanalysts in an EPIC should work together to ensure there is no Validate
oO repetition of problem statements across user, data or TC analysis workshop
7)
S
[G) N.B. The problem statement catalogue must mirror the inputs for
remediation and ideation workshops exactly,
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
Map user/data journey/ complete TCanalysis
mk OUlkKhUK
€ Branch Product Define
a t Manager workshop
2 meeting
SI Update problemstatement catalogue
o
3 Update JIRA Glose
oO
& kk
+ Allanalysts must ensure JIRA is up to date on a daily basis by creating
Send for Sendto subtasks for each task (EPIC) they are assigned and by moving the
beer Sallyand stories and the task to the current/right state.
review Product * JIRA must reflect the work remaining, as well as the work complete
Manager * Itisimportant to use the comments feature to interact with other
through JIRA
* Tag the Scrum Master when youare blocked onan issue/where you
require wider assistance.
+ Allanalysts must ensure JIRA is up to date before going on annual
leave
and refinement
*
Validate
workshop
Solution ideation
Green team
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
Map
*
Branch
er/ data journey/ complete TCanalysis
xk
2)
= Product Define
a Manager workshop
2 meeting
f)
=I
)
i)
oO
[4
Sen
bq
rev]
E
o
[)
2
[=
oO
[)
rs
1G}
Userjourneys
1. Create “peerreview” subtask onJIRA and
assign to Sarah-Jane Brush
2. Include the Teams link tothe journey
3. Move into the “Peer Review” column on
the backlog
4, Monitor JIRA for any comments/ actions
Data journeys
1. Create “peerreview subtask on JIRA and
assign it to yourself
. Attend the peerreview session every
Thursday
. Move into the “PeerReview” column on
the backlog
N
w
Update problem statement catalogue
Update JIRA
y Send for peerreview
*
POL00337648
POL00337648
Remediation
analysis and
ideation
workshop
Options elaboration and refinem
Solution ideation *
Validate
workshop
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping ‘o be mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
Branch
ra)
€ Product Define
© Manager workshop
2 meeting
SI Update problemstatement catalogue
o
Update JIRA
no]
)
Send to Sally and lose
Sendfor SenI Product Manager for review
beer Sall
review Prod Ensure all comments from “Peerreview” have been actioned before
Man
Send to Sally (all maps)
1. Create “PO review” subtask on JIRA and assign to Sally Rush
Include the Teams link to the journey
2
3. Move intothe “PM/ PO Review” columnon the backlog
4. Monitor JIRA for any comments/ actions *
Send to Product Manager (userand data journeys)
1. Create “PM review” subtask on JIRA and leave it unassigned
2. Email the journey link orcopy of the journey to the Product Manager
3. Wait days/end of sprint for feedback before moving to deliverables
folder
a)
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping ‘o be mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
Branch
W
= Product Define
a Manager workshop
2 meeting
SI Update problem statement catalogue
o
Update JIRA
i)
oO
a xk ne
Move to deliverables folder Close
Send for Sendto Moy
peer Sallyand elivé Ensure all comments from “PM/PO review”
review Product foll have beenactioned before
Manager
Allmaps
1. Onceallpeer/PO/PMfeedbackhasbeen IMieMRPe Mee iememe he dmemiens
received and actioned, move map tothe
deliverables folder
Ensure the file is named correctly Solution ideation *
according to the naming convention
Move the task to “Done” in JIRA and
include the Teams file link
Green team
» oN
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping ‘o be mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
Branch
2)
E Product Define
o Manager workshop
2 meeting
SI Update problem statement catalogue
-)
Update JIRA
ss
QI
od xk wk *
Sprint retro Close
Send for Sendto Move to
peer Sallyand deliverables . Attend session prepared to
review Product folder discuss Sprint successes/
Manager improvement opportunities
Options elaboration and refinement
Solution ideation *
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping ‘o be mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
Branch
W
te Product Define
ol Manager workshop
2 meeting
SI Update problem statement catalogue
o
Update JIRA
i)
oO
Fs xk wk wk kk
Show and Tell Glose
Send for Sendto Move to Sprint Sh
peer Sallyand deliverables Retro Tt all
review Product folder 1. Check with Amaiatosee if you
Manager are scheduled to present at
the Showand Tell
2. Ifyes, complete the Showand
Telltemplate and sendtoher
N.B, Save a newversion. Do not Solution ideation *
overwrite the template in Teams.
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
mk OUlkKhUK
€ Branch Product Define
a tt Manager workshop
2 meeting
SI Update problemstatement catalogue
o
Update JIRA
no]
)
4 k & kk ®t
Remediation and ideation workshop Close
Send for Sendto Move to Sprin
peer Sallyand deliverables ‘Retrd all
review Product folder 1. Ensure all pain points captured in analysis are included in the first
Manager table of the problem statement catalogue
2. Use these to create comprehensive yet concise
3. User, data and TC analysts should meet before to ensure problem
statements are aligned with no repetition
4, Work with Scrum Master to schedule the workshop
5, Followeddetelledinstructions tocompletetheremediationand *
ideation analysis template
Validate
N.B. Save a new version. Do not overwrite the template in Teams. workshop
Green team
POL00337648
POL00337648
Horizon System Improvement Process Guide
Please view in Presentation mode
As-is mapping be mapping
*
Sprint
planning
Map user/ data journey/ complete TCanalysis
mk OUlkKhUK
i Branch Product Define
o Manager workshop
2 meeting
SI Update problemstatement catalogue
o
Update JIRA
3
I ; a .
A * tc ke Options elaboration and refinement close
Send for Sendto Move to g Analysts
peer Sallyand deliverables 1. Use the options elaboration and refinement template to build out
review Product folder template
Manager 2. The contextslide should be completed at a capability level e.g.
Bureau Services
3. Problem statements and Options slides should be completed ata
sub-capability level e.g. Travel Currency
Ee 4, Business Analysts should not fill details on “In/Out of Scope”,
o “Residual Issues” and “Costs”. This is Product Owner responsibility
[.) (Sally)
2
5 N.B. Save a new version. Do not overwrite the template in Teams. b
LF)
fc} Ownership of this document has not been determined yet and the
developmentof this stage is still in flight