Software Development Cross Solution - Index of - Free

Find out what people REALLY do
Everything (that’s ethical and legal) is pretty much fair game when
you’re trying to get into your customer’s head to understand their
requirements. Two particularly useful techniques that help you
understand the customer are role playing and observation.
Role playing
If your customer is finding it hard to visualize how they need their software to work, act
it out. You pretend to be the software and your customer attempts to instruct you in
what they would like you to do. Then write down each thing the software needs to do
on one of your requirement cards.
Observation
And now I’d select the dates
for the booking...
Your customer
pretends that you are
the software and tries
to do their job.
OK, so now I display a calendar
widget (and add display dates to
my “Create a booking” card...)
Sometimes the best way to understand how people will work with your software is to watch them,
and figure out where your software will fit in. Nothing beats firsthand evidence, and observation
can really help to bring out constraints and details that might have been missed in bluesky
brainstorming or even in role playing. Also, try to observe the same interactions more than once
with multiple observers so you don’t just gain one person’s impression of an event.
Yes, we offer a selection of
different types of seats...
Hmm, that requirement
hasn’t come up before...
Try to keep your observation
as unobtrusive as possible.
Download at WoweBook.Com
gathering requirements
You pretend to
“be” your software.
If you can, try three
people observing on
around three occasions
you are here 4 37