Play Emergent Architecture
Sign in to queue


Agile software development emphasizes that some increment of business value be delivered every iteration. How can this happen when your iterations are two weeks in length and you estimate it will take you two months just to design the database and the access layers? The answer is to think in slices,not layers. In this session,learn how to implement enough of each layer,including the database,to solve that iteration’s problems and provide value to the business. As we use good design principles,engineering practices,and tools,the architecture will emerge. By avoiding big design up front,we’ll skip the wasted coding and brainpower on the low priority user stories. The requirements would have changed before we got to them anyway. If you are thinking this is very difficult,then just remember this FAQ: Does it take a smart person to be an Agile developer? No,it takes a smart person to write software!







The Discussion

Add Your 2 Cents