OpenMethods Blog

We have sprinted, walked, stumbled, fallen down, picked up, battonned hatches, and ultimately have overcome.
After weeks of late nights, code and QA we finally have a release ready.
For those of you who don’t know,
openVXML is our open source, Gui based, VoiceXML development tool.
It is 100% eclipse based and free for everyone to use, tweak, or begin their quest for world domination (hey you’ve got to start somewhere).
Its home project is the Eclipse Voice Tools Project http://www.eclipse.org/vtp

I must say that during this release process I have learned many things. Organizing an open source development effort in a services based environment is tough, priorities are constantly shifting, resources are re-purposed, and there are days you are wondering if this is really going to work or is your boss just playing some sick little joke on you.

Somethings that helped us persevere:

1. A good team goes a long way – This I already knew, but it was re-affirmed in this release, I want to throw some props out to Trip, Lonnie, and Brian for picking up the slack and pulling through.
2. Process Counts – I know all you developers out there are moaning as you read this BUT, a simple concise process is needed if your resources are shifting. It has to be something that anyone can pick up quickly. In the instance of our QA cycles there were multiple occasions where other people had to step in and help out when my main resources were pulled onto other projects. Keeping the process simple and pointed kept the ball rolling.
3. Find something to shoot for – small victories keep people motivated. Don’t overwhelm everybody with the big picture. Everyone needs to be clued in on what your trying to achieve but your have to Break it down and set goals, don’t forget to congratulate people when the goals are met. (I know this seems obvious but it’s easy to forget.)

The trials and tribulations are probably not as important as the fact that we have finally gotten somewhere.
Keep an eye on the website. The new release will be posted soon with some updated documentation, and we’ll be posting more blog entries on some of the new 3.0 functionality

– Tyler

Share via: