I just published a short “finding” research note on leveraging open source to save money.
Clients can find it here. It’s a very short piece meant to serve as a quick place holder while I work on a much more in-depth note. I hope to have that one ready by end of February.
Here is a quick excerpt with a couple of key points….
The challenge when optimizing cost with open-source software is twofold:
- First, cost must be reduced in one budget area (for example, acquisition cost), without that cost spilling over into other buckets (for example, service and support). Toward this end, adopters must avoid the common mistake of simply burying and obscuring costs by moving them from one budget area to another.
- Second, reducing budget costs with open source serves little purpose if you reduce the quality of service, or increase the risk beyond acceptable thresholds. Foregoing contracted service and support without realistic internal resource bandwidth to retain service levels will lead to catastrophe that could wipe away any illusion of cost savings.
This is of course old news to OSS insiders but you’d be amazed a the level of confusion I come across in many mainstream IT shops. They are being inundated with so much fear, uncertainty, and doubt from both sides of the debate that they are often paralyzed to act one way or the other.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
How to Live Without Mobile Device Management
This webinar addresses the growing trend of users refusing to have enterprise management of their mobile devices due to privacy concerns....
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.