View
286
Download
0
Category
Preview:
Citation preview
Our Agile Journey so far…
3 November 2016
Tim WallAlex Cottrell
© Z
urich
Observations
© Z
urich
3
A new way of working to support customer centricity, the digital movement and a desire to test and learn quicker
AnalysisDesign
BuildTest
Implement
Producing
working software earlier
© Z
urich
4
The right people with the right mind set…
?
…are comfortable with a changing landscape and multiple short distance horizons
© Z
urich
5
Broaden your field of vision
Architecture
Testing
Scrum M
aster
Product Owner
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!
© Z
urich
6
Don’t think like an <insurance> company
• The BA can help influence the UX• Look at best in class • Agile encourages creativity
© Z
urich
7
Customer
Speak Listen Analyse Do Evaluate
• Elaboration• Feasibility• Mapped to the business’
vision
Continual customer engagement
© Z
urich
8
Scrum BoardProduct BacklogStory Epic
Story 9 1Story 8 1Story 7 1Story 5 1Story 2 1Story 4 1Story 6 1Story 1 2Story 3 1
Rocks(Large functional
components) and Pebbles(Small functional
components)
Avoid stagnated products by prioritising some pebbles
© Z
urich
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
© Z
urich
10
Virtual Working Challenges – Leverage the Tech!
© Z
urich
Scrum Practicals
© Z
urich
Understand and Visualise the overall scope
12
Understand the project landscape
© Z
urich
Thoroughly understand your Stakeholders
Main professionaldriver
Motivation
Goals fromproject
Current Frustrations
Personality Type
IT Literacy level
“Jamie Jones”(Underwriter)
13
Create customer personas
Personal Information
© Z
urich
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
© Z
urich
Create your stories & product backlog
Product Backlog
Sprint Backlog
Attach a customer document
Epic: Create a new customer record
ID123 Estimate: 5dUser Story
As aI want toIn order toAcceptance Criteria
conditions that the product must satisfy to be accepted by the requester
• (Reference to wireframe)• (Reference to data dictionary)
Story
© Z
urich
Less big and clunky, more small and chunky
Story
Story
Story
Sprint 1
Sprint 2
Sprint 3
Role Based PermissionsWireframes
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
16
Create and maintain central artefacts and reference in stories
© Z
urich
Don’t get stuck in the long grass
Try to avoid becoming a factory for producing detailed stories
17
© Z
urich
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
© Z
urich
Any Questions?
Recommended