A Statement of Work is an important part of the contracting process. If you work a s a Project Manager, you are almost certain to encounter and SoW at some time. Thank you for watching. Please support the channel and all the free content I provide. Like, comment, and subscribe to the channel. And why not join my community, free! Sign-up at onlinepmcourses.com/assets440251/the-onlinepmcourses-newsletter/ And to show maximum appreciation, use the $ Thanks button, under the video, to make a small donation with a highlighted comment.
Thank you for your videos. What project standard are you using for the development of the SoW you are referring to? Is this a Procurement Statement of Work per the PMBoK 6th Edition? Thanks
You are very welcome! Unless otherwise stated, my videos are all methodology and standard agnostic. They refer to general good practice, rather than to any one system. This is so that they are useful to all project managers, no matter their background.
As I understand the term 'Plan on a Page', this is a one page plan for (in this case) your project. An SoW only covers the work to be done by a specific subset of the project resources and may exclude some elements of a full plan. A plan on a page is also likely to be a simplified planning tool - either for a small project or as a communication tool for describing the project in a simplified form. SoW on the other hand is a contractual (or quasi-contractual) document that sets out the work requirements for a specific organization, person, or group.
That's not an unreasonable interpretation. Yet a Scope of Work can be very detailed - if articulated through a comprehensive Work Breakdown Structure. A Statement of Work is the work one party will do and is either a commitment that they will do the work, or a requirement against which they commit to work. So, it has a contractual or quasi contractual character. It is also, usually, a part of the whole work - the Scope of Work is the whole.
A technical annex is an annex (addition) to a contract that covers specific technical details. It''s a very generic term that only becomes specific on context. So, the technical annex to a software procurement contract may contain interoperability specs and hosting requirements. So, you could regard an SOW as a specific example of a technical annex, in the context of a contract for services. But the two things are not the same.
Very nice video. Things i think about myself a few times. The old store bought once sure did have a way to keep on living. Learned alot, greatings from Sweden 🏕
A Statement of Work is an important part of the contracting process. If you work a s a Project Manager, you are almost certain to encounter and SoW at some time.
Thank you for watching.
Please support the channel and all the free content I provide. Like, comment, and subscribe to the channel. And why not join my community, free! Sign-up at onlinepmcourses.com/assets440251/the-onlinepmcourses-newsletter/
And to show maximum appreciation, use the $ Thanks button, under the video, to make a small donation with a highlighted comment.
Thank you for your videos. What project standard are you using for the development of the SoW you are referring to? Is this a Procurement Statement of Work per the PMBoK 6th Edition? Thanks
You are very welcome!
Unless otherwise stated, my videos are all methodology and standard agnostic. They refer to general good practice, rather than to any one system. This is so that they are useful to all project managers, no matter their background.
Thank you for your great work! 🙏Will definitely consider taking your courses😍
Wonderful. You're so welcome!
Thanks for sharing!
You're welcome.
Hi Mike, is SOW same as Plan on the Page ?
No
As I understand the term 'Plan on a Page', this is a one page plan for (in this case) your project. An SoW only covers the work to be done by a specific subset of the project resources and may exclude some elements of a full plan. A plan on a page is also likely to be a simplified planning tool - either for a small project or as a communication tool for describing the project in a simplified form. SoW on the other hand is a contractual (or quasi-contractual) document that sets out the work requirements for a specific organization, person, or group.
It seems like a more detailed Scope of Work?
That's not an unreasonable interpretation. Yet a Scope of Work can be very detailed - if articulated through a comprehensive Work Breakdown Structure.
A Statement of Work is the work one party will do and is either a commitment that they will do the work, or a requirement against which they commit to work. So, it has a contractual or quasi contractual character. It is also, usually, a part of the whole work - the Scope of Work is the whole.
@@Onlinepmcourses Thank you sir :)
is the same as Technical annex?
A technical annex is an annex (addition) to a contract that covers specific technical details. It''s a very generic term that only becomes specific on context. So, the technical annex to a software procurement contract may contain interoperability specs and hosting requirements.
So, you could regard an SOW as a specific example of a technical annex, in the context of a contract for services. But the two things are not the same.
Very nice video. Things i think about myself a few times. The old store bought once sure did have a way to keep on living. Learned alot, greatings from Sweden 🏕
Thanks for sharing