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?
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Getting Started with Stratos - an Open Source Cloud Platform
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
The fun stuff sucked. Also the "No emails" while working really sucked as well. An employer should not control that. Its the motivation of the employee.
Are you speaking as somebody who worked on this project?
No
Very inspiring talk - in the technical domain.
However, with all respect, the workspace in this project is TERRIBLE! 40 people crammed into a room, each with less than 1 meter distance to his neighbour. Background music you cannot escape from, like in a supermarket? The blinds are down and the artificial light is on! Why? Apparently because the projections would otherwise not be readable.
You can't be serious.
The submarine comparison is quite valid. But what is so terrific about working in a sub? It is one of the worst places to be that I can imagine.
It is no surprise to me that Neil emphasized "fun stuff" so often, because the fun is not apparent at all, at least for me. I can't be fun working in a chicken farm like this 10 hours a day. The silly Starbucks cup thing looks more like a desperate attempt to me.
Answer yourself a simple question: can you imagine spending your professional life (yes, that's 30 years and more) in such an environment? I bet you don't!
Hi Christopher,
Your comment was deleted because it added little to the discussion, and it was in a very negative (non-constructive) tone. Please feel free to find a way to express what you were trying to say again, but in a constructive manner - your previous comment appeared to be a series of potshots with nothing else of benefit, and which was only very loosely related to the discussion in this thread.
Thanks,
Ryan Slobojan
Chief Editor, InfoQ.com
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