Analogue-sequencer

--- In analogue-sequencer@yahoogroups.com, "Steve" <c0nsumer@...> wrote:
>
> I hope I'm not overstepping my bounds here, but after the recent
> discussions I feel compelled to say something. Expecting Colin to keep
> adding more and more features to the P3 long after it has shipped, and
> particularly a new OS version for a small user base without any
> renumeration, seems to be crossing a line.

The software projects I've worked on approach this thusly (borrowed
freely from RUP), in three separate steps:

REQUESTS (literal requests from users with absolutely no expectation
given that the request will see the light of day. Also known as
wishlists.)

FEATURES (analysis done on REQUESTS to align with the actual system
the request will alter. Again, absolutely no expectation given the
FEATURE will see the light of day.)

REQUIREMENTS (analysis done on FEATURES to determine high level
approach, probable cost and complexity to implement, priority, and
benefit. Only high priority REQUIREMENTS can be assumed to be in scope
for a release.)

I believe what Steve is saying is that we are all giving REQUESTS and
not giving REQUIREMENTS. Expectations and tone should be adjusted
accordingly;^)

-Jim, who is quite happy with the overwhelming flexibility of the
current P3 OS.