Slides from a presentation given by Tim Wall and Alex Cottrell to the South West branch of IIBA UK on 3 November 2016.

1. Our Agile Journey so far…
3 November 2016
Tim Wall
Alex Cottrell

2. ©Zurich
Observations

3. ©Zurich
A new way of working to support customer centricity, the
digital movement and a desire to test and learn quicker
3
Analysis
Design
Build
Test
Implement
Producing
working
software
earlier

4. ©Zurich
The right people with the right mind set…
4
?
…are comfortable with a changing landscape and
multiple short distance horizons

5. ©Zurich
Broaden your field of vision
5
Architecture
Testing
ScrumMaster
ProductOwner
A utility player with a relentless focus on the quality,
delivery and relevance of the end product
SME
PM
Is there an opportunity to create a BA Hub
at the centre of everything?
Don’t be afraid to play out of position once
in a while!

6. ©Zurich
Don’t think like an <insurance> company
6
• The BA can help influence the UX
• Look at best in class
• Agile encourages creativity

7. ©Zurich
Customer
7
Speak Listen Analyse Do Evaluate
• Elaboration
• Feasibility
• Mapped to the business’ vision
Continual customer engagement

8. ©Zurich
Scrum Board
8
Product Backlog
Story Epic
Story 9 1
Story 8 1
Story 7 1
Story 5 1
Story 2 1
Story 4 1
Story 6 1
Story 1 2
Story 3 1
Rocks
(Large functional
components) and Pebbles
(Small functional
components)
Avoid stagnated products by prioritising some pebbles

9. ©Zurich
Back End
Front End
• Enables early customer engagement and verification
• Aids Funding decisions by providing the end product early
• Provides context (for the back end)
• Suited to a pilot implementation
Back End
9
Decoupling the front and back end delivery

10. ©Zurich
10
Virtual Working Challenges – Leverage the Tech!

11. ©Zurich
Scrum Practicals

12. ©Zurich
Understand and Visualise the overall scope
12
 Understand the project landscape

13. ©Zurich
Thoroughly understand your Stakeholders
Main professional
driver
Motivation
Goals from
project
Current
Frustrations
Personality Type
IT Literacy level
“Jamie Jones”
(Underwriter)
13
 Create customer personas
Personal
Information

14. ©Zurich
Understand your user journeys
Journey 3
Journey 4
Journey 5
Journey 1
Journey 6
Journey 7
Journey 2
Journey 8
 Identify the individual journeys through the system
14
 Divide them into functional ‘Epics’ of large but distinct pieces of
functionality

15. ©Zurich
Create your stories & product backlog
Product Backlog
Sprint Backlog
Attach a customer document
Epic: Create a new customer record
ID123 Estimate: 5d
User Story
As a
I want to
In order to
Acceptance Criteria
conditions that the product must satisfy to be accepted by
the requester
• (Reference to wireframe)
• (Reference to data dictionary)
Story

16. ©Zurich
Less big and clunky, more small and chunky
Story
Story
Story
Sprint 1
Sprint 2
Sprint 3
Role Based
Permissions
Wireframes
Data
Dictionary
Process
Models
Update
and
reference
Update
and
reference
Artefacts Artefacts
 Write succinct User Stories to define needs of the users from the system
 Create and maintain central artefacts and reference in stories

17. ©Zurich
Don’t get stuck in the long grass
Try to avoid becoming a factory for producing detailed stories
17

18. ©Zurich
Manage traceability at all levels
Focus on elaborating lightweight, quality detailed stories…
18
…but don’t forget to maintain the slower moving scope and understand
the direction the project is traveling in

19. ©Zurich
Any Questions?