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.
Posted by Mike Bria on Aug 20, 2008
The problem with my proposal is that it is not a balanced value statement. In the other four statements we value the second item. We just value the first item more. But in my proposed addition, we simply don’t value crap at all.Many people have spoken up in response to Bob's posting, proposing their own revisions to the original devalued item "crap". Among these responses were: ["Craftsmanship over..."] Heroics, Production, Engineering, Hacking, Brinkmanship, Efficiency, Quantity, Toil, Yield, and even Scrabble.
So I hereby change my original proposal, which was made for dramatic effect, to:Most software development teams execute, but they don’t take care. We value execution, but we value craftsmanship more.
- Craftsmanship over Execution
Five Key Practices to Agile ALM
Agility at scale, become as agile as you can be
A practical guide to choosing the right agile tools
A Guide to Branching and Merging Patterns
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
...oddly, seems to have gotten little attention. No comments?
Don't get me wrong, I don't take it personally or anything, but the funny thing is, this is status quo. What I mean is, this is probably one of the most important topics of our industry (unfortunately), has been for oh so long, but nonetheless always seems to be something that gets little explicit attention (even more unfortunately). And as a result, simply continues on and on as "one of our biggest problems". Chicken, or the egg?
In other words, art imitating life. Neat-o! ;-)
The value statement 'craftsmanship over execution' should be added to the Manifesto. A lack of craftsmanship in so-called agile teams is very worrying and is very pertinent to my work at current clients.
I agree that the Manifesto could use this ammendment; even though the original document already provides for this by way of principle #9 which states literally:
Continuous attention to technical excellence
and good design enhances agility
Having it in the main body of the manifesto would bring it the importance it deserves.
For an interesting, different take on Craftsmanship, see the David Anderson talk from Agile2008 that just went up: Future Directions for Agile
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