1. The story so far
Rachel Murphy
28 January 2015

2. What are we trying to achieve?
Improve the way we work with the business
Build a customer centric ethos into our approach
Understand our technical estate and capabilities

3. The workstreams
5. Joint development
approach
7. Looking to
the future…
1. Establishing
the basics
3. Service
management
6. Communications
& engagement
4. Strategy &
architecture
2. Quick
wins

4. 1. Establishing the basics
Getting the SLT to work consistently together
KPI and metrics across all areas
Demand log for business requests

5. 2. Quick wins
Techbar
iPads
WiFi

6. Tech bar
Bring the service desk concept on the road
Find out how we can better help and support our colleagues
Share our plans and news

7. Tech bar in numbers
8sessions
86issues/ideas
50people

8. iPads
Listened to feedback
New secure container
Scoping out business/customer requirements

9. Wifi – one of life’s essentials!

10. 3. Service management
We’ve got a proper service desk
We’ve got a consistent process that everyone follows when dealing
with calls
You can’t manage what you can’t measure

11. 4. Strategy and Architecture
Review and map applications and infrastructure
Top 40 – hold, invest, retire
Define governance controls for the future
Exploring sourcing options for the future

12. 5. Joint development approach
All three development teams working to the same methodology
Single GitHub account
Agile coaching to boost collaboration and output

13. Framework for development
Consistent with GDS approach
Framework, not a prescription
Coaching, now and next year to help align us

14. Development framework
Explore
Understand your challenge and the user
need. Initial view of technical options.
Agree what your MVP will be.
Alpha
Build a prototype for your MVP. Test it with
users to gauge its effectiveness. Iterate.
Begin work on some technical tasks.
Beta
Build your MVP to production scale,
building a picture of the support
arrangement needed. Test with more users.
Live
Declare your service live when it is
performant and stable. Iterate and
improve.
Activities/outputs
Build consensus, form your
team, agree objectives.
Activities/outputs
Prototype(s), user research.
Activities/outputs
More stable MVP, defined
support arrangements.
Activities/outputs
Support plan, stable production
environment, improvement plan.

15. 6. Communications and engagement
Feedback from customers
Change champions
TechBlog

16. Feedback from our customers
Operation War
Diary
How could technology improve?
‘More business focused and less
Technology and inwards looking.
Better project planning and
communication, particularly for
larger projects and system
upgrades.’

17. But the little things make a difference too…
Operation War
Diary
How could technology improve?
‘It would be helpful if computers
turned on quicker.’
Need photo
14.68 x 9.83

18. Change champions
32 ambassadors for technology change in their teams
Quarterly workshops, run as facilitated session
Next one – end Feb. Anything you’d like us to get across?

19. 7. Looking to the future
Apprentices and talent
Skills assessment
People moves for the end of March
Transformation with a Target operating model

20. Apprentices and talent
Look at alternatives to standard recruitment
Specialised apprentice companies, graduates, work placements
What can we learn from start-ups?

21. Skills assessment
People are our strength and we want to make the most of them
Will help us decide on future shape and structures
People have talent, knowledge and skills outside of their job title –
this will help to unlock that

22. People moves - end of March
Jeff’s statement in December
Working with SLT to progress
Period of shadowing first two weeks of February 2015
Intention to communciate staff moves end of February 2015

23. Transformation‘Target’ Operating Model

24. Any questions?