There are 13 ways to migrate a notes document to Sharepoint using Quest Notes Migrator for Sharepoint v 5.2, see these 13 ways out here : http://notes2sharepoint.org/archive/2009/06/11/thirteen-ways-to-migrate-a-document-to-sharepoint.aspx
Wednesday, July 22, 2009
Saturday, June 20, 2009
Notes to Sharepoint migration estimation model
Updates: I have recently enhanced the Estimation model which will help people come up with more effective Notes to SharePoint migration estimats. Click here to refer to and download the new version of Notes to SharePoint migration estimation model
=========================================================================
Its been a long time, since I am actually writing up on Lotus to Sharepoint migration.
A friend of mine called me up to ask for factors that one needs to consider in order to estimate a Lotus Notes to Sharepoint migration project.
I prepared an excel sheet and gave it to him which he found out to be immensely useful for estimating his sharepoint project, you can download the excel sheet at the end of the article, I request you to first read through the below mentioned guidelines:
a) Jot down the key features:
If you have 10 Lotus notes applications to be migrated, consider each application separately, jot down key features that you will have to develop for each of these application in the excel sheet.
b) Identify the Common features:
Find out features common to all applications, like for e.g:
Set-up Configuration of SharePoint environment server farms, Administration, Search User profiles synchronization etc
Set-up the Data migration environment, install third-party tools like Quest Notes Migrator for Sharepoint, test connection to Lotus Notes applications. (this can be a common activity for all the applications to be migrated)
You need to estimate for these common features only once for the entire migration project. In case you have many applications to estimate, record them only once in the excel sheet for correct estimates.
c) Effort estimates: Identify effort involved against each feature in terms of number of days that a person will take to develop it. This will depend upon the current skill level of your SharePoint resource, nature of requirement and past experience.
d) Actual effort involved: It is always good to find out whether you had correctly estimated the effort or not, this helps you to make better estimates the next time.
That is why my estimation sheet consists of another column to be entered, i.e the Actual effort in terms of days, this should be filled in as the application feature listed in the sheet gets completed and not when the application gets completed, as there are chances of wrong effort recordings.
The team should be disciplined enough to actually make proper time recordings during development activity.
e) Learning from the past estimates: Since, we are also capturing the actual time taken against the estimated time per activity, the variance % will help us whether we have a positive or a negative variance, this in turn will help us make better estimates and predict our team's productivity and output.
f) Buffer: Always add buffer to each item in your estimates, as you can't predict what can go wrong, a team member may leave the organization in the midway or may fall sick, without any knowledge transition, additional requirements or change requests may creep in, you never know...
A good buffer also helps during bidding, where the client bargains on the effort, you can actually cut some buffer time and still deliver.
So give a good solid buffer in your estimates, if you see my estimation worksheet, you will notice that I have added a lot of buffer for each feature that I am going to develop.
Download: Notes to Sharepoint migration Estimation sheet
=========================================================================
Its been a long time, since I am actually writing up on Lotus to Sharepoint migration.
A friend of mine called me up to ask for factors that one needs to consider in order to estimate a Lotus Notes to Sharepoint migration project.
I prepared an excel sheet and gave it to him which he found out to be immensely useful for estimating his sharepoint project, you can download the excel sheet at the end of the article, I request you to first read through the below mentioned guidelines:
a) Jot down the key features:
If you have 10 Lotus notes applications to be migrated, consider each application separately, jot down key features that you will have to develop for each of these application in the excel sheet.
b) Identify the Common features:
Find out features common to all applications, like for e.g:
Set-up Configuration of SharePoint environment server farms, Administration, Search User profiles synchronization etc
Set-up the Data migration environment, install third-party tools like Quest Notes Migrator for Sharepoint, test connection to Lotus Notes applications. (this can be a common activity for all the applications to be migrated)
You need to estimate for these common features only once for the entire migration project. In case you have many applications to estimate, record them only once in the excel sheet for correct estimates.
c) Effort estimates: Identify effort involved against each feature in terms of number of days that a person will take to develop it. This will depend upon the current skill level of your SharePoint resource, nature of requirement and past experience.
d) Actual effort involved: It is always good to find out whether you had correctly estimated the effort or not, this helps you to make better estimates the next time.
That is why my estimation sheet consists of another column to be entered, i.e the Actual effort in terms of days, this should be filled in as the application feature listed in the sheet gets completed and not when the application gets completed, as there are chances of wrong effort recordings.
The team should be disciplined enough to actually make proper time recordings during development activity.
e) Learning from the past estimates: Since, we are also capturing the actual time taken against the estimated time per activity, the variance % will help us whether we have a positive or a negative variance, this in turn will help us make better estimates and predict our team's productivity and output.
f) Buffer: Always add buffer to each item in your estimates, as you can't predict what can go wrong, a team member may leave the organization in the midway or may fall sick, without any knowledge transition, additional requirements or change requests may creep in, you never know...
A good buffer also helps during bidding, where the client bargains on the effort, you can actually cut some buffer time and still deliver.
So give a good solid buffer in your estimates, if you see my estimation worksheet, you will notice that I have added a lot of buffer for each feature that I am going to develop.
Download: Notes to Sharepoint migration Estimation sheet
Friday, May 1, 2009
Configure Sharepoint Server Farm Topology
There a several ways, a user can configure Sharepoint farm topology, for two primary reasons, i.e performance and availability.
The key to achieve both performance and availability is redundancy. By redundancy, i mean having identical server farms in order to swap between the farms either using network load balancing software or hardware such as a router or a switch box.
Here are some interesting topologies that one can implement for performance, availability and scalability.
a) Single Server farm: In this topology, you have everything under one box as explained in the diagram below:
b) Two server farm: This is the most recommended approach in general situations
Server 1 : Web Server and Search server
Server 2 : A dedicated SQL Content database server
c) Four server farm : This topology brings in some redundancy to the table.
Servers 1 and 2 are webservers with a search server configured with any one web server
Servers 3 and 4 are Clustered or mirrored content SQL database servers for high availability
d) Five Server Farm: This adds a middle tier layer.
Servers 1 and 2 are webservers
Server 3 : A dedicated search server
Servers 4 and 5 are Clustered or mirrored content SQL database servers for high availability
e) Three server farm: Choose the below mentioned topology when performance is more important than availability. 
If your focus is on availability as well, reduce the web server and add an additional SQL content database server as mentioned in the diagram below: 
Choose any of the above topology that best fits for your organizational need, scale/magnitude of your application, number of users and most importantly how critical is the availability of your sharepoint application for your business and end users.
Source: Technet
The key to achieve both performance and availability is redundancy. By redundancy, i mean having identical server farms in order to swap between the farms either using network load balancing software or hardware such as a router or a switch box.
Here are some interesting topologies that one can implement for performance, availability and scalability.
a) Single Server farm: In this topology, you have everything under one box as explained in the diagram below:
b) Two server farm: This is the most recommended approach in general situationsServer 1 : Web Server and Search server
Server 2 : A dedicated SQL Content database server
c) Four server farm : This topology brings in some redundancy to the table.Servers 1 and 2 are webservers with a search server configured with any one web server
Servers 3 and 4 are Clustered or mirrored content SQL database servers for high availability
d) Five Server Farm: This adds a middle tier layer.Servers 1 and 2 are webservers
Server 3 : A dedicated search server
Servers 4 and 5 are Clustered or mirrored content SQL database servers for high availability
e) Three server farm: Choose the below mentioned topology when performance is more important than availability. 
If your focus is on availability as well, reduce the web server and add an additional SQL content database server as mentioned in the diagram below: 
Choose any of the above topology that best fits for your organizational need, scale/magnitude of your application, number of users and most importantly how critical is the availability of your sharepoint application for your business and end users.Source: Technet
Thursday, April 2, 2009
Friday, March 27, 2009
The Art Of Making Effective Presentations : Steve Jobs Way
A few years back, I did some extensive research on Apple's CEO, Steve Jobs. I learnt a lot from the way he delivers his Key note speeches/presentations. Sharing my very popular slide deck from SlideShare...
Subscribe to:
Posts (Atom)