Re: Needs to know everything; was: RE: [AM] ZZZ

In a message dated 2/9/2004 7:13:27 AM Pacific Standard Time, 
[email protected] writes:

> A thought about the problem - maybe data is not agile because it is the 
> trail left (or the framework needed) by the execution of business processes and 
> policy - and the data can only be as agile as the things it records. Which is 
> often pretty staid.
> 
> 

Dagna:

Excellent points, particularly that of defining the DBAs perspctive of risk. 
This is something we should be cogniant of when dealing with the data guys. 
They see software in an entirely different light than developers. Further, their 
anxieties typically grow exponentially with the length of time the system has 
been in use. We have often described the problems of having to maintain 
software developed long before we get involved with it: the lack of documentation 
and knowlege, etc. The same is true of the data guys: DBAs come and go, but the 
data (an important business asset) remains. While the risks associated with 
modifications to the software can be substantial, programmers have some degree 
of controlling that risk. Modifications to the structure of the data (schemas, 
loss or corruption of the data, not getting everything changed and back in 
sync, adverse effects on applications, etc.) may be perceived as posing a 
greater risk, at least to the DBAs, as well as management, 

Regards,

Pete

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
--^----------------------------------------------------------------