The "SharePoint project scope" is all of the things that must be produced to complete a SharePoint project. These 'things' are called deliverables and you need to describe them in depth as early in the SharePoint project as possible, so everyone knows what needs to be produced. Take these 5 Steps to scope your SharePoint projects:
Step 1: Set the Direction
Start off by setting the direction for the SharePoint project. Do you have an agreed SharePoint project Vision, Objectives and Timeframes? Are they specified in depth and has your customer agreed to them? Does everyone in the SharePoint project team truly understand them and why they are important? Only by fixing the SharePoint project direction can you truly fix the SharePoint project scope.
Step 2: Scope Workshops
The best way to get buy-in to your SharePoint project scope is to get all of the relevant stakeholders to help you define it. So get your SharePoint project sponsor, customer and other stakeholders in a room and run a workshop to identify the scope. What you want from them is an agreed set of major deliverables to be produced by the SharePoint project. You also want to know "what's out of scope".
Run the workshop by asking each stakeholder for a list of the deliverables they expect the SharePoint project team to deliver. Take the full list of deliverables generated in the workshop and get them to agree on what's mandatory and what's optional. Then ask them to prioritize the list, so you know what has to be delivered first.
Step 3: Fleshing it out
You now have an agreed list of deliverables. But it's still not enough. You need to define each deliverable in depth. Work with the relevant people in your business to describe how each deliverable will look and feel, how it would operate and how it would be supported etc. Your goal here is to make it so specific that your customer cannot state later in the SharePoint project that "when they said this, they really meant that".
Step 4: Assessing Feasibility
So you now have a detailed list and description of every deliverable to be produced by your SharePoint project, in priority order and separated as mandatory / optional. Great! But is it feasible to achieve within the project end date? Before you confirm the scope, you need to review every deliverable in the list and get a general indication from your SharePoint team as to whether they can all be completed before your SharePoint project end date. If they can't, then which deliverables can you remove from the list to make your end date more achievable?
Step 5: Get the thumbs up
Present the prioritized set of deliverables to your SharePoint project Sponsor and ask them to approve the list as your SharePoint project scope. Ask them to agree to the priorities, the deliverable descriptions and the items out of scope.
By getting formal sign-off, you're in a great position to be able to manage the SharePoint project scope down the track. So when your Sponsor says to you in a few weeks time "Can you please add these deliverables to the list?", you can respond by saying "Yes, but I'll either have to remove some items from the list to do it, or extend the SharePoint project end date. Which is it to be?". You can easily manage your Sponsors expectations with a detailed scope document at your side.
The scope document is the SharePoint project Manager's armor. It protects them from changes and makes them feel invincible!
Step 1: Set the Direction
Start off by setting the direction for the SharePoint project. Do you have an agreed SharePoint project Vision, Objectives and Timeframes? Are they specified in depth and has your customer agreed to them? Does everyone in the SharePoint project team truly understand them and why they are important? Only by fixing the SharePoint project direction can you truly fix the SharePoint project scope.
Step 2: Scope Workshops
The best way to get buy-in to your SharePoint project scope is to get all of the relevant stakeholders to help you define it. So get your SharePoint project sponsor, customer and other stakeholders in a room and run a workshop to identify the scope. What you want from them is an agreed set of major deliverables to be produced by the SharePoint project. You also want to know "what's out of scope".
Run the workshop by asking each stakeholder for a list of the deliverables they expect the SharePoint project team to deliver. Take the full list of deliverables generated in the workshop and get them to agree on what's mandatory and what's optional. Then ask them to prioritize the list, so you know what has to be delivered first.
Step 3: Fleshing it out
You now have an agreed list of deliverables. But it's still not enough. You need to define each deliverable in depth. Work with the relevant people in your business to describe how each deliverable will look and feel, how it would operate and how it would be supported etc. Your goal here is to make it so specific that your customer cannot state later in the SharePoint project that "when they said this, they really meant that".
Step 4: Assessing Feasibility
So you now have a detailed list and description of every deliverable to be produced by your SharePoint project, in priority order and separated as mandatory / optional. Great! But is it feasible to achieve within the project end date? Before you confirm the scope, you need to review every deliverable in the list and get a general indication from your SharePoint team as to whether they can all be completed before your SharePoint project end date. If they can't, then which deliverables can you remove from the list to make your end date more achievable?
Step 5: Get the thumbs up
Present the prioritized set of deliverables to your SharePoint project Sponsor and ask them to approve the list as your SharePoint project scope. Ask them to agree to the priorities, the deliverable descriptions and the items out of scope.
By getting formal sign-off, you're in a great position to be able to manage the SharePoint project scope down the track. So when your Sponsor says to you in a few weeks time "Can you please add these deliverables to the list?", you can respond by saying "Yes, but I'll either have to remove some items from the list to do it, or extend the SharePoint project end date. Which is it to be?". You can easily manage your Sponsors expectations with a detailed scope document at your side.
The scope document is the SharePoint project Manager's armor. It protects them from changes and makes them feel invincible!
Comments