Skip to main content

A MOSSmosis Project

Go Search
Home
Atlanta
Orlando
Huntsville
GA K12
Blog
Limelight
  

MOSSmosis > A MOSSmosis Project
Importance of a Training Initiative with SharePoint 2007 Rollouts

In a press release issued June 6, 2008, SharePoint 2007 was stated to be “Microsoft’s fastest growing product ever.” It has been widely deployed throughout many companies and organizations. Typically, many IT departments spend a significant amount of their budgets on obtaining the latest and greatest software. It is no doubt that SharePoint is one of the latest and greatest software products in recent years. SharePoint investments have contributed to the acquisition of over 100 million licenses, resulting in more than $1 billion in sales for Microsoft. While offering innovative software solutions is a crucial element in the success of any IT department, an important factor in software implementation that is often overlooked and undervalued is the training initiative that should coincide with initial software rollout.

Organizations have seen a surge in Managers and IT Departments that often roll out software without the proper planning for end user training; thereby compromising the understanding, proper use, and capabilities of the software. These compromises are made in exchange for another “successful software implementation.” The question then becomes, what constitutes a “successful software implementation”? Is it the fact that software has only been made available to end users? Is it the fact that as long as IT understands how to utilize the product then there is no real urgency to share the knowledge with other company employees? Is it the fact that the software is simple enough or user-friendly enough that others will eventually catch on?

In my opinion, software, SharePoint included, is only as good as the users using it. If users have not been properly trained and introduced to the software from the beginning, then typically, the software either is not used as intended or it is not used to its potential. This could cause a myriad of problems such as:

·         Improper use of the software

·         More maintenance, administrative, and technical support from IT staff

·         Decreased productivity

·         Decreased cost effectiveness of the software, and

·         Unmanageable software solutions

These problems represent the exact opposite of what a “successful software implementation” should exemplify. Rather, in many cases, instead of considering a software rollout to be a “successful software implementation”, a more suitable embodiment would be a “successful software installation.”  And at the end of our extremely productive days, what good is a successful installation without anyone to take full advantage of the software’s capabilities and functionalities?

Listed below are possible company-wide training strategies for any SharePoint deployment:

·         Computer Based Training or E-learning – I recommend: http://www.codeplex.com/Wiki/View.aspx?ProjectName=SLK.

·         Training Manuals

·         Corporate, Instructor-led Classroom Training

·         Group Demonstrations

·         Screen Recordings (Screen Casts) for Online Demonstrations – I recommend the Camtasia Studio product.

It is important to assess what level of training is required for end users and structure the training classes accordingly. Some users may be more technologically advanced than other users or more familiar with the particular application. Therefore, a development of varying levels of the training documentation is warranted. In addition, with specific emphasis on SharePoint, it is not only important to train end users on how to use the software, it is equally important to determine how SharePoint can be made to work for company personnel. I like to think of this as performing a “SharePoint Readiness” evaluation. This involves presenting SharePoint capabilities and features to end users and gaining input from them as to how they could use this functionality within their everyday work routine or business process. This way, you can properly evaluate what features will be the most helpful to your users and ensure user adoption for your employees across your Enterprise.

Keep in mind that any training program should be scalable in scope. It should be designed in a way to reach users at an enterprise level and should also have a way to be incorporated into the existing training initiatives for new personnel.

So, the question remains, although SharePoint is an extraordinary tool in its own right, just how much of SharePoint’s features will be used regularly within any given organization? The responsibility lies on upper management working with IT Departments to establish, maintain, and enhance training initiatives to promote the need and value of software and application end-user training. So, let’s all share the point by providing necessary training for our end users in order to maximize software potential and cost effectiveness of our solutions.

Takesia Richardson, SharePoint Administrator
Contact Takesia Richardson





Limelight is a forum for local experts to share their knowledge and experience; the information provided is for general and educational purposes only.

The lost art of Capacity Planning : A prelude to a problem

So you have SharePoint 2007 loaded and you are ready to take over the world. You’ve started creating sites and people love the promise of what SharePoint provides to your Information Worker Community. Your Governance may not be perfect, but it’s a work in progress and you can move forward. You’ve knocked that whole Architecture problem out of the park. And those little problems like Security, Business Needs vs. Business Wants, and daily Administration work are already rolling. So what are you forgetting?

Somewhere in the middle of all this there are 2 major problems that need to be answered:
1. What does our Disaster Recovery Model look like?
2. Is our Portal Configured for the Company Growth for the Long Term?

These may seem like 2 very different problems, but like most issues that involve MOSS and WSS, everything is tied together. So let’s preview the first question and why you may need to investigate.

We all know that if your Big SharePoint fans are using it, one of the first questions that they ask is “Hey, is this getting backed up?” and “How often do you run backups?” These are pretty much no brainers. Your admin goes to Central Administration, kicks off the back up and you are set, right? Well, not exactly.

These same people who want to know “if” you are backing up their data want to know how long it will take to get it back. Whether you work from SLA’s, Service Level Agreements saying that a system can only be down for a certain amount of time or more informal time windows, you still need to know how long it will take to get your content back. This is where clever planning at the beginning of your project comes in to play.

SQL Server 2005 will tell you that your databases can grow to over 1 Terabyte. This sounds great, but if you apply this to your SharePoint Portal, you will slowly and surely create problems for yourself. The database sizing issue is one of the most troublesome and daunting issues surrounding SharePoint. Many will tell you that most SharePoint Databases should not be larger than 100-150 Gigabytes. This rule is usually circulated because it takes about 1 hour to restore 15G of SharePoint content. So if you have 100G of files out there on your MOSS Portal, you will easily need 4 hrs to get those files back.

This seems like a pretty normal problem and is easily avoidable. But then, think about creating and maintaining this content in other SharePoint Environments.  Chances are if you have SharePoint in-house, you will be doing some Customizations; Branding, SharePoint Development, or Out of the Box Customizations. And if not, you still need a place, outside of your Production Environment to make your changes, even if you just want to try out some new features. So you will at least need a Sand Box Environment, used for your SharePoint staff, and a Production Environment for your users to access. Or you may have more needs and require a 3 tiered approach with separate Development, Staging/QA, and Production Environments. The last thing that you want is to have users accessing the portal and their sites change from click to click because you want to try some make some Branding Issues on the fly. But regardless as to how many environments you have to maintain, you will need to update content in all of them, so your Data Recovery plans become even more important.

So obviously, we need a more manageable database size. But how do we do this in a logical fashion? And if we decide to address the Database issue, will we just invite different problems into the fray? Stick around and we’ll answer these 2 questions and many more as we walk through the importance of Capacity Planning.


Ron Jones, SharePoint Architect
Contact Ron Jones


 

 

 

Limelight is a forum for local experts to share their knowledge and experience; the information provided is for general and educational purposes only.

 

DataViews - Just a nibble...
Most organizations have a variety of systems and databases, in which business information is stored.  From homegrown applications to MRP and ERP systems, information can be scattered across platforms, standards, and geography, making automated integration of the information extremely difficult, if not seemingly impossible. 

Many companies resort to manual processes, such as copying and pasting data into complicated spreadsheets with extensive lookup functions.  Or they simply don’t take advantage of the disparate data, and consequently make poorer business decisions, operate at lower efficiency, and make lower profit.
 
There is a hidden gem in Microsoft Windows SharePoint Server 2007 and SharePoint Designer 2007 that can help!  You can use Data Views to get information from several sources, inside and outside of SharePoint; connect web parts to show related parent-child data from these various sources, all on the same portal page.  You can interact with the data using a form and web part connections.  And you can export the data views as reusable web parts, ready to be dropped onto any page in your SharePoint portal...all with little to no code.  This is what SharePoint is all about!
 
If you’ve wondered how to get data from various databases, web services, RSS feeds, XML files, etc. into your portal in real time and how to connect or combine the data in meaningful ways, DataViews are your answer.
 
David Frankland, Senior Engineer
Contact David Frankland
 
 


Limelight is a forum for local experts to share their knowledge and experience; the information provided is for general and educational purposes only.
 
In the Limelight
Limelight is a new feature of MOSSmosis that will spotlight SharePoint experts, industry leaders and other MOSSmosis members demonstrating the capabilities of SharePoint and its organizational impact.
 

 MOSSmosis Events Calendar

TitleDateStart TimeEnd TimeLocation
MOSSMOSIS : Going Green1/20/20094:30 PM6:30 PMFox Sports Grill, Atlantic Station, 261 19th Street, Atlanta, GA 30363

 Archives

Importance of a Training Initiative with SharePoint 2007 RolloutsAdministrator8/25/2008 11:42 AMTakesia Richardson0
The lost art of Capacity Planning : A prelude to a problemAdministrator8/22/2008 4:16 PMRon Jones0
DataViews - Just a nibble...Administrator8/4/2008 4:35 PMDavid Frankland0
In the LimelightAdministrator8/1/2008 4:14 PM0

 ‭(Hidden)‬ Admin Links