don't be a zombie writing your stories - brisbane ba meetup - 14-06-2016

Don’t be a zombie writing your storiesLearn some exciting analysis techniquesRyan McKergow

ryanmckergow

rmckergow

think sharp rmckergow

Business Analysts just write stories in agile right?

think sharp

1. We’re more than just story writers…Analysis is essential

think sharp rmckergow

Poor analysis creates costly defects

Refer to this article featuring @scottwambler: http://bit.ly/costofchange

Cost

Length of feedback cycle

Analysis defects found via traditional acceptance testing

think sharp rmckergow

Collaborative analysis reduces cost of defects

Refer to this article featuring @scottwambler: http://bit.ly/costofchange

Cost

Length of feedback cycle

Analysis defects found via active stakeholder engagement / participation

Analysis defects found via collaborative workshops

think sharp rmckergow

T-shaped individualsBreadth

Depth

think sharp rmckergow

Poll: Can you relate?development team

think sharp rmckergow

Reading stories ≠ shared understanding

Com

mun

icat

ion

effec

tive

ness

Richness of communication

Reading a document /

stories

Refer to this article featuring @TotherAlistair: http://bit.ly/agilecomms

think sharp rmckergow

Talking to people = shared understanding

Com

mun

icat

ion

effec

tive

ness

Richness of communication

Face to face conversation

Refer to this article featuring @TotherAlistair: http://bit.ly/agilecomms

Face to face at a whiteboard

think sharp rmckergow

Analysis and critical thinking is essential

“Our job as analysts is not just to write requirements.”

Ryan McKergow

think sharp

2. The exciting parts of analysis:Techniques to try @ work

think sharp rmckergow

Three amigosGiven… When…

Then…?

think sharp rmckergow

Three amigos

“A technique collaborative mindset involving the key

functions in software development.”

think sharp rmckergow

Three amigosSteps to be the three amigos:

• Where ever you need to clarify a story talk to eachother at the same time

• Time: 5-15 minutes

• Other opportunities:• Sprint planning• Story kickoff• Demoing a story to the “business” (aka

Product owner)

think sharp rmckergow

Three amigos

Additional information on the three amigos:

http://bit.ly/3-amigos-atdd

think sharp rmckergow

Three amigosI have a question

…Me too!

How can I help?

think sharp rmckergow

Story kickoff

think sharp rmckergow

Story kickoff

“A technique to get a shared understanding of a story when

starting development.”

think sharp rmckergow

Story kickoffSteps to run a story kickoff:

• Hold it when ready to start dev on a story• Gather the team & creator of the story• Ask the creator to visually explain the story

& provide context• Asks lots of questions to clarify what they

want• Start dev• Time: 5-15 minutes

think sharp rmckergow

Story kickoff

Additional information onstory kickoffs:

http://bit.ly/story-kickoffs

think sharp rmckergow

Story kickoff

think sharp rmckergow

Customer journey map

think sharp rmckergow

Customer journey map

“A technique to understand what our customers go

through. What are their pains & what are the opportunities to

improve?”

think sharp rmckergow

Customer journey mapSteps to create a Customer journey map:

• Organise the team for a workshop (particularly someone involved in the existing process or a real customer!)

• List out the:• Phases the customer goes through• What activities for each phase• What they gain / is painful about each phase

• Brainstorm opportunities to improve on existing process

• Time: 60-120 minutes

think sharp rmckergow

Customer journey mapPhaseActivitiesGainsPainsOpportunities

think sharp rmckergow

Design studio workshop

think sharp rmckergow

Design studio workshop

“A technique to design the user interface together

& identify gaps in our analysis.”

think sharp rmckergow

Design studio workshopSteps to run a design studio workshop:

• Organise the team for a workshop• Product owner provides context on new feature• Everyone draws what they think the interface will

look like• Present to each other, share & critique ideas• Round 2 of drawing the interface based on

feedback (optional)• Converge on a single design• Time: 30-90 minutes

think sharp rmckergow

Design studio workshop

Additional information ondesign studio workshops:

http://bit.ly/design-studio-workshop(Details ¾ way down article)

think sharp rmckergow

Design studio workshop

think sharp

Tips to facilitate great workshops

think sharp elabor8

Preparation

think sharp elabor8

Facilitate with intent

think sharp elabor8

Encourage appropriate behaviours

think sharp elabor8

Engagement from everyone

Don’t be a zombie writing your storiesLearn some exciting analysis techniquesRyan McKergow

ryanmckergow

rmckergow

elabor8.com.au

Thank you

Ryan McKergow

ryanmckergow

rmckergow

think sharp rmckergow

Image References1. Assets.nydailynews.com, (2016). [online] Available at:

http://assets.nydailynews.com/polopoly_fs/1.98449.1314089135!/img/httpImage/image.jpg_gen/derivatives/gallery_1200/gal-movie-a-team-

jpg.jpg [Accessed 15 Feb. 2016].

2. Ambysoft.com. (2016). [online] Available at: http://www.ambysoft.com/artwork/

comparingTechniques.jpg [Accessed 28 Apr. 2016].

3. Schiffer, B. (2015). Bernd Schiffer on Twitter. [online] Twitter. Available at:

https://twitter.com/berndschiffer/status/611773018772103168 [Accessed 15 Nov. 2015].

4. Agilemodeling.com, (2015). Communication on Agile Software Teams. [online] Available at:

http://www.agilemodeling.com/essays/communication.htm [Accessed 15 Nov. 2015].

5. Methodsandtools.com. (2016). [online] Available at:

http://www.methodsandtools.com/archive/speccollab1.gif [Accessed 28 Apr. 2016].