<script type="text/javascript">
aspnetForm.encoding = "multipart/form-data";
</script>
It has been a short while since the first part of the SharePoint Projects series, I have recently moved house and also found out that I am going to be a dad, so things have been fairly hectic to say the least. Now onto the good stuff: SharePoint project implementation. So far you have spent considerable time conducting a design/architecture phase with your client you both should have a 90% understanding of how the final solution is going to look. Due to the nature of business there will quiet often be ‘changes’ to the project, these will need to be gauged in relation to effort and charged accordingly. I will split this post into multiple headings to make referencing and reading easier:
Scope Variations
If you ever encounter a client that does not vary from the scope at all, continue doing projects for this client as these are the best kind of clients you can find. Indecisiveness is unfortunately part of human behaviour and there is not a lot that can be done about it. Business decisions may be varied by internal change and occasional bureaucratic power struggles and therefore can have negative impacts on your project. A vital project management skill is gauging when to and not to charge for these scope variations. Examples:
At the end of the day the decision is up to you. Just remember to be ethical with all your decisions you make.
Contingency
A strategy to cope with fussy clients and also an important risk reduction strategy is to incorporate a ‘buffer’ or contingency into quoted hours. The old rule I learnt with information technology from one of my old university professors was that you would estimate the time it would take to complete a particular task and you triple it. For instance if you believe it would take you 30 minutes to configure search indexing and crawls it is probably a good idea to quote 1.5 hours instead. Now this is obviously a fairly generalized rule and by now you should have a fair understanding of how long a task may take, it is always a good idea to add some kind of buffer into your quotes. In a later part to this series I will go through some of my usual estimates for both WSS 3.0 and MOSS deployments.
Automated Scripts vs Manual Deployment
Scripting is something I have recently embraced and find it to be a fairly powerful ally. There is a fairly rational relationship between viability and deployment size I find. For instance if you have a single or twin server farm with WSS 3.0 or MOSS 2007 it may not always be the best option to deploy using scripts. On the other hand if you have a larger multi user farm with multiple environments for development, testing and production it may be viable to use scripts to deploy your environments. Bear in mind that scripts and associated documentation would count as a deliverable.
Governance
SharePoint farm methodology would denote that it is often a requirement to deploy corresponding farm environments for development, test and production. This methodology is relevant when there is going to be significant modification or development conducted to the solution. As mentioned before this development would be best suited in a separate project, however it must be planned for during your solution architecture.
Development Environment
The configuration of this farm is debatable. Some people will argue that this environment should mirror production as much as possible, however I believe that you would only need to replicate ‘hops’ in your production. By that I mean if you have a production which consists of 2 app servers, 3 web front ends and a database server, the development environment corresponding to this production environment would ideally be 1 app server, 1 web front end and a database server. It is not uncommon to use a single server development environment and any environmental issues that may result from this will be exposed within the test environment.
Test Environment
The test environment should be an exact mirror of the production environment. Data should also be replicated from production to test on a regular basis.
Production Environment
This is your live environment. No development is to be conducted at this level.
Implementation Stages
MOSS Only Configuration
There are occasionally other configuration stages required depending on architecture of solution.
To be continued…
For both WSS and MOSS I like to use the least privileged account methodology for all my deployments. This is considered Microsoft best Practice.
Account | Usage |
| SP_Admin | SharePoint set up account, used to install SharePoint. Local administrator on web front end. DB Creator on SQL. |
| SP_Farm | SharePoint Farm service account. DB Creator and Security Admin on SQL. Also used as the Central Admin application pool identity. |
| SP_WssSearch | WSS search Account. |
| SP_MossSearch | MOSS Search service Account. |
| SP_Content | SharePoint Content Crawl Account. |
| SP_Profile | User profile import account. |
| SP_SSPAppPool | Application pool identity for Shared Services Provider |
| SP_PortalAppPool | Application pool identity for Portal web application. |
| SP_MyAppPool | Application pool identity for Mysites web application. |
| SP_Excel | Excel Services service account. |
| SP_SSO | Single Sign On service account. |
Above is a general guide of what I use when deploying WSS and MOSS environments. Some of the above accounts are not needed for WSS.
Service Pack 2 for Windows SharePoint Services 3.0, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en
Service Pack 2 for Office SharePoint Server 2007, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
I will be back next week to post the next part to this series: Implementation.
