SharePoint User Group UK

Share the knowledge!

Welcome to SharePoint User Group UK Sign in | Join | Help
in
Home Blogs Forums Photos Files Roller

Developers vs Consultants vs Architects

Last post 04-25-2008, 11:46 AM by dhunter. 2 replies.
Sort Posts: Previous Next
  •  03-29-2008, 11:01 AM 9396

    Developers vs Consultants vs Architects

    What are your opinions on what makes a person a SharePoint Developer, a SharePoint Consultant, or a SharePoint Architect?

    I personally think there is quite a lot of overlap, and many sharepoint specialists are in the position to call themselves developers, consultants, AND architects. But then again, it's probably mainly a matter of definition.

    I would like to hear your opinions on this.

    Thanks,

    Jaap

  •  03-31-2008, 9:21 AM 9404 in reply to 9396

    Re: Developers vs Consultants vs Architects

    Personally, I would see a Developer and an Architect being a specialist in that particular field. A Consultant perhaps needs a more overview approach and the ability to draw on knowledge of development and architecture, rather than understanding to the nth degree.

    That said, because of the nature of how Moss 2007 has grown in demand since the Beta, I think you'll find that a lot of consultants have worn all 3 hats at various times during the last 18 months.

    Paul.


    www.myfatblog.co.uk
    MCTS: WSS 3.0
    MCTS: MOSS 2007
  •  04-25-2008, 11:46 AM 10221 in reply to 9404

    Re: Developers vs Consultants vs Architects

    I've worked for two Microsoft Gold Partners over the past 8 years, these roles with typical Gold Partners are seen differently as Paul described.

    A SharePoint Developer would be someone who is skilled in ASP.NET development, has experience and competence in creating web parts, features, site definitions etc.  They don't typically take part in the requirements analysis and design.

    A SharePoint Architect would be involved in the early stages of a client engagement.  They would discuss requirements, recommend architecture, design the solution.  Sometimes their role will end here or will be made into a more supervisory role, overseeing the project and sometimes some architects are more hands on (depends on the person).  An architect would be responsible for over seeing a team of developers.

    A SharePoint Consultant should be skilled in both roles, they should be able to gather requirements, design the solution, deliver the proposed solution etc.  They are typically "client facing", were as a developer isn't.

    My role as a Senior Consultant is all 3 merged together.

    In summary if I was resourcing a project and required the following:

    • Only for someone capable of delivering webparts and other components for SharePoint.  I would look for a developer.
    • Someone capable of the full project lifecycle with strong design skills.  I would look for an experienced consultant or an Architect.

    Dave


    My SharePoint Blog www.davehunter.co.uk/blog
View as RSS news feed in XML
Powered by Community Server, by Telligent Systems