This is a quick blog post in response to a question I received on a previous article: Close the gap between R&D and Customer Support. Between my long-winded answer and the fact that this subject deserves a post on its own, I decided to respond here.

I came from Google, search for interface between R&D and CS and apparently I came to the right place. Most of your article is clear to me as we are doing it day to day, more or less. Although I’m in the opposite chair (CS manager), I do understand the pressure on R&D as well as on CS. Question is, in an organization which has a habit of issuing new sub versions and major versions quite often (and of course CS attention for bug solving decreases) what can be done in order to assure timely bug fixes, as well as keep releasing new versions as often as possible.

The question of “how to manage frequent release cycles with minimal turmoil and maximum alignment (R&D, CS, Marketing)” is a good one. I highlighted our processes and best practices that worked well for my team. These should not be a surprise, as they are aligned with the agile development best practices. However, note that implementation and execution of these practices require vigor and disciple for all parties involved. I would love to hear from others’ experiences.

(more…)

With the announcement of Apple’s iPad tablet, you may have observed jabs between Apple and Adobe regarding the support of Flash Video on Apple’s iPod/iPhone/iPad platform. Though this article is not about this specific dispute, it has been inspired by the conflict.

Here is a quick backgrounder on the issue. Adobe’s Flash Video (originally developed by Macromedia) is a container format that is used for delivering video over the Internet. Many popular sites use this format to embed video and other content on the Web, such as YouTube, Hulu, Facebook, and Flash-based online games. Through Adobe Flash Player and browser plug-ins, Flash-Video is made available to users. Putting it mildly, Apple has no plans to support Flash on its iPod/iPhone family of products, while Adobe continues to push for its adoption. Instead, Apple has been pushing the HTML5 standard with H.264. For those that are interested, check out the Daring Fireball’s summary on the topic: Apple, Adobe, and Flash.

There are numerous examples of competing technologies: VHS vs. Betamax, Blu-Ray vs. HD DVD, GSM vs. CDMA, .Net vs. J2EE, various flavors of Unix and wireless standards, open vs. DRM, MP3 vs. AAC, AC vs. DC (no, not the music group but Tesla vs. Edison)… In many cases, competing technologies encourage innovation, arguably, sometimes at the cost of building a rich ecosystem. At the same time it is not uncommon for users to experience confusion over compatibility and interoperability, such as in the case with having too many multi-media formats and having to choose a player to match the video format. However, as a technology becomes more attractive, it will see a higher adoption rate, and increasing compatibility and interoperability with others as its ecosystem becomes richer.

This is all good, but as a technology company where do you put your money? As our computing infrastructure becomes more complex and interconnected, your customers are now looking for a total system experience: high-level of system performance and interoperability with others. With this, you need to not only control your technology but also influence and direct related technology decisions with your partners and competitors. To do this, you need to evaluate your technology strategy and decisions within the context of the purpose of your business, technology attractiveness and your ecosystem.  (more…)