The Agilist versus Data Architect civil (uncivil?) war

Organiser
Melbourne Scrum User Group
Date
Wed, 26 Sep 2012, 08:00 - 11:00 (Add to calendar) GMT
Venue
(Exact location not available) , Melbourne, AU
Cost
Free

There's sometimes a tension between traditional data architects/ modellers, and agilists.

Perhaps it's not too hard to understand. The "data" types feel they?ve been burned by fast delivery of applications that won't integrate with other systems, and the agile developers don't want to sit around waiting for head office architects to describe a perfect start-up model.

One approach to ending this civil (uncivil?) war is to use published data model/class model patterns. These are not the well-known Gang-of-Four ?design patterns?; they are business object patterns (from Martin Fowler, David Hay, Len Silverston and many more). The target outcome from integrating these patterns is to:

1. Facilitate timely delivery of a concise and elegant start-up data architecture.

2. Leverage proven and robust patterns that are easy to extend over the subsequent iterations.

3. Ease the pain of post-delivery integration (as applicable).

A number of case-studies that have applied this pattern-based approach will be referenced, and essential ?lessons-of-experience? highlighted. On-the-fly questions, and even spontaneous exercises to clarify the concepts, will be welcomed as this is intended to be a fun and informative session.

And one free copy of the speaker?s book, ?The Nimble Elephant: Agile Delivery of Data Models using a Pattern-based Approach?, will be offered as a door prize.

You might also like...

Comments

Other nearby events

Map

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” - Martin Fowler