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?
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Agile Development: A Manager's Roadmap for Success
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
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!
I tend to disagree with a lot of the Agile(tm) Consultants(tm) and Speakers(tm), but I really do like the core idea that one can view "Code Quality as a Corporate Asset". Whether or not one can have get "the CEO [to come] into the room and [say]" anything seems about as far-fetched as the other Schwaberisms, but we (anyone writing code -- even test code and example code) should always view "Code Quality as a Corporate Asset", and we should also view it as our craft, i.e. we should build it with great pride of worksmanship.
Peace,
Cameron Purdy
Tangosol Coherence: Clustered Cache
Great presentation!
I have to admit that I too find the Agile(tm) Consultants(tm) and Speakers(tm) to be a bit underwhelming in their rhetoric. Scrum as a management process is what usually draws me to these presentations and the key to this presentation is that Scrum builds in transparency into the process. That's not to say that RUP, Waterfall, etc. can have equal transparency, but short iterations do put the spotlight on potentially ugly practices...and that's the key to the this presentation. What do you do when presented with difficult decisions?
In Beck and Schwaber's words: have the courage to do the ethical thing.
Scrum as a management process is what usually draws me to these presentations and the key to this presentation is that Scrum builds in transparency into the process.
Yes, this emphasis on transparency is one of the things that draws me to Scrum as well. But, as others have said, a good process cannot "fix" shoddy developers. Scrum relies on the team to bring skill and common sense into the mix.
We can add: a good process cannot hide or compensate for a lack of coaching ethics. We need good processes and good people. If forced to choose... recent experience suggests: go with the good people :-)
If forced to choose... recent experience suggests: go with the good people :-)
Hopefully you're never forced to choose. I think your point about going with good people as a safe bet is that someone will emerge as a leader and put a process in a place.
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?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Andreas talks about the benefits of the Open Web and how it compares to proprietary stacks. He also talks about various projects that push the envelope like Boot to Gecko, Broadway and pdf.js.
Ron Bodkin discusses early adoption of Hadoop, NoSQL and describes MapReduce and related libraries and Frameworks. Other topics include Hive, Pig, multi tenancy, and security in a big data environment
Stephen Bohlen explains how Spring helps with interoperability between Java and .NET, demoing it with the help of a sample application.
Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.
4 comments
Watch Thread Reply