The Emotional Design Challenge

When designing any architecture as architects we often tend to underestimate some areas, while overestimating others. Typical examples in underestimations are around the data availability and documentation when designing interfaces or to overlock manual business continuity. Examples of overestimation are areas like terrorism or potential non-availability  of less critical systems. This under- or overestimation is … Continue reading The Emotional Design Challenge

Do Not Confuse Data Governance With Data Management

Last week, I participated in a roundtable during a conference in Paris organized by the French branch of DAMA, the data management international organization. During the question/answer part of the conference, it became clear that most of the audience …

Do not confuse data governance with data management

Last week I participated in a roundtable during a conference in Paris organized by the French branch of DAMA – the data management international organization. During the question/answer part of the conference, it became clear most of the audience was …

Form Follows Function on SPaMCast 381

This week’s episode of Tom Cagley’s Software Process and Measurement (SPaMCast) podcast, number 381, features Tom’s essay on Agile adoption, Kim Pries talking about technology’s gender gap, and a Form Follows Function installment on the fallacy of greenfield development. Tom and I discuss my post “The Seductive Myth of Greenfield Development”. We talk about how […]