Під час доповіді поговоримо про участь бізнес-аналітиків і розкриємо основні складові discovery workshop: - Організація. Коли проведення воркшопу, окрім стартової фази, є максимально ефективним? - Підготовка. Як почати з нічого і якісно підготуватись до воркшопу у стислі терміни? - Проведення: Workshop Do’s and Don’ts. Приклади технік і вправ, а також приблизний план самого воркшопу. - Оформлення кінцевих результатів або презентації, що запам’ятовуються

1. How to run a discovery
workshop
BA Stories
Apr 15, 2020.

2. Ground Rules.
1. Please mute yourself.
2. Post your question to Zoom chat.
3. We’ll review questions per each speech section.
4. Remaining questions will be left for final Q&A.
5. Let’s enjoy the webinar)

3. Content.
1. Why Workshop?
2. When it is needed?
3. How to prepare for the Workshop?
4. How to run the Workshop?
5. Technique examples
6. Remote Workshop tips
7. Q&A

4. Introduction.
Nataliia Pelykh
Lead Business Analyst
@ Ciklum
Experience
• Business Analyst with 5+ years experience
• Primary domains: finance & healthcare

5. Why Workshop?

7. Risks to be covered.
• Value
• Usability
• Feasibility
• Business viability

8. Workshop essence.

9. Typical objectives.
• Define the goals that the product needs to
achieve.
• Define major constraints and limitations.
• Frame the challenge and prioritize needs.
• Gather insights and align on visions.
• Validate the idea on the early stage.

10. When it is needed?

11. New product start.
• Rough idea that has to be elaborated and
validated.
• Next steps to be determined.
• Many grey areas, assumptions, little facts.
• Lots of information to analyse and
structure.

12. Existing product improvement.
• Many organizational gaps / stakeholder
concerns.
• Current solution calling for proper
investigation.
• Improvement opportunities and design
options need to be identified.
• Information needs to be elicited from a
group of people.

13. Need for innovation.
• Business case to be investigated.
• Problems and their causes to be
identified.
• Change strategies need to be
developed.
• Innovation opportunities to be
suggested.

14. How to prepare ?

15. Typical preparation.
• Limited time.
• Partial information.
• Vague purpose.
• Unstable participants list.

17. Where to look for the info?
• Crunchbase.com – money raised, acquisitions
• AppAnnie – market size, rankings for apps
• Reddit, Quora, Yahoo answers – general news
• Mention.com – social media accounts activity
• Google Trends, Google Alerts – competitors monitoring

18. How to run?

20. Workshop don’ts.
• Don’t gather all available people, stay picky
• Don’t show up unprepared
• Don’t talk too much
• Don’t overuse whiteboard
• Don’t set exaggerated expectations
• Don’t over-rely on agenda

21. Agenda option.
Day 1
Introductions 10 min
Product Vision 45 min
Press Release 45 min
Elevator Pitch 30 min
Success Sliders 20 min
Pragmatic
Personas
45 min
Day 2
User Story
Mapping
90 min
Prioritization 30 min
User Story
Writing
90 min
Team Charter 20 min

22. Technique examples.

23. Product vision.

24. Elevator pitch.
For target customers
Who are
dissatisfied with
the main pain point or
need
Our Product is a new product category
That Provides product’s key problem-
solving capability
Unlike the product alternative
Our Product product’s key features

25. Success sliders.

26. Lightning decision jam (LDJ).
1. Start with Problems
2. Present Problems
3. Select Problems to Solve
4. Reframe Problems as Standardized
Challenges
5. Produce Solutions with ‘HMW’
6. Vote on Solutions
7. Prioritize Solutions
8. Decide what to execute

28. Remote tips.
• Show presentation in parts
• Ask questions more frequently
• Add you thoughts to the mindmap
• Signal if you want to comment
• Don’t delete anything
• You could try Miro as a tool

29. nataliia-pelykh
npe@ciklum.com
Contacts

30. Any questions?