Tacking toward agility



Email    print   
May 1, 2008 —  (Page 1 of 3)


If you put a newcomer into a sailboat, give them the tiller and the mainsheet, and tell them to sail upwind, the most likely outcome is that they’ll sail backward. Sailors never tire of talking about making boats go faster and the million different variables that contribute to boat speed. However, you don’t need to know anything about rigging tension and sail shape in order to get moving. You just need to know some basic constraints and rules about positioning the boat and the sail relative to the wind. You might not win races, but you’ll be sailing.

Similarly, for all of the columns we write about fine-tuning approaches to design and architecture, tool choice and process improvement, there are really only a few crucial things that you must take care of in order to start moving forward in software development. Sure, there are teams that seem to do everything right: daily stand-up meetings held as they do 40 minutes of cardiovascular exercise, pair programming while sitting with perfect posture, flossing after every code check-in, and so forth. Most of us, though, struggle with less-than-perfect teams, hoping that the things we are skimping on aren’t the critical ones. These things define our culture and determine the type of programmers who are likely to end up working with us over the long term.

Professional development begins with source control. It’s astonishing to me, but I not infrequently encounter teams that use FTP and e-mail to move development files around. This is simply unacceptable and will immediately “flip the bozo bit” in any kind of skeptic.

In the past few years, the OSS Subversion software has become very common, but I’ve recently become skeptical that it’s a good match for newcomers to version control. While I’ve never lost any data in Subversion, it seems to get into faulty states (“wedged”) fairly often, especially when manipulating large numbers of files, which is done often when introducing a team to source control. While it’s generally easy for an experienced user to fix a Subversion error state, to a newcomer it can be off-putting. There are many choices, but I would suggest SourceGear Vault, Perforce and Visual Studio Team System as alternatives.



Related Search Term(s): Agile

Pages 1 2 3 


Share this link: http://sdt.bz/32021
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Finding the right tool for the agile job
Experts emphasize that tools should bolster the agile process above all else Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb