Comments (8)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 bobleah commented Permalink

I've always believed that TTV (Time to Value) has been a barrier to innovation. However, with the advent of cloud computing, this barrier has been reduced to a mere speed bump. Looking forward to reading your blog!

2 David_Salinas commented Permalink

"Hello World" indeed.... Welcome to the developerWorks blogging community.... nice to see your reference to the traditional software engineering attempt when playing with a new language. Speaking of "Hello World", did you know the first known reference was in Brian Kernighan's 1972 book: Tutorial Introduction to the Language B?

3 thartric commented Permalink

"Barriers to innovation"? First thing that comes to my mind is finding ways to break free of the rules and out of the normal routine. Welcome, and I look forward to following your blog Gina!

4 JanetRWillis commented Permalink

Hi Gina! Good to see you here. Can't wait to read your blogs. !!

5 CJS commented Permalink

Innovation is not just a disruptive force in the marketplace, but also within any organization that is willing to gamble in it, for the simple reason that it breaks down the very structure of how organizations rely on sources for thought and direction. The challenge for many organizations is not in it's ability to have on it's rolls innovative team members, but rather in it's inability to break away from a process that fosters predictable change. The key therefore is how much capital is available within the organization to not just compete but to win in the marketplace, for that to happen however, it should be open to a process that encourages managed chaos and that in my humble opinion is the barrier to innovation.

6 PeterYim commented Permalink

Rational software really facilitates software development and management. Gina, good to see you here sharing your thoughts!

7 tdc commented Permalink

Hmmm, Gina...that name sounds familiar :) It's great to have your blog on My dW, Gina. Loved your article about the opportunities and challenges associated with electric cars in N&amp;O. Others oughta check it out here: <br /> http://www.newsobserver.com/2010/11/04/778771/electrifying-opportunities.html

8 tdc commented Permalink

Gina, in the Web UI development arena, the barriers I see to innovation are more often than not the increasing number of -- and increasingly complex -- standards that we must adhere to - from design through implementation and test. By the time we've run the gauntlet of architectural, functional, system, design compliance, browser, and accessibility hurdles, we're left with little time, or energy, to incorporate innovative solutions. Or, having started out with an innovative solution, we often have to back off due to its non-compliance with one or more standards. As you well know, since day one in dW, we've jumped these hurdles many times, but the cost is greater each year. <div>&nbsp;</div> Of course we'll never be rid of standards, most of which I agree are necessary. But with pressure to deliver [better+more+sooner+cheaper], where does that leave us? <div>&nbsp;</div> One initial step in the right direction would be to provide an abundance of vetted design patterns -- along with tested sample code snippets -- that have passed the above-mentioned hurdles. <div>&nbsp;</div> But design patterns aren't new. The problem is, they're often one-way, developed by one small team and then delivered, end of story. Often there are far too few patterns to cover many possible design situations. A key improvement would be a centralized store for developers, where they could both download and submit unique patterns for all to take advantage of. These days, the idea of one small central team creating all allowable patterns isn't realistic. Ensuring compliance as the 'gatekeepers', maybe, but not creating. Besides, the more that participate, the wider the gamut of designs and ideas. No one team can possibly anticipate the needs of many. Again, dW requirements have proven this over and over again. <div>&nbsp;</div> So, there's one problem and one possible solution. I look forward to reading about other ideas!