Reasons for using story boards
- To act as an inspiration for other requirements.
- To increase understanding of the requirements between all stakeholders and the consequences.
- The system has not existed before.
- The users have no experience of the system.
- The users have been doing their work for some time and are stuck in the way they are doing it.
- The users are having trouble articulating their requirements.
- The business analysts are having trouble understanding what is required.
- The feasibility of a requirement is in doubt.
- There is a disagreement on what is required.
- The system is a graphical user interface.
Putting together a story board
This method complements use cases and provides a sketch of what the user might see when using the product for the use case. A use case is a brief description of what goal the system must carry out. A storyboard focuses on what the product will do rather than the mechanics of the implementation medium.
Pencil and paper, whiteboards, flip charts, post it notes or card board boxes are all examples of what could be used when putting storyboards together.
It is not meant to look like the finished product and encourages iteration.
To put together a storyboard sketch what the user might see when using the product whilst asking the users what they would like the system to tell them and how they would like the information to be given to them.
Example
The diagram above is for a Login use case.
It shows the start of how a storyboard could look and how consequential iterations would build up more detail into what needs to be on each page of the system and the interactions required. So for example the user name and password could generate further discussion as to what if the user doesn’t know their password etc. so that other pages are added and more questions answered.
In addition to uncovering requirements it can also help resolve conflicts.
Using the example there could be a conflict where the IT security stakeholders wish more complexity to ensure unauthorised users cannot log on to the system and the business stakeholders do not want to put off users. The storyboard then provides a tool to increase understanding and of the usability so concerns can be discussed and overcome.
Storyboards are therefore a powerful tool for gathering requirements and resolving conflict.
Thoughts? Questions? Please share in the comments.
If you have found this article useful then you might like my book – The Business Analysis Handbook – Techniques and Questions for better Business Outcomes. The book is available from www.koganpage.com and all major print and e-book retailers.
