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?
Free Gartner Cloud Services Brokerage Report
Agile Development: A Manager's Roadmap for Success
18 agile and lean practices for effective software development governance
Agile Maturity Model Applied to Building and Releasing Software
Complimentary Gartner (Hype Cycle for Cloud Security Report)
JP is truly one of the great thought leaders, many of his ideas were years, even a decade ahead of their time, there are things he suggested years ago that are only now starting to be thought of as new ways of doing things.
In many cases JP was the reason people wanted to work for DrKB, he was the man behind OpenAdaptor released in 2001. He was driving open source in the bank before most people knew what it was. He stopped paying Microsoft and bought hundreds of Macs for his developers. The developers left other banks to work under JP. Because he had such high quality staff he was able to reduce head count and effectively cost.
You really need to watch this if you're into open source or work for a bank.
-John-
My favorite moments (around the 40 minute mark)...
- Three pieces of advice for architects: Don't actually write an enterprise architecture, it's too controlling and stifling ("I'm proudly accused of not having one"), don't write hard policies & guidelines ("you must [instead] have principles that are flexible"), engage with the teams ("The architect is the de facto project manager. It is not an ivory tower job.").
- Cameron asks, "What are the biggest factors that contribute to project failure?" Without hesitation, JP says, "an unwillingness to say 'no' to the customer."
Can this article be reproduced in a podcast / text form so that it can be acessed in full-text form?
would love to have a copy of this presentation if there is one available. May I request for one? thanks.
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