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
Getting Started with Stratos - an Open Source Cloud Platform
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Monitor your Production Java App - includes JMX! Low Overhead - Free download
It's a pity that the last few slides and minutes were cut short. I actually listened to the entire talk and was getting into it when Rod started his predictions for the future ... then the edits kicked in and I feel I missed out. Apart from that, I found it quite interesting.
Hi Terence,
Unfortunately, the tape ran out at the end of the presentation - you'll notice that the presentation video length is 63 min. The slot for QCon presentations was 60 min and the tapes have about 63 min worth of room, so the first tape ran out while Rod was wrapping up the presentation (since there's always at least a minute of blank time at the beginning of the tape) - a second one was swapped in as fast as possible to capture the end, but there was between 30 seconds and a minute of downtime as a result.
Thanks,
Ryan Slobojan
Chief Editor, InfoQ.com
I really enjoyed thistalk a lot and pretty much agree with everything point Rod Johnson made, about the history and evolution of Java. We were early adopters where I was working in the mid 90s, when there were no books and JAva was just a promise to rescue programmers from C++ hell. It has pained me to watch it bloat and swell and crush better ideas in it's standardization wake. J2EE made me nearly weep, Object Space Voyager product was the model I was hoping would "win". I especially like the Hibernate example for the power of open source and community adoption or lack there of. I've also been yelling that as JAva developers it's long past time to get out of this anti-MS mindset and admit they have way better tools for developers to build nice tools, and C#/.NEt is a serious competitor that has benefited from correcting some of Java's mistakes just as JAva corrected some of C#'s mistakes. I notice that point was never addressed.
This presentation should be a must see for every Java EE developer.
Rod Johnson really knows about developing Enterprise applications and has lots of good suggestions and insight.
Highly recommended!
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.
4 comments
Watch Thread Reply