Loading ...
Sorry, an error occurred while loading the content.

Re: [agileDatabases] Agile Implementation of Netezza/Cognos Implementation

Expand Messages
  • Scott Ambler
    GT Agile or not, technological and data dependencies cannot really be sidestepped by refactoring . But, they can often be addressed through mocks or
    Message 1 of 5 , Sep 17, 2011
    • 0 Attachment
      GT > Agile or not, technological and data dependencies cannot really be sidestepped by 'refactoring'.

      But, they can often be addressed through mocks or stubs.  Of course, you should probably do some initial requirements and architectural envisioning to identify them in the first place.
       
      GT > Only after evaluating the impact as minor and the benefits as sufficient to outweigh the negative impacts, the database schema changes while a code iteration is in train.

      Agreed.  This is exactly the first step of the process of database refactoring, doin a reality check to determine if it makes sense to do so.
       
      GT > While one or more code iterations are taking place in paralle, the data design and ETL are working on their iteration of the db schema and data, which will be consumed by later code iterations.

      Better yet, this could occur in a "whole team" manner where data-experienced people are embedded in the actual team.  This can improve productivity by reducing overall overhead.  Unfortunately this can be difficult in many companies due to the organizational complexities resulting from the cultural impedance mismatch between data and development professionals.

      - Scott 
      Scott W. Ambler
      Chief Methodologist for Agile/Lean, IBM Rational
      Agile at Scale blog: http://www.ibm.com/developerworks/blogs/page/ambler
      Follow me on Twitter: http://twitter.com/scottwambler


      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.