Yamaha DTXpress/DTXplorer/DTXtreme

--- In DTXpress@yahoogroups.com, "moosetication" <moosetication@y...> 
wrote:
> A long time ago (in a galaxy far, far away) I decided to adopt 
> an "assertive requirements gathering" approach, and I'm still doing 
> it. Why? How does it work? I spend a little time talking to people, 
> then I tell people what they'll get, then I wait to see how many 
> scream, and how loud. Then I filter my assertions based on that, 
and 
> iterate until the screaming becomes muttering under the breath.
> 
> Formulating requirements is hard, and it's not usually due to 
apathy.

Stewart,

Points well taken. Didn't mean to be harsh, just hortatory. What if 
we adopt an assertive requirements gathering approach? In a way, we 
could look at the board that way. If it's hard to formulate what we 
may want and easier to pinpoint what we don't want, let's start with 
the negative and hopefully move to the positive. No one should feel 
like s/he is on the spot, but when the spirit moves, it would be nice 
for it to land here. We can start with the DTXP module (or any other 
product) as the first assertion. We can add to it or subtract from it 
in our unavoidably chaotic and leisurely way until the screaming 
turns to muttering and maybe end up with something; it won't please 
everyone, and won't come from everyone, but that's that. We don't 
have a time limit. We can just keep it in the back of our minds. For 
examplem when someone posts a question that turns on a light, we can 
jot the idea down. You're right that it should be pressure-free, and 
reflect the hobby status that this game is for many. But hobbies are 
also enthusiams, and we can accommodate a bit of heavy interest when 
it arises.

Ed