Have you ever been told that all Business Analysts do on Agile projects is write stories? I have… and that’s the boring part of our job! There are a lot of cutting-edge analysis techniques we can use to not only elicit requirements, but have fun and collaborate with others while doing so. During this presentation, you will learn why problem solving with our software development teams is essential. I will introduce techniques to get our teams talking, discussing the problem, and agreeing on a solution. Learn how to run a story kickoff, facilitate a customer journey map or experiment with design studio workshop. I’ll also include general facilitation tips to take these sessions up another notch. Don’t just be a zombie writing your next story. Let’s think about the problem and how we’ll solve it together!

1. Don’t be a zombie writing your stories
Learn some cutting edge analysis techniques
Ryan McKergow
ryanmckergow
rmckergow

2. Be like Buzz! He’s our mascot for today

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

4. 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

5. Collaborative analysis reduces costs 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

6. Poll: Can you relate to this?
development team

7. Discussion time: Have you been in this situation?
What did you do?
development team

8. Reading stories ≠ shared understanding
Communicationeffectiveness
Richness of communication
Reading a
document /
stories
Refer to this article featuring @TotherAlistair: http://bit.ly/agilecomms

9. Talking to people = shared understanding
Communicationeffectiveness
Richness of communication
Refer to this article featuring @TotherAlistair: http://bit.ly/agilecomms
Face to face
conversation
Face to face at
a whiteboard

10. What does this mean for us as
Business Analysts?

11. We need to be T-Shaped individuals
Breadth
Depth

12. Analysis is essential
“Our job as business analysts
is not just writing requirements.”

13. Analysis is essential
“We help our teams gain
a shared understanding of
the problem,
the business objectives, &
how we’re going to solve it.”

14. Cutting edge analysis
techniques to try @ work

15. The Three Amigos
Given… When…
Then…?

16. The Three Amigos – What is it?
“A collaborative technique
mindset for problem solving &
gaining a shared
understanding.”

17. The Three Amigos – When should I use it?
All through out the software
development process

18. The Three Amigos – How do I do it?
Steps:
• Where ever you need to clarify
a user story  talk to each
other at the same time
(Time: 5-15 minutes)

19. The Three Amigos – Does it work?
I have a
question Me too!
How can
I help?

20. Discussion time: The Three Amigos
“Have you had a similar
situation where using this
mindset would have saved
you time?”

21. The Three Amigos – Want more info?
Check out:
http://bit.ly/3-amigos-atdd

22. Story Kickoff

23. Story Kickoff – What is it?
“A technique to get a shared
understanding of a user story
when starting development.”

24. Story Kickoff – When should I use it?
When starting development
on a user story.

25. Story Kickoff – How do I do it?
Steps:
• Gather the team around a
whiteboard
• Visually explain the user story
• Encourage questions
• Start development
(Time: 5-15 minutes)

26. Story Kickoff – Does it work?

27. Story Kickoff – Want more info?
Check out:
http://bit.ly/story-kickoffs

28. Customer Journey Mapping

29. Customer Journey Mapping – What is it?
“A technique to understand
what our customers go
through. What are their pains
& what are the opportunities
to improve?”

30. Customer Journey Mapping –
When should I use it?
At the start of the project or
an initative.

31. Customer Journey Mapping - How do I do it?
Steps:
• Organise the team for a workshop
• Invite a customer(s)
• List out the:
• Phases the customer goes through
• Activities for each phase
• What they gain / is painful about each phase
• Brainstorm opportunities to improve on existing
process
Time: 60-120 minutes

32. Customer Journey Mapping - How do I do it?
Phase
Activities
Gains
Pains
Opportunities

33. Customer Journey Mapping – Does it work?

34. Discussion time: Customer Journey Mapping
“Discuss approaches you
could take in your
organisation to spend time
with your customers.”

35. Design Studio Workshop

36. Design Studio Workshop – What is it?
“A technique to design
the user interface together
& identify gaps
in our analysis.”

37. Design Studio Workshop –
When should I use it?
When analysing a
new feature.

38. Design Studio Workshop – How do I do it?
Steps:
• Organise the team for a workshop
• Explain the 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

39. Design Studio Workshop – Does it work?

40. Design Studio Workshop – Does it work?

41. Design Studio Workshop – Want more info?
Check out:
http://bit.ly/design-studio-
workshop
(Details ¾ way down article)

42. Tips to facilitate
great collaborative workshops

43. Preparation

44. Facilitate with intent

45. Encourage appropriate behaviours

46. Engagement from everyone

47. How you can facilitate
great collaborative workshops
1 Preparation
Encourage appropriate
behaviours
Facilitate with
intent
Engagement from
everyone
3
2
4

48. Thank you
Ryan McKergow
ryanmckergow
rmckergow