Using User Stories to Discover and Define Requirements for Technical Documentation Tools
- Workshop
- Management & Leadership
- 12. November
- 04:30 PM (CET) - 06:15 PM (CET)
- C4.2
Contents
When it comes to choosing a new tool, whether it’s a Component Content Management System, Content Delivery Platform, review tool for subject matter experts, or even a tool for internal use, many companies create long lists of features which they then send to various vendors or their own developers. The result: almost identical responses from the vendors and no guarantee that the tool you decided on is actually the right one for you.
At this workshop, we’ll use a combination of theory and practical exercises to give you hands-on experience defining your requirements in a way that lets you choose the tool that best supports your needs.
You’ll learn:
- What user stories are and how to write them properly to discover your actual requirements
- How user stories can help you unveil potential conflicts in the views of different stakeholders (e.g., end users, management, and IT)
- How to translate user stories to requirements
You’ll take home ready-to-use templates and examples for writing user stories for different stakeholders.
Takeaways
- How to write user stories that truly discover your requirements
- How to use user stories to evaluate different tools
- How to organize the process of requirements gathering and writing user stories
Prior knowledge
no prior knowledge required
