<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: What questions should we ask before architecting a SharePoint solution?</title>
	<atom:link href="http://tech.ahmedshokr.com/2009/09/27/what-questions-should-we-ask-before-architecting-a-sharepoint-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.ahmedshokr.com/2009/09/27/what-questions-should-we-ask-before-architecting-a-sharepoint-solution/</link>
	<description>To be creative, you must believe that you are!</description>
	<lastBuildDate>Wed, 23 Jun 2010 11:55:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ahmed Shokr</title>
		<link>http://tech.ahmedshokr.com/2009/09/27/what-questions-should-we-ask-before-architecting-a-sharepoint-solution/#comment-68</link>
		<dc:creator>Ahmed Shokr</dc:creator>
		<pubDate>Tue, 29 Sep 2009 01:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://ahmedshokr.wordpress.com/2009/09/27/what-questions-should-we-ask-before-architecting-a-sharepoint-solution/#comment-68</guid>
		<description>Thanks, Yassmeen
Look, in any enterprise the need of the internal team to 100% own the proposed solution is out of question.
This means they have to know exactly the solution architecture, the source code must be fully commented and clear, all the application events logged, etc
So, if anything needs attention the internal team itself can solve it without being under the mercy of the vendor (The software builder).
In order to provide that level of ownership, we need to give the client the following:

1. Detailed tracking and monitoring
2. The ability to do changes on the implemented components (Clear, clean, well documented source code)
3. What is needed from the internal team to master the technology itself (with the required level to own the application), focusing on the components which used in the application.</description>
		<content:encoded><![CDATA[<p>Thanks, Yassmeen<br />
Look, in any enterprise the need of the internal team to 100% own the proposed solution is out of question.<br />
This means they have to know exactly the solution architecture, the source code must be fully commented and clear, all the application events logged, etc<br />
So, if anything needs attention the internal team itself can solve it without being under the mercy of the vendor (The software builder).<br />
In order to provide that level of ownership, we need to give the client the following:</p>
<p>1. Detailed tracking and monitoring<br />
2. The ability to do changes on the implemented components (Clear, clean, well documented source code)<br />
3. What is needed from the internal team to master the technology itself (with the required level to own the application), focusing on the components which used in the application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yassmeen</title>
		<link>http://tech.ahmedshokr.com/2009/09/27/what-questions-should-we-ask-before-architecting-a-sharepoint-solution/#comment-67</link>
		<dc:creator>yassmeen</dc:creator>
		<pubDate>Mon, 28 Sep 2009 22:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://ahmedshokr.wordpress.com/2009/09/27/what-questions-should-we-ask-before-architecting-a-sharepoint-solution/#comment-67</guid>
		<description>Clear and organized way but I it is from a very high level prospective which i guess is normal because it addresses Moss solution in general

My question is what do you mean by Ownership ? do you mean security Roles and who can do what in the system or administration in general.</description>
		<content:encoded><![CDATA[<p>Clear and organized way but I it is from a very high level prospective which i guess is normal because it addresses Moss solution in general</p>
<p>My question is what do you mean by Ownership ? do you mean security Roles and who can do what in the system or administration in general.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
