Project Scope Statement: How to Create it on Example
ฝัง
- เผยแพร่เมื่อ 28 เม.ย. 2024
- ✅ Master Project Scope Management and Make Clients Happy
pages.itpmschool.com/scope-ma...
#itprojectmanagement #projectmanagement #itprojectmanager
It's a checkpoint at which clients and customers approve the project scope.
Project Scope Statement is a simple document that describes the work that needs to be done on a project.
Ideally, you need to write it in such a way that your clients understand it.
In no case you want to use this document to cover your back, add hidden costs, or work.
Any deliverables and any work that is not stated in the Project Scope Statement is out of the current project.
However, it should not be a detailed contract, as well.
Treat it as a mutually beneficial agreement.
You agree to plan the project further based on the contents of the Scope Statement.
Clients agree to accept the results described in it.
It also applies one crucial thing:
Clients ask for a change or additional work. It's not in the Project Scope Statement.
It means that you should be allowed to make adjustments in the project budget and schedule.
If you approach the creation of this document with the correct mindset - you'll increase the chances for project success dramatically.
In this video, I also provide a project scope statement example. We'll create it together based on a simple Web Site project.
I'll walk you through all the sections of the document showing possible language you can use.
Nevertheless, do not fix on the words I use. You need to use language that your clients understand.
They need to see the complexity and scale of the project. Ideally, they should also be able to imagine the deliverables you describe.
As a side note:
Project Scope Statement is described in the PMBOK Guide. PMI provides a specific structure. But it doesn't mean that you should follow it to the letter.
You, as a project manager, have to adapt the document so that it is useful on your given project.
***
Do you want to become a project manager - get my Career Change Cheat Sheet!
Scope Baseline, Project Scope Statement, and More (+Examples):
pmbasics101.com/project-scope/
![The Correct Requirements Traceability Matrix [+template]](http://i.ytimg.com/vi/BYn83CEXSgo/mqdefault.jpg)
✅ Master Project Scope Management and Make Clients Happy
pages.itpmschool.com/scope-management
1. Client’s understanding.
Client understands the project scope
Great, thanks for feedback!
Thanks!
i think it's the first. Isn't it?
The way you describe the project scope statement with example it is easy to understand. So thank you for sharing this information.
You're very welcome, Hardik! Glad it's useful.
Thank you so much for this detailed and well-explained presentation! I truly appreciate you taking the time to do this!
You are welcome. I’m really glad you find it useful. And thanks for the feedback - it means a lot to me.
Wonderfully detailed explanation & love the way you clearly emphasized the interconnectivity with change management, budget & schedule perspectives to the scope statement. Many thanks.
Glad it was helpful. Thanks for your feedback - it means a lot to me:)
Thanks for the brilliant presentation. I think both are very good benefits but the biggest benefit would be the understanding of the client as any job done on the project is seen at the customer's prospective.
Thanks for your kind feedback! Yes, a great benefit of the scope statement as well.
You have saved me in my software engineering class, thanks!
Glad I could help!
Thank You for sharing your knowledge! Great work Sir.
My pleasure, Axell!
Both 1 and 2 are significant reasons why the project scope is important; Eliminates guess-work.
Thanks for your feedback!
loving your presentations, simple and short
Glad you like them, Abhijeet! Thanks for you feedback.
Understanding the project scope explained by the client is important as this would help to make modifications to the project when necessary.
Thanks for your feedback, Idris. They a good summary/insight!
Very informative. Thank you!
Glad it was helpful!
thank you for this explanation. I am new to Project Management. This explanation is excellent. thank you very much
Thanks for your kind feedback!
(Sorry for the late response. Still catching up after New Year holidays.)
You nail it Thank you
You are welcome. Glad you found it valuable.
Yes, Thanks! 😊
You're welcome 😊! Thanks for your feedback.
This is a very useful video with step by step guide that has examples.
Thanks for writing, Russell. Glad you enjoyed it!
The explanation aligns perfectly with what I aimed to learn, considering that many individuals , like me struggle to formulate a project scope statement. Established project managers may find value in leveraging these resources.
Thanks for participation and feedback.
Curious to know what kind of training/event got you to this video?
@@ITProjectManagers ALX Africa's AI Career Essential course.
It is for understanding all the projects scope by customer. Because when a change request become you have to check it with Scope baseline that should include all Scope Statment. WBS and WBS dictionary that they have been agreed with So you can not just check Scope statement in this instance. great job bro thnx
You are welcome, Salah. Great summary.
Hi dmitriy, im from indonesia, thank u so much for your presentation, all of point its really essential from PM. Btw i have followed u on linkedln 😊. Thank u
Glad it was helpful, Ruth!
Excellent video. Thank you!
Glad it was helpful! Thanks for your feedback.
Amazing explanation thank you.
Glad it was helpful!
Awesome. I am here based on ALX' recommendation
Thanks for comingю
Who's ALX?
Thank you!
You are welcome, Muderhwa!
Many Thanks
You are welcome! Glad it's useful.
Yes...thanks
You're welcome! Thanks for feedback.
Thank you
Great Video
Glad you liked it!
Thanks for the video!!!!!
You are welcome!
Yes, great content.💕
You are welcome, Philip. Glad you found it useful.
awesome, this is what I am looking for. I am studying to become a Project Manager in a software outsourcing company. This video helps me a lot. Thank you so much.
Can we consider each deliverable equal an epic (epic includes user stories)
I found the definition
A deliverable is a tangible part of the work completed to meet project objectives. It can be a part of the product or service that stakeholders can try or see. It can be a project document or a part of the Project Management Plan. In any case, it is something important we need to finish our project.
Deliverable includes Epics and User Stories.
So Work Packages = Epics , right?
Glad it was helpful!
No, in software development, a build or a version of your product is actually a main deliverable. This build can include some finished User Stories or whole feature/epics. But you shouldn’t wait for the whole epic to be complected to create an Interim deliverable to demonstrate some functionality your already finished.
In software a deliverable is a build or a version of your product or service.
You can have many interim deliverables that includes certain User Stories. Then, you can have an external deliverable that you’ll show to project stakeholders. For example, it will include the whole finished epic.
User Stories, Features and Epics are the tool of the requirements management. You need to decide which deliverable will include required User Stories.
As you understand, in Scrum we progressively add an increment of User Stories in each next deliverable.
Very helpful, thanks
Glad it was helpful!
Thank you so much👌
You are welcome, Hazel!
Easily understandable and informative video on how to write a project scope. I hope you are doing good.
I want some real questions for the interview preparation of PM role in MNC. Can you please provide or share the link asap. Your kind help will be much appreciated. Thanks in advance.
Hi Krutika, thanks for your feedback. Here’s the link to videos I have on interview questions: th-cam.com/play/PLjbXjDdSp7vdoOusKG7Wzi8aD6E-qbejb.html
YES!
Thank you for your feedback, Naedeezy!
Very good! Thanks!
Glad you liked it! Thanks for writing back.
Yes 👍
Thanks for your feedback, Ian. Sorry for the late response.
Thank you for this video
My pleasure. Glad to hear you found it useful.
YES
Great! Thanks for your feedback.
Yes
Great, thanks!
thank you
You're welcome
شكرا جزيلا
You are welcome:)
Insightful. Thank you
You're very welcome
Hi, Thank you so much this video was very helpful. Can you please explain the difference between Project Charter and The Scope Statement.
Thank you in advance.
I have a full video on Project Charter as well: th-cam.com/video/78-zA_PZpmE/w-d-xo.html
In short, you create a Project Charter at the very start of the project. The main goal is to identify the project's goal, constraints, and boundaries. Based on this information you'll collect requirements that will help you reach the goal. Based on requirements you need to identify the project scope - the actual work you need to perform and the deliverable you need to create. That's where the Project Scope Statement comes in to play. You describe the project scope in this document with language that your clients and sponsors understand. They need to sign it off so that you can plan the project based on this scope of work.
Thank you so much. Much appreciate your kind reply.
@@shahlinaiqbal4421 You are welcome!
I would say my ability to refer to my scoop statement when needed..great content..recommended class by ALX kenya
Thanks!
helpful
Glad you think so, Kanwal!
yes
Thank you for your feedback and participation, Melody!
Thnk you.
You're most welcome!
Brilliant work. I want to ask a thing in project justification (3:18), why you have written: "I as customer". Previously you as that "I work in a web development studio".
Good question. Now, I see why it confused you:)
So, the idea is that I work in a web development studio and I collect this information from a customer who needs a web site. The customer is a blogger, so he would tell me some like, "As a customer, I need a web site."
But usually, you want to be specific about the "avatar" for a piece of requirements. Therefore, I should have written "As a blogger, I need a web site..." on that slide.
By the way, if you haven’t see the latest video, it’s on scope management as well. It gives you another example: th-cam.com/video/NvGVy2IIgvs/w-d-xo.html
Thanks for clearing the query
Haven't had a chance to test if it holds zero, but mounts just fine and has nice clear glass. Centered vertically true to a plumb line with the crosshairs which is always a plus!It's a great th-cam.com/users/postUgkxc4K63Fd5LglDMObu7-Bgapxp_ef0W8hE scope. There's no parallax adjustment or focus ring, so may be limited to 3-7x, have to see how it is on the range. Also be aware that the rings are "look through" so you can still use irons, but they are really tall if you only intend to use the optics. On a 22LR no biggie since I'm not shooting competitions or worried about a hard cheek press. Will boresight and range test, if all goes well, I'll leave it at that!
Glad you found it useful!
Thanks for the clear video.
The Project Scope wouldn’t be shared with the customer if you are designing a product for many future customers.
However if you have only one customer who is paying for the product and project then you’d share the Project Scope to show the work that you will be doing. Often the project scope is included within a schedule (Gantt Chart) which also shows when you will do each aspect of the project.
Well, in case you work in a product company the "share solution" for your clients is a part of your services. The scope of work in such a case is integrating and customizing the solution. That’s the scope you do show to the client.
However, if you re-use something you create for one clients in the work for the other client...well, in most cases it’s illegal because all the results of a project belong to the client who paid for it.
very well explained!
Glad it was helpful, Clare!
Hi. So scope baseline includes project scope statement, wbs and wbs dictionary. And wbs still needed to include in project scope statement?
Thanks
Hi Andrew,
Yes, Scope Baseline includes Project Scope Statement, WBS, and WBS Dictionary.
In the Project Scope Statement, we describe major deliverables.
Here’s how it works on a high level. You create a Project Charter and usually it contains major deliverables of the project (e.g. iOS application + User Guide + Instructional videos). Clients approve the Project Charter.
You take these major deliverables and collect requirement on them from stakeholders. It’s totally OK if you identify more major deliverables. in the process.
Then, you describe these deliverables and how you’ll create them in the Scope Statement. You describe them in a language so that you clients can understand it and approve.
After approval, you take these major deliverables and put them into your WBS and decompose them further.
That’s how project integration management works on this level.
Kudos for the Video clip! Excuse me for chiming in, I would appreciate your thoughts. Have you ever tried - Weydaniel Organized Dominator (probably on Google)? It is a great one off product for getting 7000 plus project management and business templates minus the headache. Ive heard some interesting things about it and my cooworker at very last got astronomical results with it.
thx
You are welcome! Glad it's helpful.
I have a question. Within an agile project do we allow the statement of work to go through the scrum process, if so how do we document the statement of work process. Before you can start actuall project at my job, we need a SOW, But we all know building a SOW is work
Hi Keith,
Sorry for delaying the reply. That’s a great question.
Building a SOW definitely takes some time and effort. But you don’t need the whole team for that. It should be a high-level document describing major deliverables. So, ideally you need to create it before you get into Sprint 1. Creating it during a sprint kills the purpose of the document.
In general, you need to treat projects as if they have at least several phases, not only the execution with Scrum. Check out this article: pmbasics101.com/software-development-life-cycle/
There’s a chapter on how to treat smaller projects and where you should create SOW and similar activities.
yess
Great! Thanks for your feedback!
Thank you for the video. I have to create a project scope statement for work but I don't have a business background and I am struggling to understand how to write them. There seems to be alot of assumed information in business and I just don't have that information. I couldn't follow the explanation for what the difference is between requirements and scope. As far as I can tell the requirements are what needs to be done in a project, and a scope is what needs to be done in a project. When you described the two you seemed to be implying that there is a difference, but I couldn't grasp what that difference is.
Does anyone have any suggestions for resources that explain what is needed but also the background of the process so that someone without a business background might be able to follow along? Thanks heaps.
Requirements describe what the product/service should be capable of, how it looks, it's characteristics.
Scope describes what need to be done (actual work) to implement those requirements.
For example, requirement "the door should be with magnetic lock operated by iOS application."
Scope of work: deliver new door to the site, uninstall old door, install new door, setup iOS application, test the door.
@@ITProjectManagers Thanks so much for taking the time to explain, I really appreciate it. I still struggle to see the distinction as they both sound like the things that need to be done, but some of those things are being grouped together like getting the door to open using an iOS application, that needs to be done, but it is being called a requirement, but then other things that need to be done such as the installation of the door and setting up the software are being called scope. It seems to me that they are all a part of the step by step set of physical tasks that need to be done to complete the overall project. Which is fine, but the only reason I ask is that if I break a project up into each of the incremental tasks that are completed one after the other, I don't see how one picks which of those tasks are considered requirements, and which are considered scope. Then I notice there is a section later on in a scope document in which the overal project is broken down into the individual tasks that need to be completed and are listed again. It all seems very redundant and repetitive, so I feel like I am missing something really important.
@@AusFastLife It may sound repetetive because it's a simple example on a physical product you can imagine. Here's a different one.
Requirement: store customer's data provided in e-commerce store in database.
Can you come up with all tasks required to implement this requirement? There might things like create API, set up Web Function, etc. And there might be a lot of tasks if you do it from scretch. So, physical tasks will not be obvious, more over there will be tasks for different functions (not only developers).
In the long run, the requirement will be implemented, but no one will see it.
I recommend that you read this article, it may help you understand better the concepts: itpmschool.com/project-decomposition/
If I'm a freelancer, who does the project scope, me or the client? I just watched another video saying I should request the project scope from my client. I was just confused in this part
Generally, as a technical expert, you must create a project scope statement. This document explains to customers what work you plan to perform in order to achieve the project's objectives. What you may want to ask from a client is a Project Charter: th-cam.com/video/VrB-xkrX158/w-d-xo.html
As a freelancer, you may create a simple template that clients fill out.
Don't confuse Scope Statement with a Statement of Work (SOW). SOW is usually an addition to a contract that outlines the required work. SOW is provided by the client.
@@ITProjectManagers i thought I'll have to do SOW as well. This is so confusing 😅 Do i have to provide the contract or the client? I'll be having a discovery call with a big company and this is my first time, so I'm searching about the process and knowing that they are a big company, I don't know if they will provide those documents
@@mikachu4854 a big company will surely enforce their own contracts, NDAs, and systems as much as possible.
In general, all this formal documentation is required to secure your agreements and get paid. So, if the other side don't have these documents or don't want to use them, then you should provide you templates. You are interested to secure your business relationships.
@@ITProjectManagers I could just ask them if I would provide it right? Because I'm a freelance copywriter and I would like to be specific when it comes to revisions (and other limitations so I won't be overworked) and i think that was part of the SOW. I'm not sure... So in case we ended up proceeding after the proposal, I will create the project scope, request for a SOW, then sign contract or NDA provided by them? Is that how it goes?
Yeees
Thanks for you feedback! Great to know we on the same page.
What is the difference between a project scope statement and a project proposal?
Hi Mumba, great question.
These are completely different documents.
Usually you create Project Propasal before a project exists. With this document, you try to persuade stakeholders and sponsors to select and fund your proposed project. You focus on business cases and benefits for organization. You may need to create Proposal for internal projects. However, sometimes, you may want to propose a new project to an existing client and you'll create a Project Proposal.
Project Scope Statement is a document you create for an existing project after you collected requirements. With this document, you try to explain the scope of work required to reach project objectives to the clients and sponsors. You want to get their educated and informed sign-off so that you continue planning the approve scope.
Please let me know if it answers you question.
Bro what is the simple defination of collect requirements can u tell me brother
Hi Bro,
Simple one is this:
Collect requirements means communicating with clients and other people to collect information about how your product or service should look like and what is should be capable of.
You can do this in many different ways.
@@ITProjectManagers thanx alot👍
👍
Sir was n requirement gathering, can you please elaborate the role of subject matter expert after we get the requirements from client. Are these people lie on project side or product side ?
There are different Subject Matter Experts (SME). Usually we refer to SME as a business person who provides insights on how things work in the real world, so that the project team can implement it in their product or service. These people are usually on the product side. On the other hand, there are "technical" SME. Usually these are internal stakeholder with superior knowledge of the technical domain you work in. They are no a part of your team usually. They may help the team or act as ordinary stakeholders that you need to engage. Rarely, you may acquire a SME into your project team. They would work for you part time to help collect or generate requirements, and understand the business need. Usually it happens when client (project owners) don’t have expertise in the areas for which they develop the product. I hope it clears things out.
Dmitriy - Project Management Basics Thanks Sir.
Dmitriy - Project Management Basics sir I have one more query. Does sponsor lies on both product side and project side ? Please elaborate
@@jagroop200, sorry for late reponse. This comment didn't show up for me;(
On a high-level, a Project Sponsor always pays for a specific project. However, it doesn't mean he cannot sponsor a series of project to create a product. In both cases, this role is outside of the project team. This persons or entity can be internal or external stakeholder. So, the short answer is that Sponsor can be on any side.
Benefits- tells people I know funding is a potential issue
Sorry, I missed your comment. If it's still actual, please write a new one.
Note: leaving this comment to keep track of open questions.
I think if you translate it in Arabic the watching will increase it is only my opinion ☺️ and thanks for this explaining
Thanks for your kind feedback. I have a long list of languages people propose me to use. Unfortunately I know only two:)
Please use background picture while talking consistantly to make it more understandable....
Thanks for writing. Not sure what you suggest here. Can you explain?
@@ITProjectManagers kindly first
Use graphical representation
Use images and point images by using your hand about which you are explaining instead of theory,
Because visual graphic is great teacher....
Try to use white board in background make environment like a class room . If you can it will help is easier to understand..
Yes XD
Thanks for your feedback!
This was great, thanks, I have been researching "simple project plan template free download" for a while now, and I think this has helped. Ever heard of - Biycarlett Astounded Builder - (search on google ) ? It is an awesome one off product for discovering how to download thousands of business and project management templates without the hard work. Ive heard some super things about it and my partner got great success with it.
Why poeple are saying yes ?
You need to watch the video to learn why:)
Would you like to eat a pineapple?
Nope, I don’t like it.
обхсс
Thank for a mindful comment. Do you want to explain your thoughts further?
Yes
Good job!
YES
Thanks for your feedback, Keza!
yes
Thanks for writing back, King!
Yes
Thanks for your feedback, Juliet. What was the biggest takeaway from this video for you?
Yes
Thanks for your feedback!
Yes
Thanks for your feedback, Uchechi.
Yes
Thanks for feedback.
Yes
Thank you for your feedback, Amogelang!
Yes
Thanks!
Yes
Thanks for your feedback!
Yes
Thanks for your feedback!
Yes
Thanks for feedback!
Yes
Great! Thanks for your feedback!
Yes
Great! Thank you for your feedback!
Yes
Thanks for your feedback!
yes
Thanks for your feedback, Allwell!
yes
Thanks for your feedback!
Yes
Thank you for your feedback!
Yes
Thanks for your feedback!
yes
Thanks for your feedback! I really appreciate it
yes
Nice, Ian. Thanks for your feedback and participation.
yes
Great! Thanks for your feedback!
Yes
Thanks for participation and feedback.
Curious to know what kind of training/event got you to this video?
@@ITProjectManagers it is an ALX AiCE program
yes
Thanks for participation and feedback.
Curious to know what kind of training/event got you to this video?