I think the key here is to focus on techniques that allow you to imagine and test out future scenarios, rather than just documenting existing processes. Based on that, I'd say prototyping is probably the most effective approach for defining future requirements.
Shadowing seems like it would be the least effective technique for defining future requirements. It's more focused on observing current user behaviors and workflows, rather than exploring new possibilities for the future system.
Hmm, I'm a bit unsure about this one. I know workshops and prototyping are both common requirements elicitation techniques, but I can't quite remember which one is less effective for future requirements. I'll have to think this through carefully.
I'm pretty confident that prototyping is the most effective technique for defining future requirements. Workshops and scenario analysis are good for eliciting current needs, but prototyping lets you explore and test potential future features.
I'm gonna have to agree with Marshall on this one. Shadowing is just observing the present, not defining the future. That's like trying to drive while only looking in the rearview mirror.
I'm gonna have to go with D. Shadowing is just watching someone else do their job - how's that supposed to help us figure out what we need in the future?
Loren
7 months agoCarman
7 months agoAliza
7 months agoLorrie
7 months agoJanine
8 months agoDenae
8 months agoRozella
8 months agoDemetra
8 months agoDianne
8 months agoRicki
9 months agoErick
9 months agoBuck
9 months agoRamonita
9 months agoChi
11 months agoCiara
11 months agoLai
10 months agoMari
11 months agoMarshall
11 months agoMing
11 months agoEulah
11 months agoDaniel
12 months agoCurtis
1 year agoEulah
1 year agoSuzi
1 year agoBeckie
11 months agoLouvenia
12 months agoWenona
12 months agoCurtis
1 year ago