Iterate adding an early career teacher or mentor and prepare to build more 🏫
Design - Iterate pages in adding an ECT or mentor from user research round
Analysis - Analyse what screens we need to design for when adding a mentor goes wrong
Design - Design pages for adding a mentor where there is an error or issue
Design - Reviewing content generally and defining a style guide or adding to the content strategy
Design - Design pages to add an early career teacher when an appropriate body has already claimed them in the induction service
Analysis - Write up tickets and kick off with devs for new pages agreed in the add an early career teacher or add a mentor journey
Analysis - Write up analysis for how we handle CIP and school-led schools, ECTs and mentors
Development - Build pages we've agreed are ready in the Add an ECT or Add a mentor journey
Research - Check in with the strategic design team and think about how we could survey or ask schools for the info they use to help them fulfil their registration responsibilities
Collect insights around transfers of ECTs and mentors 🏫
Analysis - Look at how transfers work in ECF1 and map it out
Research and design - Collect insights, problems, requirements and needs related to transfers to kick off on our away day
Whole team - Talk about how to decide if transfers will be two separate journeys or 1
Start to plan data model, roadmap and how we can work with LPDOB ☁
Product - Plan in lead provider related milestones on roadmap
Whole team - Draft the financial side of the data model, ready to check with PDOB
Research - Investigate what support might be needed for 2025 changes and where research or design might need to help
Analysis - Prepare analysis to bring to LPDOB on how we might want to expose LP or DP details to lead providers
Continue migration and up instances to speed it up 👾
Development - Start looking at migrating mentorships and training periods
Development - Create way to view data imported by school
Appropriate body sprint goals 🆎 🔍
Test what we've built so far for the new induction service
Kas - Plan how we want to test what we've built of the induction service so far
Get together to test it!
Begin the first iteration of the Extensions user journey and record content 📏
Kas - Finalise content for extensions flow
Analysis - Update service rules on Github about extensions
Nice to have
Development - Add extensions journey
Continue migration data preparation 🐦
Development - Work out the tricky induction periods we need to migrate from the TRS
Analysis Work out what errors we're expecting from migration import
Wrap up DfE Sign in process 🐦
Development - Match up the appropriate bodies with their organisation IDs so they can access the service
Start looking at round 2 of UR 🗣
Research - Agree high-level priorities for round 2 with appropriate bodies.
Design Create term validation lofi screens to test on UR round 2
Development Build journey and error messages.
UR - Clarify dates for UR round 2. Week of the 25th or the 2nd Dec.
Kas Create scenarios to test for each user flow
Align on comms to external users
Design - Prepare meeting with ECTMAN and Mosaic team
Complete analysis & design on Release & Outcomes journeys, ready to build unhappy paths next sprint 🤔
Analysis - Define a complete list of service rules for Release & Outcomes & populate backlog
Nice to have
Design - Create lo-fi designs for Release & Outcomes errors
Create and agree admin console rules with TRA transformation 🖼
Design - Define admin console rules for CPD, and a set of rules which dictate when updates should / shouldn't be possible in CPD or TRS console (including exemption rules)
Analysis - Service rules for user flows in admin console
Nice to have
Design - Lofi design of admin console
Prepare governance for AB portal
Analysis - Review drafted DPIA work and update with any AB requirementsDelivery - Scheduling PEN test contract. Main contact is Saheida
Nice to have
Development - Prepare PEN test
Not a priority
Define service rules for viewing records flow
Analysis - Viewing records flow - when an ECT has concluded induction or been released and mid-induction changes, including correcting data (e.g. what mistakes should ABs correct themselves).
Define non-functional requirements
Analysis - Non functional requirements include expectations on users visiting, load testing - volumes of inductions at different times of the year.
Sprint 14 - 👻
Lead provider and school sprint goals
Iterate adding an early career teacher or mentor and prepare to build more 🏫
Design - Iterate pages in adding an ECT or mentor from user research round
Analysis - Analyse what screens we need to design for when adding a mentor goes wrong
Design - Design pages for adding a mentor where there is an error or issue
Design - Reviewing content generally and defining a style guide or adding to the content strategy
Design - Design pages to add an early career teacher when an appropriate body has already claimed them in the induction service
Analysis - Write up tickets and kick off with devs for new pages agreed in the add an early career teacher or add a mentor journey
Analysis - Write up analysis for how we handle CIP and school-led schools, ECTs and mentors
Development - Build pages we've agreed are ready in the Add an ECT or Add a mentor journey
Research - Check in with the strategic design team and think about how we could survey or ask schools for the info they use to help them fulfil their registration responsibilities
Collect insights around transfers of ECTs and mentors 🏫
Analysis - Look at how transfers work in ECF1 and map it out
Research and design - Collect insights, problems, requirements and needs related to transfers to kick off on our away day
Whole team - Talk about how to decide if transfers will be two separate journeys or 1
Start to plan data model, roadmap and how we can work with LPDOB ☁
Product - Plan in lead provider related milestones on roadmap
Whole team - Draft the financial side of the data model, ready to check with PDOB
Research - Investigate what support might be needed for 2025 changes and where research or design might need to help
Analysis - Prepare analysis to bring to LPDOB on how we might want to expose LP or DP details to lead providers
Continue migration and up instances to speed it up 👾
Development - Start looking at migrating mentorships and training periods
Development - Create way to view data imported by school
Appropriate body sprint goals 🆎 🔍
Test what we've built so far for the new induction service
Kas - Plan how we want to test what we've built of the induction service so far Get together to test it!
Begin the first iteration of the Extensions user journey and record content 📏
Kas - Finalise content for extensions flow Analysis - Update service rules on Github about extensions
Nice to have Development - Add extensions journey
Continue migration data preparation 🐦
Development - Work out the tricky induction periods we need to migrate from the TRS Analysis Work out what errors we're expecting from migration import
Wrap up DfE Sign in process 🐦
Development - Match up the appropriate bodies with their organisation IDs so they can access the service
Start looking at round 2 of UR 🗣
Research - Agree high-level priorities for round 2 with appropriate bodies. Design Create term validation lofi screens to test on UR round 2 Development Build journey and error messages. UR - Clarify dates for UR round 2. Week of the 25th or the 2nd Dec.
Kas Create scenarios to test for each user flow
Align on comms to external users
Design - Prepare meeting with ECTMAN and Mosaic team
Complete analysis & design on Release & Outcomes journeys, ready to build unhappy paths next sprint 🤔
Analysis - Define a complete list of service rules for Release & Outcomes & populate backlog
Nice to have Design - Create lo-fi designs for Release & Outcomes errors
Create and agree admin console rules with TRA transformation 🖼
Design - Define admin console rules for CPD, and a set of rules which dictate when updates should / shouldn't be possible in CPD or TRS console (including exemption rules) Analysis - Service rules for user flows in admin console
Nice to have Design - Lofi design of admin console
Prepare governance for AB portal
Analysis - Review drafted DPIA work and update with any AB requirements Delivery - Scheduling PEN test contract. Main contact is Saheida
Nice to have Development - Prepare PEN test
Not a priority
Define service rules for viewing records flow
Analysis - Viewing records flow - when an ECT has concluded induction or been released and mid-induction changes, including correcting data (e.g. what mistakes should ABs correct themselves).
Define non-functional requirements
Analysis - Non functional requirements include expectations on users visiting, load testing - volumes of inductions at different times of the year.
Agree on appeals team process and archive data
Analysis - Clarify these topics with TRA