1. Site Lifecycle – Creating and Archiving Sites Robert Bogue Thor Projects Rob.Bogue@ThorProjects.com

2. Who am I? 7 Time Microsoft MVP currently awarded for SharePoint Architect = Developer + IT Professional Author of The SharePoint Shepherd’s Guide for End Users – and 17 other books. Blogger: http://www.thorprojects.com/blog http://www.thorprojects.com/blog

3. What is Site Lifecycle?

5. What am I going to cover? Why managing site lifecycle is important The provisioning process Demonstrate site provisioning workflow The archiving process Demonstrate identification, approval, and archiving of sites Business Considerations for site lifecycle

6. Site lifecycle seems simple but…

7. …soon opposing forces show up Getting business done Information architecture ControlGovernance Operational Costs User Empowerment IT Concerns

8. Chasing your tail – creation and removal Provisioning Archival

9. Provisioning If IT Managed ● Manual / Time Consuming ● Expensive / Precious Resources Required If User Managed ● Illogical information organization ● Unusable site structure ● Inconsistencies

10. Archival IT Concerns ● Difficulty discovering abandoned sites ● Costly resources consumed ● Increased legal risk ● Reduced Search Relevancy User Concerns ● What, me worry…

11. Site lifecycle seems simple but…

12. Provisioning Stages Site Creation Request User Request Business Event Provision Site(sites) Site collection or sub site? What type of site? Where to locate? Post creation events Correlating data like business event data Related metadata like classification from taxonomy Notifications

13. User Input User request provisioning flow

14. Business Event Event driven provisioning flow

16. Proposed Solution – User Created Example Request information including cost centers (for chargeback) Forms Library Gets business approval for charges Get IT approval for name & location Create Site Notify user Gets business approval for charges Get IT approval for name & location Create Site Notify user

17. Site Archival

18. What do I mean by Archive? Site Backup (optional) Site Deletion (always)

19. Archival Stages Identify Archive Candidates Limited/no site usage Closed state (for example, project completed) User Initiated Centralize view candidates Obtain Archive Permission Notify and obtain owner permission to remove Notify IT admin of intent to remove Archive Backup if appropriate Delete site Notification owner and it admin

20. Solution: Site Archival

21. Monitoring Site Usage Typical Site States ● Active (Read-Write) ● Reference (Read) ● Inactive Solution: Site Level Workflow and centralized process ● Workflow Monitor for activity (read or write) ● Workflow may move active to reference ● Administrative removal/automation of inactive

23. Site Monitoring

24. Site Collections vs. Sites Site Collections Cost accounting The operation typically requires IT Pro without automation Impacts information architecture Sites Manage information architecture Typically Provisioned by a Power User Impacts site collection utilization

25. Site lifecycle related aspects Risk and resource management Workspaces Information Architecture

26. Information architecture Do I understand where I should go? Can I get where I need to go quickly? Are my experiences consistent? Does the site I’m using solve my problem?

27. Risk and Resource Management

28. Workspaces

29. Takeaway 1 Think early about information architecture and provisioning

30. Takeaway 2 SharePoint gives you the tools to create a flexible provisioning without a lot of work

31. Takeaway 3 Consider increasing the effectiveness of your business processes by automating extensions into SharePoint

32. Control your Lifecycle!

33. Slide Title Please use this template for your slides ● Please DO NOT change the format of this template ● Please DO NOT use special formatting such as shadowing for code or images, or shadows behind boxes, etc. Please DO NOT use layers or slides because the text is unreadable when printed as handouts for students. ● Please send completed slides to erik@devconnections.com erik@devconnections.com ● Filename for slides should be: lastname_conference_sessionnum_sessiontitle.ppt Please zip all files before sending them. Include sample code for the attendee disk in a subfolder.

34. Your Feedback is Important Please fill out a session evaluation form drop it off at the conference registration desk. Thank you!