masklinn at masklinn.net
Tue Jun 8 13:03:34 CDT 2010
On 2010-06-08, at 19:48 , Mike Meyer wrote:
> On Tue, 8 Jun 2010 18:16:51 +0200
> Masklinn <masklinn at masklinn.net> wrote:
>> On 8 juin 2010, at 18:02, Mike Meyer <mwm at mired.org> wrote:
>>> There are a
>>> number of different ways to change your general environment, but the
>>> best ones all involve deciding what features you'd like in a release
>>> before you start developing them.
>> I don't really agree with that, time-based release methods don't
>> generally decide on the featureset (indeed sometimes they don't even
>> plan features at all) before development, and I believe they're very
>> nice methods if you don't have to answer to salespeople or a
>> marketting/sales-oriented boss.
> Ok, now I'm intrigued, but on rereading what you're saying is a bit
> ambiguous. Do you really believe that the best workflows don't involve
> planning what features you'd like?
No, I just disagree with your statement that the best workflows always
involve planning release features before even getting started.
> Or do you believe that workflows
> that do that planning are generally best ("nice" in your words) but
> doesn't mesh well with sales?
I believe that workflows which do *not* do that planning don't mesh
well with sales for obvious reasons (salespeople generally promise
stuff to current or future clients, workflows which remove any
guarantee features-wise remove that weapon, which I don't believe is
seen keenly by sales and marketing staff).
> Come to think of it, I've pretty much never had to deal with sales
> pressure. I'll chalk it up as one of the benefits of not working on
> windows products.
I don't think that has much to do with the software's platform, as
much as with the software's audience.
More information about the Mercurial