Home
About Us
Advertise
Printable version
Use pilot projects to gauge success
By Eric Riz
June 19, 2012 —
(Page 1 of 2)
I’m often asked for advice on how to ensure that a SharePoint project is completed and implemented successfully. Following some pointed questions, I provide some tactics to try, but the reality is that there is no single tip or strategy that will provide such an insurance policy.
Even with the most finely tuned adoption or governance plan, your project can still fail for a variety of reasons: mismanaged requirements, development errors or simply the wrong training. It takes a perfect storm in order to get everything rolled out and implemented correctly. Though it’s impossible to identify just one item that can save you from such issues, a pilot project is a great way to measure twice and cut once with your rollout of SharePoint.
A pilot project is a soft launch that puts your deliverables into the hands of a subset of your user community. Following a shortened cycle of design, development and delivery, a pilot runs for a defined period of time in order to review and obtain feedback on the rolled-out functionality. Once a corporate perspective has been obtained on the rollout, the project team can then begin developing for a wider deployment to the business.
Possibly the best advice I can give is to take your pilot project as seriously as you would a full deployment. Staff your project with A-Team players and make sure that everyone who needs to know about the project does. What you are limiting is not functionality, but the distribution of the product in order to get the feedback you need to ensure corporate rollout success.
Once you have made the decision to roll out a pilot, you must next decide who will be involved in it. Depending on who brought SharePoint into the organization, this may be an easy choice. For example, if HR is responsible for SharePoint coming into the business, they are also an easy choice to be in the pilot. They will provide strong, user-defined requirements, honest feedback, and a keen interest in its long-term success. If IT is responsible for SharePoint, look for business units or user groups that will provide the same strong requirements driven by business needs. You can also start backwards when defining your pilot group by choosing a business problem that you know SharePoint can solve, then define which user group can best be affected by its deployment.
Next Page
Pages
1
2
Share this link:
https://sptechweb.com/link/36726
Related Articles
Learn to use SharePoint Project Items
SPIs can help you create a streamlined solution for your SharePoint environment
Use the SharePoint 2010 theme engine
With a little effort, you can gain complete mastery over the look and feel of your SharePoint sites
Defining SharePoint taxonomy for work management success
It's important to get a solid taxonomy in order to fulfill business objectives in SharePoint
Add comment
Name*
Email*
Country
United States
Canada
Afghanistan
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua & Barbuda
Antilles, Netherlands
Arabia, Saudi
Argentina
Armenia
Aruba
Australia
Austria
Azerbaijan
Bahamas, The
Bahrain
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bermuda
Bhutan
Bolivia
Bosnia and Herzegovina
Botswana
Brazil
British Virgin Islands
Brunei Darussalam
Bulgaria
Burkina Faso
Burundi
Cambodia
Cameroon
Cape Verde
Cayman Islands
Central African Republic
Chad
Chile
China
Christmas Island
Cocos (Keeling) Islands
Colombia
Comoros
Congo
Cook Islands
Costa Rica
Cote D'Ivoire
Croatia
Cuba
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
East Timor (Timor-Leste)
Ecuador
Egypt
El Salvador
Equatorial Guinea
Eritrea
Estonia
Ethiopia
Falkland Islands (Malvinas)
Faroe Islands
Fiji
Finland
France
French Guiana
French Polynesia
Gabon
Gambia, the
Georgia
Germany
Ghana
Gibraltar
Greece
Greenland
Grenada
Guadeloupe
Guam
Guatemala
Guernsey
Guinea
Guinea-Bissau
Guinea, Equatorial
Guyana
Haiti
Holland (see Netherlands)
Honduras
Hong Kong, (China)
Hungary
Iceland
India
Indonesia
Iran, Islamic Republic of
Iraq
Ireland
Israel
Italy
Jamaica
Japan
Jordan
Kazakhstan
Kenya
Kiribati
Korea (North)
Korea (South)
Kuwait
Kyrgyzstan
Laos
Latvia
Lebanon
Lesotho
Liberia
Libya
Liechtenstein
Lithuania
Luxembourg
Macao, (China)
Macedonia, TFYR
Madagascar
Malawi
Malaysia
Maldives
Mali
Malta
Marshall Islands
Martinique
Mauritania
Mauritius
Mayotte
Mexico
Micronesia, Federated States of
Moldova, Republic of
Monaco
Mongolia
Montenegro
Montserrat
Morocco
Mozambique
Myanmar
Namibia
Nauru
Nepal
Netherlands
Netherlands Antilles
New Caledonia
New Zealand
Nicaragua
Niger
Nigeria
Niue
Norfolk Island
Northern Mariana Islands
Norway
Oman
Pakistan
Palau
Palestinian Territory
Panama
Papua New Guinea
Paraguay
Peru
Philippines
Poland
Portugal
Puerto Rico
Qatar
Reunion
Romania
Russia (Russian Federation)
Rwanda
Saint Helena
Saint Kitts and Nevis
Saint Lucia
Saint Pierre and Miquelon
Saint Vincent and the Grenadines
Samoa
San Marino
Sao Tome and Principe
Saudi Arabia
Senegal
Serbia & Montenegro
Seychelles
Sierra Leone
Singapore
Slovakia
Slovenia
Solomon Islands
Somalia
South Africa
Spain
Sri Lanka
Sudan
Suriname
Swaziland
Sweden
Switzerland
Syrian Arab Republic
Taiwan
Tajikistan
Tanzania, United Republic of
Thailand
Timor-Leste (East Timor)
Togo
Tokelau
Tonga
Trinidad & Tobago
Tunisia
Turkey
Turkmenistan
Turks and Caicos Islands
Tuvalu
Uganda
Ukraine
United Arab Emirates
United Kingdom
Uruguay
Uzbekistan
Vanuatu
Vatican City State (Holy See)
Venezuela
VietNam
Virgin Islands, British
Virgin Islands, U.S.
Wallis and Futuna
Western Sahara
Yemen
Zambia
Zanzibar
Zimbabwe
[Not specified]
Compose