SharePoint Team Services at SVI

SharePoint Team Services

Overview:

SharePoint Team Websites provide a place on the Web where your team can communicate, share documents, and work together on a project. You can create a separate team Web site for every project your team is working on.  All team information is confidential.

Add information with ease.  You can contribute to the team Web site using nothing more than a Web browser. However, if you use a SharePoint Team Services-compatible client program, such as Microsoft Office XP, you can work seamlessly with the team Web site, saving documents to the site, editing team Web site documents in the client program, and moving information between client programs and your team Web site.

Share current data.  In your normal daily tasks, you create documents and data that are eventually used by other SVI personnel.  This information can be easily posted (saved) to a place in the SharePoint Team Website where other team members can view it.  As information becomes available, it is immediately available to others.  This capability alone will help SVI effectively cope with the ever-increasing flow of information and help ease future transitions within our school.  (See the rationale for the use of SharePoint in an email to Nancy Verheyden.)

Software availability.  SVI is currently licensed to use the SharePoint software.  It is available on the MS Office XP Pro with FrontPage CD.   It is proposed that the SharePoint Team Services be installed on the SVI Intranet site -- svi.sccd.ctc.edu -- which is secured for employees only.

Listed below are some hyperlinks that will help to clarify the advantages and use of SharePoint Team Services.  Suggestion:  See Demos and Examples first.

Product Documentation:

http://www.pointteam.com/_vti_bin/help/wsHome.htm

http://www.tcbinc.com/products_and_services/sharepoint.asp

http://www.triadconsulting.com/events/IAAP/2004_Convention/1_SharePoint_TeamSites/Windows%20SharePoint%20Team%20Site%20Guide.pdf

http://www.microsoft.com/resources/documentation/sts/2001/all/proddocs/en-us/admindoc/owsj00.mspx

Site Help:

http://www.pointteam.com/_vti_bin/help/wsHome.htm

Demos:

http://www.microsoft.com/sharepoint/teamservices/evaluation/demo/default.asp

Examples:

http://www.sharepointsample.com/samplesites.htm

Seminars on SharePoint

http://www.microsoft.com/seminar/shared/asp/view.asp?url=/Seminar/en/20010710TNT1-30/manifest.xml

http://www.microsoft.com/seminar/shared/asp/view.asp?url=/Seminar/en/20020531tnt1-54/manifest.xml

Software Requirements:

To run SharePoint Team Services, you must first install the following software on your server:

Hardware Requirements:

Hardware requirements vary depending on the operating system you use. The following table describes the hardware requirements for the supported operating systems.

Deployment:

http://www.microsoft.com/technet/prodtechnol/sppt/sharepnt/spdepgdp.mspx

http://www.windowsitpro.com/Article/ArticleID/26645/26645.html?Ad=1

Installing SharePoint Team Services:

http://www.microsoft.com/resources/documentation/sts/2001/all/proddocs/en-us/admindoc/owsd02.mspx

http://www.microsoft.com/technet/prodtechnol/sppt/sharepnt/default.mspx/proddocs/admindoc/ows000.asp

To install SharePoint Team Services Team Services from the FrontPage 2002 or Office XP versions containing FrontPage 2002:

1.       Insert the compact disc into the CD-ROM drive on your server.

2.       Navigate to the \SharePt directory.

3.       Double-click Setupse.exe.

Follow the steps in the Setup Wizard to install SharePoint Team Services.

SharePoint Administration (overall):

http://www.microsoft.com/resources/documentation/sts/2001/all/proddocs/en-us/admindoc/owsd02.mspx

http://www.vividoffice.com/projects/sp_legallarge1.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/spsdk11/CAML_Schema/spdbconOverview.asp

SharePoint Services 2003 -- the new version

http://www.microsoft.com/windowsserver2003/technologies/sharepoint/wss_overview.html

Applications for SharePoint 2003

http://www.microsoft.com/technet/prodtechnol/sppt/wssapps/default.mspx

Hi, Nancy

Your guidelines for the evaluation and deployment of software are genuinely appreciated... not only for its content, but for the fact that it is a "written" guideline. So often, changes in policies and procedures are passed on by word-of-mouth, and we hear about them only when we are exposed to them by necessity. And then, one person may remember a policy change differently than someone else.

Having an ongoing record of currently active policies and procedures would help all personnel in our school to work together for a common goal -- everyone would be playing from the same sheet of music. Explicitly written procedures reduce misinterpretation and help streamline the operations. A clear concept of our individual roles in our school's mission will help it to run more smoothly and efficiently.

Also consider this, our school and its activities are constantly changing. Its not only the computer technology that is changing at a phenomenal rate, but society as a whole. Our ability to change is central to our survival in the future. We must be able to react swiftly to the changes in our society and its workforce. Many changes that we encounter ripple through many different processes and procedures within our school. A central place where we all pertinent information is kept will enable us to make smooth transitions.

The difficulty in keeping a central repository of policies and procedures (in the form of a manual) is:

Consequently, even though the concept of a central repository is advantageous to an organization, its use may be too time-consuming and labor-intensive to justify its benefit.

Solution: SharePoint Team Services
With a SharePoint website, all personnel in the school who have authorization can access shared files, add information to a central repository or specialized directories for each department, and it's easy to use.

See the demonstration of the following topics:

The flow of information in our school is increasing -- sometimes, too rapidly. Immediate access to information will help SVI run more efficiently. Just think -- no hunting for the last email sent regarding Software Installation Guidelines. Just go to SVI > Computer Services > Software > Policies and find all documents pertaining to Installation Guidelines.

Information can be easily available to all faculty, staff, and administrators. Or, it can be restricted to certain people in the department. SharePoint is an easy way to get input from everyone involved in a project. It encourages dialogue with selected participants. Details can be worked out away from the meeting room. Changes can be collaborated and then published -- all in the same place... SharePoint.

Documenting change is not a job for just one person, but all of us. Having information at our fingertips makes our jobs easier. THINK OF THE POSSIBILITIES...

Again, thanks for your guidelines.
Dennis