How to Champion a Successful Software Purchase

Hello, my name is Dax Farhang. I am the Product Manager, responsible for ElectricCommander. From time to time I will post my thoughts on the software industry, the Software Product Management space, and Electric Cloud’s software solutions. I might even toss some darts at our competition if the appropriate mood sets in. Given that I am a member of the marketing organization, there are some who that will contend that all of my posts will merely be veiled attempts to lure you to Electric Cloud products. There’s no point trying to convince those individuals otherwise. Instead I dedicate my inaugural post on this blog to all of you.

Have you ever tried to push a new software tool for your team and failed? Have you ever wanted to drive the purchase and use of a new software application but didn’t feel properly equipped to execute? Anyone on a team is capable of championing this effort with the appropriate approach. It is even more important in a tough economy to present a well-reasoned argument with a reasonable expected ROI fully calculated. Here are a few guidelines that will increase your chance of success.

Read the rest of this entry »

ElectricAccelerator Agent Metrics, part 2

ElectricAccelerator agent metrics provide a tremendous amount of data that you can use to analyze and improve the performance of your builds. Last time we saw how to collect the metrics and we explored the data presented in the Overall time usage section. This time, we’ll look at the data in the Usage records section.

Read the rest of this entry »

The Myth of Continuous Integration

Would you jump out of the airplane and then check your parachute rigging?
Would you start your scuba dive before you checked that your air was turned on?
Would you do your preflight check during the takeoff roll?

I don’t know anyone who would answer yes to any of these questions, yet most of us still engage in the software development equivalent of these risky practices: we check our code in and then do a production build on it.  We’ve even given this practice a name: Continuous Integration.  It should be called Continuous Build Breakage.

Read the rest of this entry »