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?
Transforming Software Delivery: An IBM Rational Case Study
Agility at scale, become as agile as you can be
A Guide to Branching and Merging Patterns
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Got to the word "refactor" -- then quits. Maybe related to spotty hotel internet, but it happened three times in a row.
--mj
It is clear that software building has changed over the last ten years. Test driven development makes it possible for us to adapt codebases to the needs of our customers and thus oursevels. "Legacy systems are systems that do not have any tests", then surely legacy systems will diminish over time.
Thanks Michael and Steve for a very good overview of the field.
Great presentation...
One thing that is missing, I think, is the "discussion/socialization" part of the TDD, designing the tests first - boils down to validating the requirements (as well as drafting the design) before starting implementation. TDD forces you to think and discuss about the requirements (as well as the implementation). That's also a reason why its consistent application brings more quality to the product.
The first sentence/title summarizes it all, I think. It is about professionalism... Some people proofread their emails before hitting the Send button, others don't. Some people think about what message they want to convey in an email, others still don't even do that (and it may be because of the context rather than the individual). Still others will think about what they want to say and reflect about the best way to do that, it might be an email, it might be a conversation, but they know that even if they can craft the best wording, it is less important than conveying the message (what) rather than focusing on the phrasing (how)... However, isn't it the case that it takes years focusing on the how and becoming an expert at the how, only to realize that the what is, in the end, the most important...
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.
3 comments
Watch Thread Reply