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?
It was a very nicely put dilemma with good examples, congratulations!
I found one important for me point missing there though, which is code maintenance. I do agree forcing a generic solution to a peculiar problem often results in extra tedious and unnecessary work. Sometimes when the choice is not so obvious I would also consider the fact a generic solution might save you a couple thousands lines of code. These lines might be easy to write but you will have to maintain them later. And if they are easy to write you might be tempted to have them written by a novice developer which certainly won't help the code readability. So maybe it would be better to have a hundred lines of clumsy configuration after all in such case?
Really like the presentation
"It depends.." .. A truly generic answer :)
Probably, a generic solution is merely a specific solution to a set of similar problems.
Unfortunately, most of the time there is no definition for that similarity.
I have always found the generic home build frameworks much harder to read, test and debug than the specific and perhaps boring solution.
Even worse is the specific and undocumented configuration DSL that you invent for your generic framework. It might work for you but 'then come the next guy'.
I would say go for the safe solution, the solution that you know will work. Boring code is very quick to write, it's the thought of repeated work that is hard to cope with. Then when you have a working solution, look for patterns, refactor and generalize.
I would worry more about the novice architect than the novice developer.
the app framework of devexpress www.devexpress.com/Products/NET/Application_Fra... is a perfect example.
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