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.

Lean Business Analysis and UX Runway - Natalie Warnert

1,043 views

Published on

How to integrate BAs and UX in a Agile/Lean environment to create an MVP to learn while reducing potential waste. Presented at Lviv IT Arena, 2015 in Lviv, Ukraine by Natalie Warnert, October 3, 2015

www.nataliewarnert.com

Published in: Data & Analytics
  • Be the first to comment

Lean Business Analysis and UX Runway - Natalie Warnert

  1. 1. Lean Business Analysis and UX Runway Managing value by reducing waste Natalie Warnert IT Arena – Lviv, Ukraine October 3, 2015
  2. 2. Agenda • Natalie’s background • Define roles of BA and UX in Agile • Understand Agile role integration • Show example of how this can be done via Runway process (Best Buy example) • Benefits and risks You will leave knowing how to help BAs and UX collaborate to learn quickly
  3. 3. Natalie Warnert • Agile Coach, Project Delivery Mgr • MA, CSP, CSM, PSM Web: www.nataliewarnert.com Twitter: @nataliewarnert Email: info@nataliewarnert.com
  4. 4. Minneapolis, Minnesota, USA
  5. 5. BestBuy.com
  6. 6. What is a BA? Business Analysts  Act as a liaison between Business and IT  Work on requirements for projects  Solve problems  Build specifications for how solutions will work  Define As-Is and To-Be states of the business User Experience Professionals • User Researcher • Information Architect • Visual Designer • Accessibility Specialist • [insert verb here] how a person interacts with a system – Flow – Perception – Ease of use – Understanding What is UX? *Content from Leslie J. Morse
  7. 7. Why is it so hard for UX, analysts and Agile to play nicely? Image source: http://static.comicvine.com/
  8. 8. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more Source: agilemanifesto.org
  9. 9. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more But comprehensive documentation is my JOB!
  10. 10. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more Both of these are important
  11. 11. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more We can’t just keep changing things ALL THE TIME! Change request? That big design up front is an important plan!
  12. 12. But what about Lean? Eliminate waste Small batch sizes Only deliver value Shorten the feedback loop Build > Measure > Learn
  13. 13. Wait… Eliminate waste Small batch sizes Only deliver value Shorten the feedback loop Is what I produce waste?
  14. 14. But… Eliminate waste Small batch sizes Only deliver value Shorten the feedback loop It does not make sense in small pieces!
  15. 15. I do not understand… Eliminate waste Small batch sizes Only deliver value Shorten the feedback loop What is not value? All of this is valuable!
  16. 16. I do not understand… Eliminate waste Small batch sizes Only deliver value Shorten the feedback loop Does that mean I have to work faster? Quality takes time!
  17. 17. It’s a balance! Key integration and engagement at all levels of planning, development, implementation, and feedback to understand and respond to customer desires Image source: worldofDTCmarketing.com
  18. 18. But how? • Shorten development lifecycles • Business hypothesis driven experimentation • Validated learning Source: The Lean Startup – Eric Ries
  19. 19. BA’s can analyze and create But how? • Shorten development lifecycles • Business hypothesis driven experimentation • Validated learning
  20. 20. But how? • Shorten development lifecycles • Business hypothesis driven experimentation • Validated learning Research Prototyping A/B Tests Etc.
  21. 21. But how? • Shorten development lifecycles • Business hypothesis driven experimentation • Validated learning At all levels: portfolio, product, team
  22. 22. Analyst and UX Runway Continuously assessing what needs to be done first second just in time (JIT) or not at all (waste) to find the Minimum Viable Product (MVP) MVP = ‘just enough’ to learn
  23. 23. Analyst and UX Runway Big Design up Front to Just in Time to adjust to feedback and improve cycle time Broad requirements to pieces of value and function to learn Focus and detail Time to development and delivery
  24. 24. Analyst and UX Runway +5 +4 +3 +2 +1 Dev Starts
  25. 25. Analyst and UX Runway +5 +4 +3 +2 +1 Dev Starts User Research (A/B tests, BDUF, Studies, hypothesis validation) Focus to integrate learning and investigate new hypotheses
  26. 26. Analyst and UX Runway Information Architecture and Visual Design (wireframes & images) Focus for Grooming +5 +4 +3 +2 +1 Dev Starts User Research (A/B tests, BDUF, Studies, hypothesis validation) Focus to integrate learning and investigate new hypotheses
  27. 27. Analyst and UX Runway Information Architecture and Visual Design (wireframes & images) Focus for Grooming +5 +4 +3 +2 +1 Dev Starts User Research (A/B tests, BDUF, Studies, hypothesis validation) Focus to integrate learning and investigate new hypotheses Focus for story review 10% overlapIntegration capacity Any last details
  28. 28. Cart, Fulfillment, Checkout, Payment
  29. 29. How does it actually work? • Story mapping • Value mapping • Backlog/requirements grooming • Internal reviews and collaboration with entire team (at multiple engagement levels) • Demos of designs, results of research, describing business hypotheses and value learning
  30. 30. Story Mapping Attach Product recommendations Warranty plans Recommend for you Complete your purchase Apple Care Geek Squad Protection Required Accessories
  31. 31. Value Mapping Attach Product recommendations Warranty plans Recommend for you Complete your purchase Apple Care Geek Squad Protection Required Accessories What will bring more value? To business? To customer? User Research, existing metrics, new metrics, developmental complexity
  32. 32. Backlog Grooming/Story Refinement Connect to data feed Data mine and associate parent products with child products Complete your purchase Wireframes Visual Design Output data to front end Organize and display items Write and display text
  33. 33. Sprint Planning Connect to data feed Data mine and associate parent products with child products Customers who bought also bought Wireframes Visual Design Output data to front end Organize and display items Write and display text 1 2 2 3 1
  34. 34. Execution and Review • Sprint 1 = Spreadsheet of associations, data flows/sources, system and user interactions • Sprint 2 = Products associating in a list from database, outputting in front end, visual design (what it will look like) • Sprint 3 = Fully functional prototype with a few test products – enough to learn
  35. 35. Lean testable feature to LEARN
  36. 36. Working TOGETHER Instead of throwing things over the wall: • What the system shall do • How the customer shall interact with the system • How the system shall interact with itself and other systems Collaborate to make the most effective solution in an efficient manner.
  37. 37. Benefits of Runway • Increased quality • Fewer fire drills or emergencies • Less re-work • Faster/effective delivery • Flexibility in design • Consistent product • Predictability
  38. 38. Risks of Runway • Analysis paralysis • Bottleneck creation • Can be manipulated • “Just enough” is not the same for all teams, features, products
  39. 39. What to remember: Planning is not bad Plans should allow for flexibility Continuous learning and validation Value is key – effectiveness over efficiency Image Source: http://blog.thehigheredcio.com/2011/08/31/efficiency-vs-effectiveness/
  40. 40. Thank you & questions Contact: Email: info@nataliewarnert.com Web: www.nataliewarnert.com Twitter: @nataliewarnert

×