Re: Use change strategically was RE: [AM] Unfounded assertion
"J. B. Rainsberger" <[email protected]>
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Message-ID | <[email protected]> |
Jonathan Kern wrote: >>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. That is not my experience. > 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. If I knew which features my customer really needed ahead of time, I'd quit, buy a lottery ticket and relax. Since my customer doesn't even know which features he'll need, what chance do I have? (The implication is correct, but I doubt the hypothesis.) -- 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 --^---------------------------------------------------------------- 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 --^----------------------------------------------------------------