<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://port25.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What does business readiness of software really mean?</title><link>http://port25.technet.com/archive/2006/07/18/What-does-business-readiness-of-software-really-mean_3F00_.aspx</link><description>There is a buzz word floating out there – “business readiness”. It seems that the marketing teams here at Microsoft are trying to capture something important to organizations and people that are responsible for selecting, deploying and maintaining software</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 40109.1145)</generator><item><title>Learning from OSCON 2006</title><link>http://port25.technet.com/archive/2006/07/18/What-does-business-readiness-of-software-really-mean_3F00_.aspx#2930</link><pubDate>Tue, 15 Aug 2006 23:51:03 GMT</pubDate><guid isPermaLink="false">af7480c4-26b7-468d-87b0-2acebabb473d:2930</guid><dc:creator>Port 25</dc:creator><description>Hank Jenssen and myself attended the OSCON on the 27th and 28th of July. We did not attend the tutorials or the Executive briefing but were there two days of the two and a half days the sessions were in progress. We also attended the keynotes on both&lt;img src="http://port25.technet.com/aggbug.aspx?PostID=2930" width="1" height="1"&gt;</description></item><item><title>re: What does business readiness of software really mean?</title><link>http://port25.technet.com/archive/2006/07/18/What-does-business-readiness-of-software-really-mean_3F00_.aspx#2844</link><pubDate>Thu, 27 Jul 2006 17:16:42 GMT</pubDate><guid isPermaLink="false">af7480c4-26b7-468d-87b0-2acebabb473d:2844</guid><dc:creator>BrianLy</dc:creator><description>&lt;p&gt;Interesting and appropriate posting!&lt;/p&gt;
&lt;p&gt;My view on 'business readiness' is that the developer or ISV has considered integration and deployment aspects of the software. It's all well and good setting up an instance of your software on your own development servers, but having a real customer do it can be eye opening.&lt;/p&gt;
&lt;p&gt;The problem varies depending on the scale of the client as well. Smaller organisations are likely to be less risk averse and have the ability to jig some servers around, simply because a small group of people are involved and they are close to the business. Large organisations are different. Here you have people specialising in specific areas - directory services, database, middle-tier etc. You need to be able to get buy-in from management groups in all of the areas. In most cases you will also struggle with technical incompetence and internal politics as well.&lt;/p&gt;
&lt;p&gt;All of this is fairly applicable to open source since the onus is going to be on the people implementing the solution. &amp;nbsp; An IT may have to pull the solution together and in many cases the business will not be fully confident in their capability. This doubt results in second thoughts from management and lots of rumours with IT of how difficult open source is...&lt;/p&gt;
&lt;img src="http://port25.technet.com/aggbug.aspx?PostID=2844" width="1" height="1"&gt;</description></item></channel></rss>