SharePoint implementation – Some key issues to consider#1 – Estimating and keeping track of storage

We at Talman just recently (almost) finished implementing our first phase of SharePoint implementation, which was largely related to collaboration (specially documentation and other knowledge base related information) across various divisions at Talman. Being the Project manager and implementer for the whole project (which lasted more than 8 months…and still going on), I would want to share some of the key issues which would need good thinking and planning while doing similar project.

With documents and information forming the key elements in divisional collaboration, estimating and planning for the storage needs was very critical. We initially failed to estimate the storage needs as we lacked awareness / information on how much documents / information existed on various servers, desktops and other filing systems. We ran out of storage space twice within first 6 months. Even with storage costs no longer at the premiums of the past, storage is still not free. It can, in fact, get quite expensive. And in this age of videos, pod-casts and meeting / training recordings, it’s exceedingly easy to fill every gigabyte of free space. As sites proliferate – and SharePoint sites have a strong tendency to do just that – demands for more storage can become a concern (key issues being administration and cost).

Some of the key issues to manage as a SharePoint administrator:

  • Be able to monitor storage use
  • Set quotas for individual users, sites, and sites collections
  • Have the ability to automatically warn users when they are reaching their limits
  • Ability to quickly allocate additional storage space when it is truly required

Being able to track storage is essential to being able to adequately and sensibly plan for current and future needs.

During the two instance (where in we ran out of storage capacity without any warning from SharePoint), our inability to estimate and plan as above resulted in:

  • A immediate scare when SharePoint sites failed to respond (What happened to our doco? Will we have to do everything all over again? Can’t access this and that? and……)
  • Team members getting frustrated for not being able to store documents and create newer versions of their existing documents
  • Team members loosing faith in the SharePoint collaboration system
  • Disruption in the system and processes we had agreed to follow to keep the collaboration going

All the above would immediately raise question why not to plan what goes on SharePoint and what gets left out???? That is the second issue to consider… in my next post..

 

July 25, 2008 · Rahul Desai · No Comments
Posted in: SharePoint, Talman news

Worlds oldest blogger dies – CIOL News Reports

Interesting story….

Worlds oldest blogger dies – CIOL News Reports

July 14, 2008 · Rahul Desai · No Comments
Posted in: General

Microsoft India MD joins HP – Software & Services-News-Indiatimes – Infotech

Microsoft India MD joins HP – Software & Services-News-Indiatimes – Infotech

 

Technorati Tags:

June 7, 2008 · Rahul Desai · No Comments
Posted in: General

Microsoft shuts down another Live site- Software & Services-News-Indiatimes – Infotech

Interesting and something uncommon…

Microsoft shuts down another Live site- Software & Services-News-Indiatimes – Infotech

Technorati Tags:

June 7, 2008 · Rahul Desai · No Comments
Posted in: General

A good article on…..Blockers and How To Deal With Them

Working with multi cultural team members and cosmopolitan work environments for all this years, I have experienced blockers many times over the years (I am sure everyone has). Grant Holliday has written a nice post on “BLOCKERS” and how to deal with them, here is the link.

The post is not only good in identifying a blocker and dealing with the blocker, it also identifies what you should try and avoid if you do not want to be called one.

Adding one more point to his list of definitions of a “can’t do-er” (aka blocker)…(Please do read the other 3 here before reading further):

Most blockers put themselves ahead of the whole team, the enterprise goals / targets. For most of the blockers “Me, myself comes first instead of us, ourselves”.

March 14, 2008 · Rahul Desai · No Comments
Posted in: General, Project Management

Some strategies for good impact performance at work

Do you ever wonder why some people have a better work ethic than others?  A good work ethic means being responsible, dependable, accountable and taking initiative.  High-quality work ethics vibrate through the organization.  And we all notice when it’s missing from a environment! As a project manager, it is good to lead by example, have some strong ethic in place and pass on the same to your team members.

Some good thoughts / suggestions (which I normally try to follow) to build a strong work ethic:

  • Take ownership of your position.
  • Do what you say you are going to do. 
  • Be accountable for your performance. 
  • Learn your job.
  • Then consider taking on more responsibility within your department.
  • Others count on you. 
  • Be dependable.
  • Show up and be on time. 
  • Be conscious of your attendance.
  • Keep personal business at work to a minimum.
  • Do what it takes to make your manager successful.

Some suggestions for personal growth:

  • Think strategic and long term.
  • Avoid distractions that take your golden work time. 
  • Stay focused.
  • Stay current in your industry.
  • Avoid burnout by pacing yourself over a period of time.

Reputations are formed over time.  You can start moving towards top from where you are today.

 

March 10, 2008 · Rahul Desai · No Comments
Posted in: Personal, Project Management

Facebook founder is world’s youngest billionaire-USA-World-The Times of India

 

Facebook founder is world’s youngest billionaire-USA-World-The Times of India

 

March 6, 2008 · Rahul Desai · No Comments
Posted in: General

Who exactly cut your Internet?

Interesting story on India times…..link as below:

http://infotech.indiatimes.com/articleshow/2767152.cms 

 

Technorati Tags: ,

February 9, 2008 · Rahul Desai · No Comments
Posted in: General

Overestimate or Underestimate?

While trying to provide estimate for a new requirement / project, it is always an enigma whether to overestimate the requirement and face the risk of not getting the project or underestimating the requirement to get the project.

My thoughts, don’t intentionally underestimate (to get the work). The outcome and the penalty for underestimation is more severe than the result / outcome for overestimation.

From project management view, the biggest outcomes of intentionally underestimating requirements are:

  • Reduced effectiveness of project plans
  • Reduced chance of on-time completion
  • Losses involved in terms of cost
  • Disturbed Client relations or lack of Client satisfaction
  • Loss of overall goodwill

Time spent on proper estimating helps in:

  • Recognizing a mismatch between the requirement / project’s business target and a requirement / project’s estimate
  • Gives you chance to justify (to the client) the cost of the project (why is it on the higher / lower side?)
  • Assessing valuable risk information that the project might not be successful
  • Take corrective action early, when it can do some good

It also helps the over all project with:

  • Improved status visibility
  • Higher quality
  • Increased credibility for the development / support team (and of course the company)
  • Clarity on various risks involved (at various stage)

The ideal goal should be to address concerns about overestimation through proper planning and control, not by biasing your estimates (just to make the client happy initially) . Quiet a few project managers don’t like spending time on proper planning and estimate and most of them do not have a standard method to do so….

Quote of the day:
God is not dead but alive and well and working on a much less ambitious project. – Anonymous

 

December 21, 2007 · Rahul Desai · No Comments
Posted in: Project Management, Software Engineering

Think before you Blog…..

Think Before You Blog

Technorati Tags:

December 16, 2007 · Rahul Desai · No Comments
Posted in: General