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 Dec 18, 2008
Corey Haines has recently embarked on a unique personal "Pair Programming Tour" around central US. Now three weeks into this innovative journey, Haines has posted video interviews revealing many of the unique insights he's gained about pairing, automated testing, and the evolution of a software craftsman while sharing the keyboard at the home-bases of Dave Chelimsky, Brian Marick, Uncle Bob Martin, and others.
Inspired initially by the Hungarian mathematician Paul Erdős, Corey Haines has embarked on a tour in the name of increasing our industry's emphasis on software as a craft. Like Erdos did in the mid twentieth century, Haines is currently traveling around the upper midwest to practice software development (rather than mathematics) with a wide range of his peers and mentors. To "pair" with them.
While he's dubbed the tour a "Pair Programming Tour", it's ultimate intent is somewhat less about the practice of pair programming per se than it is about the ideas of what it takes for a software developer to really become good at what he or she does. As Corey himself stated when InfoQ caught up with him:
The tour is the beginning of providing a mechanism for people to gain the benefits of the journeyman mentality, traveling and working with different people.
In essence, Haines is acting on a quite literal interpretation of the belief that software is craft, and one that can only be mastered through hands-on experience with different problems and exposure to the learnings of other craftsman.
Regarding how the tour has helped him personally in this way, Haines had this to say about the 3 weeks he's spent thus far passing the keyboard with others:
One thing that stands out is the benefits I've gained by pairing with such a wide range of people on different projects: a Ruby Cocoa application; a Ruby VM in ActionScript; Merb-, Rails- and Limelight-based apps; and, good old Ruby. I've seen a lot of different environments, from offices to living rooms, which has given me a different perspective on people, as well.
Haines has captured video interviews with each of his hosts and posted each to the blog tracking the progress of his tour, allowing us to also share in his "exposure to other craftsmen's stories". In these interviews you'll hear various stories and viewpoints from Uncle Bob Martin, Brian Marick (Part 1 and Part 2), David Chelimsky, Micah Martin, Dave Hoover, and Eric Meyer. Each of these interviews are well worth watching in their entirety, but a few of the highlights are:
Set some time aside to check out Corey's record of his tour, share in the insight he's taken the initiative to gather over the past few weeks.
And as always, don't be shy, login and comment below to let everyone here know what you think about Corey's Pair Programming Journeyman Tour!
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
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.
No comments
Watch Thread Reply