Chapter 6 Scenarios
Formality Guide
Rabbit projects:- Use scenarios as a trawling technique.
- The requirements analysts and the appropriate stakeholder build a scenario for the business use cases.
- usually faster to discover the required functionality by working with scenarios.
- usually overlook non-functional requirements
Horse project:
- consider scenarios as an alternative to writing atomic functional requirement
- can serve to inform the developers of the functional needs of the product
- this approach does not work all the time.
Elephant project:
- use of scenarios as a discovery tool
- The meetings with the stakeholders are occasions for reviewing the desired way of working
- it is used as the basis for writing the functional requirements
- keep their scenarios as part of the documentation
Scenarios
1. The moviegoer asks for movies based on her previously recorded
preferences.
2. The moviegoer filters the movies based on the time of screening
and
the location of the cinema.
3. If requested, reviews of the shortlisted movies are provided.
4. The moviegoer selects a movie.
5. The moviegoer elects to buy the ticket online.
6. Ticket details and a quick response code are sent to the moviegoer’s mobile phone.
7. The moviegoer elects to send e-mails to selected friends with
details of the movie and an invitation to join her at the movies.
8. The moviegoer checks parking availability, and public transport
options, for the cinema.
9. The moviegoer sets an alarm to remind her when it is time to leave
for the movies.
The Essence of the Business
The same technique of scrubbing away the technology and getting to the
essence is employed for later steps in the scenario. Keep working through it
until you and your interested stakeholders agree that it is an accurate, but
not yet detailed, portrayal of the work. When it is finished, it would look
something like this:
Diagramming the Scenario
Exceptions
Exceptions are unwanted but inevitable deviations from the normal case.
They are unwanted in the sense that the owner of the work would rather
that they did not happen. Nevertheless, we know that they will happen from
time to time, so we have to cater for them.
At IG, Scenarios play an important role in the business problem, and it can be used for the formality guide. For Rabbit Project, use scenarios and non-functional story cards to discover requirements. While for Horse Project consider scenarios as an alternative to writing atomic requirements for less complex projects and Elephant project, use scenarios as a discovery tool and then a basis for writing the functional requirements. Also, we also have some Scenarios component like Diagramming the Scenario(an alternative to text for explaining the functionality of a BUC), Alternatives(include expected alternative actions), Exceptions( documenting unwanted but inevitable deviations) and What If..? ( documenting possibilities). Importantly, the interested stakeholders must agree on the documentation - including what the work has to do and how much of the work will be done by the product.
ReplyDeleteWith the current solutions that is planned for implementation at IG, determining scenarios involve considerations like user needs and how to fasten up the overall processes of approving loans as well managing decisions based on the volatile market situation. A typical business event at IG can be when a customer needs a loan or when a customer wants to invest his/her money and the corresponding BUCs will be provide loan and manage capital respectively. The way we wish to handle these scenarios is by the implementation of the new CRM tool, which will help these scenarios to be implemented faster and smarter which will ultimately help in increase customer turn around. and the CRM tools falls under the Rabbit category, scenarios are used to discover functional and non-functional requirements.
ReplyDeleteThat is a great information about Scenarios. I also would like to add about the information related to the misuse cases and negative scenarios. There are some possibilities like someone abusing at work, misleading in customer information and planting a virus or other malware that can happen at IG Wealth Management. So, while gathering the requirements, Business Analyst should also focus on What if and generate requirement for these type of scenarios. So, The more you know about eventualities before you build the product, the more robust and long-lasting it will be.
ReplyDelete