User:Morningrain777/sandbox

Table of Content Steps to create a new Wiki library for your team
 * What is Wiki, Sharepoint Wiki Library and CIO Operaions Team Wiki?
 * Chicago Protest.jpgtives
 * Audience
 * Scopes
 * Guiding Principles
 * Steps to create a Wiki library, add new pages and update existing content

Steps to add new pages for your Wiki library

Steps to update Wiki content

Team Roles and Responsibilities

Permission and Support

Appendix

o   FAQ

o   Sample Ops Team Wiki Site screen capture

o   CIO Operations Wiki SME Support

What is Wiki, Sharepoint Wiki Library and CIO Operations Team Wiki?

CIO Operations Teams need a tool to capture all documentations needed to do their day to day job. The tool must be easy to create, update, navigate and search. The tool is called an “Operations Team Wiki” (or “Operations Wiki” for short).

A Wiki is a site that is designed for groups of people to quickly capture and share ideas by creating simple pages and linking them together. After someone creates a page, another team member can add more content, edit the content, or add supporting links. The community of content owners helps to ensure the accuracy and relevance of the content. Wikis continue to evolve as people add and revise information.

A Wiki Library (or Wiki for short) is a native Sharepoint application that can be created to allow content owners to create/edit pages in the browser. Wiki pages can contain formatted text, pictures, tables, hyperlinks and links to other wiki pages. It is a very powerful tool to use to collect, share and communicate ideas and knowledge. In comparison with other page types that can also be created/updated on the Sharepoint, for example, Publishing pages or web part pages, Wiki pages are more flexible and customizable, they are easy to create and update without requiring any third party tool (ie. Sharepoint Designer). It is recommended that the CIO Operations Team Wiki be created by using the Wiki Lbrary capability on the Sharepont Platform.

Objectives

·        The objective of a CIO Operations Wiki site is to provide a system of records for all CIO Operations (aka Ops) material.

·        Enable Operations team members to find up-to-date functional and technical specifications for their applications or services.

·        This site governance section describes how the CIO Operations Team Wiki should be used and maintained.

Audience

·        CIO Operations Wiki is inteneded to be used by anyone working on the Operations support and maintenance. Initiatve team members may also find useful and up to date information on the applications and services that the CIO Operations team provide to support.

·        A "Wiki Core Team" may also exist, and that team provides permissions, support and makes site updates. See more on roles and responsibilities below.

Scopes

·        The Operations Wiki should contain all application specific materials needed to support an application or a service.

·        The scope of the CIO Operations Wiki does NOT include other Analyze phase or Accenture Delivery Methods deliverables.

Guidelines for deciding what material goes in the Wiki versus the Sharepoint Dpcument Library:

·        The CIO Operations Wiki is for final documentation only.

·        All team deliverables should be posted on the SharePoint Document Library site for storage. You may post links on the CIO Operations Wiki to reference the deliverables, but all working documents should remain in SharePoint Document Library.

·        Some decision criteria:

o   Does the Ops team need to access the material to do their job?

§ If Ops team does not need access the material for their day to day job, then it should not be stored on the Operations Wiki.

o   Is the material changing from release to release or frequently?

§ If the material is changing frequently, or not in the final state, it should not be stored on the Operations Wiki.

o   Some potential Operations Wiki pages including:

§ Ops team test strategy

§ Ops team test approach

§ Tools installation instruction (not subject to change from release to release)

§ Ops Environment etc.

Given project needs are different, the above are the general guidelines, Ops project teams need to use their own discretion to decide what content goes to Operations Wiki site vs. the traditional SharePoint Document Library.

Guiding Principles:

·        Content must be reviewed and updated on a regular basis (ie. every six month).

·        Posting items to the Operations Wiki site should be used as an opportunity to review, enhance, and streamline existing processes.

·        Content should be developed to exist in a stand-alone format, meaning a reader of the content can understand it without someone explaining it.

·        Leadership should champion the Operations Wiki site to make it part of the collective mindset: “When you don’t know what do to, go the CIO Operations Wiki. If the content doesn’t exist, pull the right people together and draft the content”.

·        Managing Directors (MDs) and Senior Managers (SMs) will not review new content that is not on the CIO Operations Wiki.