About the Blog

  • Software is our business, and perfecting the art and science of delivering it is our mission. The contributors to this blog are passionate about the impact that great teams and good software can have on an organization’s bottom line. They bring decades of experience designing, developing and delivering great software, and each is playing a critical role in Borland’s own transformation.

Blogging Authors

« I was close, gettin' closer, just this far away; come to find out close only counts in horseshoes and hand grenades | Main | The growing influence of FDD in agile and handling scarce skills in multi-team situations »

March 16, 2009


Feed You can follow this conversation by subscribing to the comment feed for this post.


I think Agile by nature un-defines many boundaries, so therefore having a roadmap could assist in refocusing attentions to ensure they are 'on the right track'.

Of course you would want your roadmap itself to be Agile too!


Jeff Brantley

Absolutely correct. In my experience, everyone wants to know they heading in the "right" direction... and the want to be part of the process. We schedule our collaborative product roadmapping sessions every quarter. It really helps the team to know we are continually looking 6 to 8 quarters out and adjusting based upon new information (market, customer, and technical). Do you think I should post more on that topic? Of how we do Roadmapping at Borland?
-jeff b

The comments to this entry are closed.