10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
A practical guide to choosing the right agile tools
Getting Started with Stratos - an Open Source Cloud Platform
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
18 agile and lean practices for effective software development governance
Eric Evans does not seem like great presenter, like his previous presentation on DDD, this too can put you to sleep.
But if you stay awake - he is saying something very important.
Eric is not a presenter, he is a good thinker about software development. His ideas are very exciting and I enjoy listen to them.
I completely disagree with comments about Evans being a mediocre presenter.
I thought this was a great discussion of the current state of DSLs within the context of DDD. All I want from a presentation is digestible interesting content, and Evans does this very well.
Yes, if you have no interest in these topics, Evans's style is not charismatic enough to compel your attention, but if you actually care about these ideas, he's a wonderfully thoughtful speaker.
I have to say I agree with Al on this one. I recently read Evans' book so was keen to watch this to the end.
I would have liked some discussion on language features and their support for DSLs (closures, type looseness, mixins, etc) and the risks that using these features might create in furthering abstractive qualities - I wonder if what he's saying is effectively what Paul Graham said, but from a different angle - i.e. we should all be busy learning Lisp...
That aside, except for some strange camera issues with contrast, I enjoyed this.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
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.
5 comments
Watch Thread Reply