SharePoint Thinking IV

The following are some items to consider and think about in regard to SharePoint:

1)      To take SharePoint ideas to the next level, find people to help stretch those thoughts.

2)      Be aware to have the right people for your SharePoint project so you obtain the right result.

3)      Utilize your SharePoint ideas in the right environment, with the right technologies.

4)      The SharePoint ideas power comes when the right way and place to implement is obtained.

5)      Find the right medium to display and discuss your SharePoint idea wisdom.

View Video:

SharePoint Thinking III

The following are some items to consider and think about in regard to SharePoint:

1)      Continue to help users improve their SharePoint knowledge via quick guides, ad-hoc one: one training, videos, etc.

2)      Continue to make sure that users are utilizing SharePoint for goal setting.

3)      SharePoint is always changing with new features and functionality so always changing is part of the SharePoint mantra.

4)      Evangelize communication aspects of SharePoint to users (blogs, wikis, etc.).

5)      Find a quiet spot, whereas the evangelizer of SharePoint, one can think about what the environment needs to be successful.

View Video:

SharePoint Thinking II

The following are some items to consider and think about in regard to SharePoint:

1)      Take a basic SharePoint project and obtain the needed data to implement but consider several options, perspectives and ideas in the final project.

2)      Realize that SharePoint is a change for many users and requires that they are able to change to be rewarded by the change.

3)      Prepare to succeed by building beliefs in what SharePoint can do.

4)      Being excited about the SharePoint product will lead to users being confident and committed to the product.

5)      Having a good mood and energy about the SharePoint technology stack will drive users attitude.

 

View Video:

SharePoint Thinking I

The following are some items to consider and think about in regard to SharePoint:

1)      Those users who have a negative perception of SharePoint – should be set to be positive by shifting them to understand that SharePoint can solve their problems.

2)      Evangelize and make it clear that SharePoint provides results – when users change their thinking.

3)      Be sure to listen to all users ideas.

4)      Be consistent in getting back to users in regard to their needs.

5)      Break requests into the proper pieces so they can be deployed over time and include proper review, testing and changes.

 

View Video:

SharePoint Agile Story Template

When using Agile and SharePoint, it’s important to utilize a simple template for a story. By having a template, it will help the development process of what is actually needed to be built. As an example, a template is as such:

FOR <customers>

WHO <need a piece of functionality>

THE <product>

IS A <product category>

THAT <key benefit>

UNLIKE <competition, alternative>

OUR PRODUCT <differentiating statement>

Filled in, this could be as such:

FOR <human resources department>

WHO <need a web-part to display frequently asked questions>

THE <frequently asked questions knowledgebase>

IS A <dropdown of choices of key departments>

THAT <are listed by category>

UNLIKE <the information technology web-part frequently asked questions>

OUR PRODUCT <will allow users ti pick the proper category then allow a response to the requestor via e-mail>

SharePoint Web Content Management

The following are some key steps to utilize in regard to web content management:

Step 1 – Create content with proper page layouts and image resources.

Step 2 – Have content approved/rejected via an approval process.

Step 3 – Schedule content as needed.

Step 4 – Have a start date and end date for published content. Once content is expired, it should be archived.

View Video:

5 Step Approach to a Metadata – Archive Policy

The following are the 5 steps needed to create a metadata based archive policy:

•      1) Create Content Syndication Content Types that originate from a Content Type Hub. These are housed in an Archive web application. Since these Archive Content Types are syndicated content types it means they can be used on different web applications, and site collections.

•      2) Each site created so that one can leverage an archive policy needs to have content types created and named appropriately:
Example:
Name of Site 1-Year
Name of Site 2-Year
Name of Site 3-Year

•      3) For each content type - create an Information Policy to a Content Type.

•      4) Make sure that the content organizer site feature is turned on so that metadata based rules that move content submitted to a library to the proper location are in place.

•      5) Set-up a workflow then for each site so that when a file meets the policy based on the content type, the site owner gets an e-mail:
Example: This document - [%Current Item:Name%] - has been moved to the Archive document library due to the expiration policy. Click here to view your files and return them from the archive site to your proper site.

View Video: