Questions for an Enterprise Architect
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
Pimp My Architecture
- Sections
- Process & Practices,
- Enterprise Architecture
- Topics
- Architecture ,
- Enterprise Architecture ,
- Communication ,
- Teamwork
- Tags
- QCon London 2009 ,
- Ivy ,
- Refactoring ,
- Maven ,
- EJB ,
- JBoss ,
- QCon
-
- The next QCon is in London March 5-9, Join us!
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture such as changing the team culture, removing obsolete technologies, allowing mistakes to be made (and learned from), transitional architectures, introducing bounded contexts, refactoring and emergent simplicity, and rotating through roles.
Bio
Dan is a principal consultant with ThoughtWorks, where he writes software and coaches teams in agile and lean methods. He believes in putting people first and writing simple, pragmatic software, and that most problems that teams face are about communication. This is why he puts so much emphasis on "getting the words right", and why he is so passionate about BDD, communication and how people learn.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture such as changing the team culture, removing obsolete technologies, allowing mistakes to be made (and learned from), transitional architectures, introducing bounded contexts, refactoring and emergent simplicity, and rotating through roles.
Bio
Dan is a principal consultant with ThoughtWorks, where he writes software and coaches teams in agile and lean methods. He believes in putting people first and writing simple, pragmatic software, and that most problems that teams face are about communication. This is why he puts so much emphasis on "getting the words right", and why he is so passionate about BDD, communication and how people learn.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
RelatedVendorContent
Getting Started with Stratos - an Open Source Cloud Platform
Agile Development: A Manager's Roadmap for Success
Mobile and the New Two-Tiered Web Architecture
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Related Sponsor
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Excellent talk
by
Paul Fremantle
Posted
Ok....nothing much to take away
by
Sushil Kumar
Posted
My favourite of Dan's talks
by
Elizabeth Keogh
Posted
Wrong title
by
Emeka Kanu
Posted
Good Stuff Here
by
Richard Ruge
Posted
great stuff - for developers, too
by
Gergely Nagy
Posted
Favorite
by
Sonja Threadcraft
Posted
Slides...
by
Richard Fearn
Posted
-
Excellent talk. Thanks!
-
Hear this ramble on about da..da..da.....no real concrete takeaways.
-
I love this talk because as well as teaching a bit about enterprise application architecture, the messes that can be created and some alternatives to that mess, it teaches about the people which create that mess, treating a team with respect and leveraging their enthusiasm for change effectively. IME that's a harder thing to get right than the actual architecture.
Worth watching just for Dan's description of singletons. -
This talk seems to be focusing more on good software development management rather than good architecture. Yes there are the architectural benefits that he talked about. But as a developer, I'm getting more lessons as to how to be a good team leader in the future, rather than being a good architect....No offense
-
'ello 'ello. I thought the discussion was great for the Sr Developer to Architect. This is not about architectural design practices. It's all about selling a good or better software architecture; i.e. pimp = sell. Whether that's to a team, CIO, CEO, whomever. A lot of the time we have a great idea that never gets used for all the reasons that Dan gives in this discussion.
Peace, Richard -
I think there are great thoughts here even for us, "developers".
As Dan points out: the first problem is *not* the lack of technical experience of the colleagues (like knowing design patterns for example, he says most of the guys were skilled enough) but the whole approach, culture, mentality.
That's much deeper than just managers' BS - it's about the real -pragmatic, agile- nature of the software development (rather than the rigid separation of developers/bosses, silos in the Waterfall model).
Maybe more details on techniques wouldn't hurt, but that would have made this much longer - yet, what's said there was a necessary minimum. There just too many of those techniques, and those can be better covered in books like "Design Patterns", Refactoring, TDD, "Working Effectively with legacy code",etc.. -
Excellent. Thanks Dan & InfoQ.
-
...can be found here.
8 comments
Watch Thread Reply