-by Jeremy Thake, MCT, MCTS

With organizations expanding their usage of SharePoint as a development and web infrastructure platform, managing team development, release cycles, and updates across distributed SharePoint farms can be a complex undertaking.  To make sense of this Lifecycle, Mr. Thake reviews a variety of considerations, including:

• A review of SharePoint Assets
• Architectural Considerations
• Team Development
• SharePoint Application Lifecycle Maturity Model
• Deployment options for solutions, content, and other artifacts

	Register for a free copy of the Whitepaper
	*First Name:
	*Last Name:
	*Company:
	*Job Responsibility	-- Please select -- SharePoint Developer SharePoint Administrator Architect Integrator Business Stakeholder Other
	*Geographic Region	-- Please select -- North America South America Europe Asia-Pacific Africa Middle-East
	*Corporate Email:
	*Are you currently building, or do you plan to build any of these sites on SharePoint? (check all that apply)	Internet (Public Facing Sites) Extranet Intranet Not at this time
	*How many SharePoint Farms does your organization maintain?	1 4-5	2-3 6 or more
	*Do you currently maintain separate Dev, Staging, & Production environments for SharePoint?	Yes No Not now, but we plan to
	*How Many SharePoint Developers and Admins does your organization currently employ?	1-5 11-15	6-10 16 or more
	*Are you interested in a live demo or free eval of ROSS (Dev/Stage/Prod replication software)?	Yes No Thanks
	Please use a valid corporate email address. On successful submission of this form, a copy of the whitepaper will be emailed to you at the address you provide.

About the Author

Jeremy Thake, SharePoint Server MVP and founder of SharePointDevWiki.com, is a Microsoft Certified Trainer and Technology Specialist in WSS and MOSS. Jeremy is also a sought-after speaker at SharePoint shows and events.

Whitepaper sponsored by RepliWeb.To learn more
about RepliWeb and its line
of SharePoint solutions,
please visit their website at:

www.repliweb.com