<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Software as a Service: Just a delivery model?</title> <atom:link href="http://onproductmanagement.net/2007/06/26/software-as-a-service-just-a-delivery-model/feed/" rel="self" type="application/rss+xml" /><link>http://onproductmanagement.net/2007/06/26/software-as-a-service-just-a-delivery-model/</link> <description></description> <lastBuildDate>Tue, 22 May 2012 19:30:38 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1.2</generator> <item><title>By: Alan</title><link>http://onproductmanagement.net/2007/06/26/software-as-a-service-just-a-delivery-model/comment-page-1/#comment-2468</link> <dc:creator>Alan</dc:creator> <pubDate>Wed, 27 Jun 2007 00:52:17 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/06/26/software-as-a-service-just-a-delivery-model/#comment-2468</guid> <description>It is a truism to say that the answer is based on your frame of reference. Perhaps you think it sounds like a small point to distinguish between the terms &quot;consumption&quot; and &quot;delivery&quot;. But this is exactly my point: enteprise software companies are thinking of things from their own perspective, which leads to terms like &quot;delivery model&quot;. If we think about it as a consumption model, we are more likely to think more broadly than just the software; it&#039;s about the whole experience of consumption.I&#039;ll be publishing an article later this week in which I get into more detail about the overall experience of consumption of SaaS. I believe that SaaS is a revolt against the sins of enterprise software past... more tomorrow.</description> <content:encoded><![CDATA[<p>It is a truism to say that the answer is based on your frame of reference. Perhaps you think it sounds like a small point to distinguish between the terms &#8220;consumption&#8221; and &#8220;delivery&#8221;. But this is exactly my point: enteprise software companies are thinking of things from their own perspective, which leads to terms like &#8220;delivery model&#8221;. If we think about it as a consumption model, we are more likely to think more broadly than just the software; it&#8217;s about the whole experience of consumption.</p><p>I&#8217;ll be publishing an article later this week in which I get into more detail about the overall experience of consumption of SaaS. I believe that SaaS is a revolt against the sins of enterprise software past&#8230; more tomorrow.</p> ]]></content:encoded> </item> <item><title>By: saeed</title><link>http://onproductmanagement.net/2007/06/26/software-as-a-service-just-a-delivery-model/comment-page-1/#comment-2467</link> <dc:creator>saeed</dc:creator> <pubDate>Tue, 26 Jun 2007 19:10:30 +0000</pubDate> <guid
isPermaLink="false">http://onproductmanagement.wordpress.com/2007/06/26/software-as-a-service-just-a-delivery-model/#comment-2467</guid> <description>Well, it&#039;s both a consumption model and a delivery model. The answer, of course, is based on your frame of reference at the time. Some vendors can deliver their product both ways: i.e. either via SaaS or on-premise to a customer. I&#039;m assuming, those customers pay for (consume) the software differently, depending on the model.The general thinking is that it will be very difficult for software vendors to support both models efficiently as the processes for delivering (selling and supporting) them are different. I tend to agree with this, though certainly some companies today (e.g. SugarCRM) are succeed with a dual delivery model. I could make a joke here about Sugar consumption, but I&#039;ll refrain.</description> <content:encoded><![CDATA[<p>Well, it&#8217;s both a consumption model and a delivery model. The answer, of course, is based on your frame of reference at the time. Some vendors can deliver their product both ways: i.e. either via SaaS or on-premise to a customer. I&#8217;m assuming, those customers pay for (consume) the software differently, depending on the model.</p><p>The general thinking is that it will be very difficult for software vendors to support both models efficiently as the processes for delivering (selling and supporting) them are different. I tend to agree with this, though certainly some companies today (e.g. SugarCRM) are succeed with a dual delivery model. I could make a joke here about Sugar consumption, but I&#8217;ll refrain.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User is logged in)
Database Caching using disk: basic
Object Caching 317/318 objects using disk: basic

Served from: onproductmanagement.net @ 2012-05-22 21:01:23 -->
