Roles in SharePoint Projects (Response to OfficeOverEasy), Part II of IV

Traditional Projects and Project Management

The difference between SharePoint and other projects is basically that everyone thinks when you are doing sharepoint all you need to do is develop c#/.NET. The problem is that SharePoint is more than that. You get in contact with so many different things and concepts (Identity Management (AD), Aspect Orientation (Security, Logging), Abstraction Layers, Performance Considerations (custom vs. ootb components/ controls, legacy application integration), c#, aspx, jscript, silverlight, sql server, database abstraction (entity framework, odbc, bdc and similar) and then of course when you try to acquire knowledge on all of these technologies and concepts you might overlook what can be done with SharePoint ootb. A partner of mine really knows a lot about designing solutions with the content query web part, filters, content editor webparts and javascript. We usually discuss and I learn more about what he does. Only when he says he doesn’t know how to do something we decide to go code!

Then you have the classic discussion: is a project manager a people-leader, a controller or a highly skilled and organized consultant that can also do project work? Usually you can classify projects based on the duration and the number of persons who work in it. That should basically be the criteria to decide what is needed. I like the idea of a project manager, who is kind of an escalation engineer and decides on the facts, priorities and scope and doesn’t know too much about the underlying technology. But he needs to have somebody to rely on or this guy will get screwed if he doesn’t have great people-skills – let’s face it, there are less and less people with outstanding people-skills, right? 😉

I also believe that it is important to have people in different roles and not have too many roles for a single person. The workload will usually overwhelm that one person and he will need to prioritize one role over the other. If you want constructive discussions and subsequently good decisions, get strong-willed people in your project and make them discuss until they get a consensus in place. It will not only benefit the project but also the persons involved as it creates a different type of environment that will help them train better on the job. It’s kind of like inspiration.


One Response to Roles in SharePoint Projects (Response to OfficeOverEasy), Part II of IV

  1. Your style is very unique in comparison to other people I have read stuff from.

    Many thanks for posting when you’ve got the opportunity, Guess I’ll just book mark this web site.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: