Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Don't be a zombie writing your stories - Brisbane BA Meetup - 14-06-2016

1,170 views

Published on

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 lot of exciting analysis techniques we can use to not only elicit requirements, but have fun and collaborate with others while doing so.

During this talk, you will learn about 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 design studio workshop, facilitate a customer journey map or hold a story kickoff. I'll also include general facilitation tips to take these session 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!

Published in: Technology
  • Be the first to comment

Don't be a zombie writing your stories - Brisbane BA Meetup - 14-06-2016

  1. 1. Don’t be a zombie writing your stories Learn some exciting analysis techniques Ryan McKergow ryanmckergow rmckergow
  2. 2. think sharp rmckergow Business Analysts just write stories in agile right?
  3. 3. think sharp 1. We’re more than just story writers… Analysis is essential
  4. 4. 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
  5. 5. 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
  6. 6. think sharp rmckergow T-shaped individuals Breadth Depth
  7. 7. think sharp rmckergow Poll: Can you relate? development team
  8. 8. think sharp rmckergow Reading stories ≠ shared understanding Communicationeffectiveness Richness of communication Reading a document / stories Refer to this article featuring @TotherAlistair: http://bit.ly/agilecomms
  9. 9. think sharp rmckergow Talking to people = shared understanding Communicationeffectiveness Richness of communication Face to face conversation Refer to this article featuring @TotherAlistair: http://bit.ly/agilecomms Face to face at a whiteboard
  10. 10. think sharp rmckergow Analysis and critical thinking is essential “Our job as analysts is not just to write requirements.” Ryan McKergow
  11. 11. think sharp 2. The exciting parts of analysis: Techniques to try @ work
  12. 12. think sharp rmckergow Three amigos Given… When… Then…?
  13. 13. think sharp rmckergow Three amigos “A technique collaborative mindset involving the key functions in software development.”
  14. 14. think sharp rmckergow Three amigos Steps 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)
  15. 15. think sharp rmckergow Three amigos Additional information on the three amigos: http://bit.ly/3-amigos-atdd
  16. 16. think sharp rmckergow Three amigos I have a question … Me too! How can I help?
  17. 17. think sharp rmckergow Story kickoff
  18. 18. think sharp rmckergow Story kickoff “A technique to get a shared understanding of a story when starting development.”
  19. 19. think sharp rmckergow Story kickoff Steps 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
  20. 20. think sharp rmckergow Story kickoff Additional information on story kickoffs: http://bit.ly/story-kickoffs
  21. 21. think sharp rmckergow Story kickoff
  22. 22. think sharp rmckergow Customer journey map
  23. 23. 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?”
  24. 24. think sharp rmckergow Customer journey map Steps 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
  25. 25. think sharp rmckergow Customer journey map Phase Activities Gains Pains Opportunities
  26. 26. think sharp rmckergow Design studio workshop
  27. 27. think sharp rmckergow Design studio workshop “A technique to design the user interface together & identify gaps in our analysis.”
  28. 28. think sharp rmckergow Design studio workshop Steps 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
  29. 29. think sharp rmckergow Design studio workshop Additional information on design studio workshops: http://bit.ly/design-studio-workshop (Details ¾ way down article)
  30. 30. think sharp rmckergow Design studio workshop
  31. 31. think sharp Tips to facilitate great workshops
  32. 32. think sharp elabor8 Preparation
  33. 33. think sharp elabor8 Facilitate with intent
  34. 34. think sharp elabor8 Encourage appropriate behaviours
  35. 35. think sharp elabor8 Engagement from everyone
  36. 36. Don’t be a zombie writing your stories Learn some exciting analysis techniques Ryan McKergow ryanmckergow rmckergow
  37. 37. elabor8.com.au Thank you Ryan McKergow ryanmckergow rmckergow
  38. 38. think sharp rmckergow Image References 1. Assets.nydailynews.com, (2016). [online] Available at: http://assets.nydailynews.com/polopoly_fs/1.98449.1314089135!/img/httpImage/image.jpg_gen/der ivatives/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].

×