This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
Hi Here is my query. One of the important charactersitics of Agile methodology is [B]SPEED[/B]. How does Agile handle projects that involve Legacy systems? What techniques does this Methodology adopt for these Legacy systems that involve huge volumes of data? How does Agile handle Relational data issues which may be time consuming? Does your book address these topics?
I think the book authors have "left the building" but we can still talk about your questions. The biggest problem with legacy systems is a lack of tests. In fact some folks define legacy as anything lacking automated tests.
I have to say a mainframe team I was on in the 80s was pretty darned agile even without automated tests and formal iterations. We broke work down to very small jobs with real customer value, worked from a prioritized backlog, worked closely with the customer, delivered software and received customer feedback very quickly.
You mentioned huge amounts of data. How would that slow down coding and testing and other agile practices? Maybe we can come up with ways to get around it ... like testing only a small number of representative cases instead of a hundred-million-record master file.
BTW: Somebody will be around to talk about ranch name policies. You can go into your profile, select change name and read the policies to beat them to it.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi