Sow, as many as yours, my colleagues and me we have a lot of projects in SharePoint but what to do if you are a junior?  If you’re “description” is not like on that link, so you’re a junior http://www.wisegeek.com/what-is-a-senior-consultant.htm

I’m going to take a relevant case, in fact a real case to explain how to successfully end the case. I had a client who only had 1 web application with only one site collection with only one database (40GB)

Environment: Microsoft SharePoint 2003 | Microsoft SQL Server

The case was to migrate all content from 2003 to 2010. I will now explain how to made a “great” project in 7 steps..

#1 ANALYSE

Try to understand what the client wants. The client in most of the case will say I want a “working site” and that it. As far I know you will analyze.

• See if any service is configured
  • Search Service
  • iFilter
  • Versioning
  • Custom Master Pages

Write everything on a Paper or do like me, draw it.. Take a big paper and write step by step what you need and what you will configure. When you finished go “talk” with the client and see if you did not forget anything.

#2 SEARCH

When you’re analyze process is finished check you’re URL’S, you’re senior colleges and ask for help. See if they made something like that. Check on google..

I found pretty interesting information like “You cannot upgrade directly from Windows SharePoint Services 2.0 to Microsoft SharePoint Foundation 2010.

The changes between versions are too great, and the hardware requirements differ so much between versions that a direct, in-place upgrade is not possible or supported. You can, however, perform a series of database attach upgrades to first upgrade your content to Windows SharePoint Services 3.0 and then to SharePoint Foundation 2010. This article describes the process of performing this double-database attach upgrade.

Or very good links like: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?PageType=4&ListId={72C1C85B-1D2D-4A4A-90DE-CA74A7808184}&pID=441 they explain you step by step how to migrate, in an official way.

#3 POC

After collecting all the information that you need, you can begin with a POC ( proof of principle is a realization of a certain method or idea(s) to demonstrate its feasibility or a demonstration in principle, whose purpose is to verify that some concept or theory that has the potential of being used. A proof-of-concept is usually small and may or may not be complete)

#4 TALK

Please talk! Don’t be afraid, go to your business unit manager or you’re team leader and ask if you’re POC is good enough for what the client is asking.. You’re superiors will never criticize now because you’re asking something.  But the will be upset if you don’t ask or show anything.

#5 SEARCH

Again, searching. I’m still hearing “why?”. Pretty simple. There will be all-time somebody who will ask you to do something more or something that you don’t know. Again the answer is “Google “. This is a critical issue, you will continue till everyone is “ok” with your POC before showing to client.

#6 EXECUTE

When the client sees that you’re POC is like they want. You can begin implementing everything that you did on your POC and development environment.

Be careful for these points:  

• Plan step by step MS project is a great tool ( example below )
  • 1h for SQL installation ( 7h remaining of 8h)
  • 2h SharePoint installation ( 5h remaining of 8h )
  • … 

• Provide extra time for “errors” that can additional come
• Made snapshots if you have a fatal error, don’t want to be the hero for searching an impossible answer
• If you are with many people, take leadership if you can..
• Give the client “response time” for evaluating and critiquing your deployment.
• …

#7 DOCUMENTS

Ahhh documents.. Provide a STEP by STEP document to the client. There is only 1 golden rule “how more pages how better”..

I hope it will help you to gain experience in your future SharePoint Projects..