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
8 months agoCarman
9 months agoAliza
9 months agoLorrie
9 months agoJanine
9 months agoDenae
10 months agoRozella
10 months agoDemetra
10 months agoDianne
10 months agoRicki
10 months agoErick
11 months agoBuck
11 months agoRamonita
11 months agoChi
1 year agoCiara
1 year agoLai
12 months agoMari
1 year agoMarshall
1 year agoMing
1 year agoEulah
1 year agoDaniel
1 year agoCurtis
1 year agoEulah
1 year agoSuzi
1 year agoBeckie
1 year agoLouvenia
1 year agoWenona
1 year agoCurtis
1 year ago