Comments on: Enterprise Software Innovator’s Dilemma

By: Agile Considerations for CXOs « The Agile Executive

Agile Considerations for CXOs « The Agile Executive — Sat, 05 Dec 2009 01:41:17 +0000

[...] Market-of-One [...]

By: Only 10% « The Agile Executive

Only 10% « The Agile Executive — Mon, 06 Jul 2009 14:09:01 +0000

[...] a comment » Readers of the posts Customer Intimacy and Enterprise Software Innovator’s Dilemma might recall two observations made in this [...]

By: Are We at a Point of Saturation? « The Agile Executive

Are We at a Point of Saturation? « The Agile Executive — Sun, 19 Apr 2009 17:43:13 +0000

[...] was pointed out in Enterprise Software Innovator’s Dilemma that ”good enough” Open Source Software is inevitably becoming good enough. If you [...]

By: Companies make shoes! « The Agile Executive

Companies make shoes! « The Agile Executive — Thu, 16 Apr 2009 17:20:41 +0000

[...] software companies, the impact of “good enough” Open Source Software should be assessed in conjunction with close examination of the market value to revenues ratio. [...]

By: Microblogging Will Marginalize Corporate Email « I’m Not Actually a Geek

Fri, 13 Mar 2009 16:36:24 +0000

[...] about the Innovator’s Dilemma in the enterprise software space comes from this blog post, Enterprise Software Innovator’s Dilemma. Existing vendors expand the functionality of their products, heavily relying on the requests of [...]

By: Why Agile Matters « The Agile Executive

Why Agile Matters « The Agile Executive — Tue, 03 Mar 2009 03:06:48 +0000

[...] a low-cost input for traditional enterprise software vendors are dire. As pointed out in the post Enterprise Software Innovator’s Dilemma, some low-cost input effects are already manifesting themselves through Open Source [...]

By: Viva le re-volition « Folknology

Viva le re-volition « Folknology — Sun, 08 Feb 2009 21:03:29 +0000

[...] requisite and turning a few heads. In the enterprise we are also seeing OpenSource as being ‘good enough‘ and I don’t mean that in a bad way, good enough is really important and is a definite [...]

By: israelgat

israelgat — Wed, 04 Feb 2009 14:45:15 +0000

Hi Jamison,

The good points you bring up are discussed in my recent Cutter Consortium essay “To Release No More or To “Release” Always” Here is a quote from the essay:

As an example, PatientKeeper maintains “…at least 45 releases in the field at any one time.” Using VPN technology, PatientKeeper “… try to get everyone on the latest release about once a year.”

As Michael and I write in this blog about striking a balance between engineering considerations, market considerations and customer considerations, we will address additional aspects of market-of-one. Stay tuned…

Best,

Israel

By: Jamison Gray

Jamison Gray — Wed, 04 Feb 2009 02:32:11 +0000

I am skeptical but intrigued, as I presume you’ll
present some answers to what must be the obvious
concerns about this Market of One concept, such as:

* maintenance of customer-specific changes alongside future development in the code base. This just seems like a nightmare if you’re accumulating custom-build features into your code but trying to move all versions of your software forward (or am I misunderstanding the idea? Are these “custom release” features all developed in the main line of code?)

* support issues when each customer could be running a distinct version of the software

* what continuous integration looks like in this world

* whether focusing on Markets of One and their desired features is the enemy of the kinds of innovation that could “raise the bar” and move that Customer Requirements line up.

I know, this last point is trying to make the case for keeping focus on approach 2 in this article, of “functional differentiation” – which is claimed here to be less promising in today’s world of competing with OSS. Still, the title of this article implies
an interest in innovation, so I’m wondering whether
one can still pursue it while following this
approach.

– Jamie

By: Li

Li — Wed, 28 Jan 2009 18:49:43 +0000

Very interesting and widens horizons.

The info is very constructive

Please continue it help to understand the process.

Thanks L