Inc. Let's say that our project is to design an online video editing suite. The product manager determined that there will be two kinds of users, professional editors and home users. She also said that the professional user will use the advanced features, while the home users will not. Before designing anything, we need write detailed usage scenarios for each type of user, to understand how they will use the system.
Scenarios help with many areas of development.
They are starting points for design, QA, documentation and usability testing. See a sample scenario . Clarifying assumptions . By agreeing on usage details, development team members formalize their assumptions so there are fewer surprises later. Fully exploring the design .