InfoQ Team has published my aricle *-Driven* do not change anything.
I gave a speech on these theses during the 33rd Degree Conference 2013 and I was told I didn't know Domain Driven Desing at all. Well, I have my private opinion about this. But I am sure I know how the cognitive biases work and all that *Driven* madness is one of them.
This article is not intended to criticize anybody or anything. It is about priorities and searching for a balance. Being focused on our basic skills first, helps to use a *-Driven* approach properly especially in an unknown context. I do really appreciate all those mental frameworks because they do great job. But I think if software development is driven by something, these are stakeholder needs and our common sense. Being driven by anything else might be harmful simplification.
Enjoy the article!
agile (39) anti-patterns (17) architecture (32) books (10) buissness analysis (1) cases (1) code speaks 2u (3) conferences (13) conversation patterns (26) customer collaboration (14) ddd (4) design patterns (15) dialogi (1) dsl (2) effectiveness (19) embedded (1) events (21) gtp (4) info (2) infoq (5) kanban (2) lean (2) master (1) measuring (1) orm (2) pea (2) product humanisation (1) refactoring (13) requirements (7) retrospections (1) retrospective (1) scrum (9) scrumguide (1) sm (1) soft skills (4) software craftsmanship (14) tdd (1) team (20) time management (3) tutorial (1) uml (1) user stories (1) visions (26)