RE: Use change strategically was RE: [AM] Unfounded assertion

> I was referring to speculation in the sense of anticipating change,
> possibly with no actual sign that such change may be forthcoming.

Ahh. It is a fine line... You should properly model your system in the best
manner possible for your known requirements. You can apply some guesswork
about possible future direction. When doing so, this usually has the effect
about swaying your design one way or another -- with little difference in
current cost.

If it costs you nothing to design one way that gives a probable future
feature an easy time of coming to life in a least disruptive manner, this is
a good thing. It relies on your sense that this probably future feature is a
good bet. It also relies on the cost of going down Path A is nor more than
Path B.

To go down Path C that costs a fortune and has very little likelihood of
coming to fruition, this is irresponsible.


-- jon



> -----Original Message-----
> From: J. B. Rainsberger [mailto:[email protected]]
> Sent: Monday, February 09, 2004 3:02 PM
> To: [email protected]
> Subject: Re: Use change strategically was RE: [AM] Unfounded assertion
>
>
> Jonathan Kern wrote:
>
> >>/seems to be/ that Agile practitioners treat speculative design as a
> >>liability, whereas others treat speculative design as an asset.
> >
> > Hmmm. I hope not. Maybe I misunderstand "speculative design?"
> Do you mean
> > inquisitive or speculative in the investment sense?
>
> By "speculative design" I refer to design elements that do not solve the
> problem as we know it today, but rather are focused on solving parts of
> the problem that we guess are coming. These are design elements that
> address problems or features about whose future existence we speculate.
>
> > I view having an agile model and environment such that one can
> absorb and
> > react to change in a rapid manner.
>
> I was referring to speculation in the sense of anticipating change,
> possibly with no actual sign that such change may be forthcoming.
> --
> J. B. Rainsberger,
> Diaspar Software Services
> http://www.diasparsoftware.com :: +1 416 791-8603
> Let's write software that people understand
>
> For more information about AM, visit the Agile Modeling Home Page
> at www.agilemodeling.com
>

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------