Project Management Central

Please login or join to subscribe to this thread

Topics: Information Technology, New Practitioners, Using PMI Standards
MP4PM: What should a "Statement of work" include?
Network:132203



In my last blog posting i have Introduced Part II of my "MP4PM" initiative what is all about "review business case"

For further information please have a look here:
https://www.projectmanagement.com/blog-pos...ment---Part-III

Now it is time to work through the next installment which will be a mindmap/template for conducting a "Statement of work" as an input to the "develop project charter" process in the PMBoK Guide..

Let's have a short look what the PMBoK Guide (5th Edition!) has to say about the "Statement of work" :

"The project statement of work (SOW) is a narrative description of products, services, or results to be delivered by a project. For internal projects, the project initiator or sponsor provides the statement of work based on business needs, product, or service requirements. For external projects, the statement of work can be received from the customer as part of a bid document, (e.g., a request for proposal, request for information, or request for bid) or as part of a contract. The SOW references the following:
• Business need. An organization’s business need may be based on a market demand, technological advance, legal requirement, government regulation, or environmental consideration. Typically, the business need and the cost-benefit analysis are contained in the business case to justify the project.
• Product scope description. The product scope description documents the characteristics of the product, service, or results that the project will be undertaken to create. The description should also document the relationship between the products, services, or results being created and the business need that the project will address.
• Strategic plan. The strategic plan documents the organization’s strategic vision, goals, and objectives and may contain a high-level mission statement. All projects should be aligned with their organization’s
strategic plan. Strategic plan alignment ensures that each project contributes to the overall objections of the organization.
"

The goal is know to setup a mindmapTemplate which provides the structure and the guideline to document all the needed information which is needed to conduct a proper "Statement of work (SOW)".

Please have a look here on the beta version of the "Statement of work (SOW)" map:

http://www.projectmanagement.plus/mp4pmmap...ent%20of%20Work

Since the already existing beta version of the map (work in progress) has already several sections/branches i will again setup a separate discussion thread for more or less each of this branches.

I will provide all the single links to the discussion in one of the next postings here.

It would be great if many of you would participate on the discussion and so helping to develop a first class "Statement of work" map/template.

Thanks so much in advance!

Regards,

Markus
Sort By:
Page: 1 2 next>
Network:132203



please refer to the following discussion threads for your input:


MP4PM: Statement of work - opportunity/business need/Goals/Scope

https://www.projectmanagement.com/discussi...eed-Goals-Scope


MP4PM: Statement of work - Scheduling Goals / Key Milestones

https://www.projectmanagement.com/discussi...-Key-Milestones


MP4PM: Statement of work - Success Cirteria/ cost estimates

https://www.projectmanagement.com/discussi...-cost-estimates


MP4PM: Statement of work - Assumptions / Constraints / Requirements

https://www.projectmanagement.com/discussi...---Requirements

If you have any additional topcis that you do miss actually please do not hesitate to post them here.

Thanks for your inputs in advance.

Regards,

Markus
Network:838



Hi Markus,

could you please check the link to the map? I just get a blank page but no error message.

Thanks,

Thilo
...
1 reply by Markus Kopko, PMP
Dec 23, 2016 4:01 AM
Markus Kopko, PMP
...
Hi Thilo,

just checked the link and it works for me. I do use the FF Brwoser latest version.
Sometimes the map needs a bit of time to be loaded.
May be you have some add blocker or noscript active?

Anyone else with that experience?

Thilo, if it still doesn't work for you please send me your email via pm and i will send you the map directly.

Regards,

Markus
Network:66



Thank you for this post and series. It is especially helpful as a project manager to be spending this extra time delving into the details of items that we "get used to" making day in and day out. You articles that you posted have been extremely helpful and I look forward to reading more of your posts.
...
1 reply by Markus Kopko, PMP
Dec 23, 2016 4:02 AM
Markus Kopko, PMP
...
Hi Austin,

very nice to see a new face participating in the discussion, highly appreciated!
And many thanks for your kind words, such feedback is really encouraging and motivating.

Regards,

Markus
Network:132203



Dec 22, 2016 11:32 AM
Replying to Thilo Wack
...
Hi Markus,

could you please check the link to the map? I just get a blank page but no error message.

Thanks,

Thilo
Hi Thilo,

just checked the link and it works for me. I do use the FF Brwoser latest version.
Sometimes the map needs a bit of time to be loaded.
May be you have some add blocker or noscript active?

Anyone else with that experience?

Thilo, if it still doesn't work for you please send me your email via pm and i will send you the map directly.

Regards,

Markus
...
1 reply by Thilo Wack
Dec 23, 2016 7:26 AM
Thilo Wack
...
Hi Markus,

today the link worked, no changes were necessary from my side. The map indeed takes some time to load. I probably just had a very slow connection yesterday and maybe not enough patience...

Merry Christmas and a Happy New Year! Have some happy and restful holidays.

Kind regards,

Thilo
Network:132203



Dec 22, 2016 12:00 PM
Replying to Austin W. Duncan
...
Thank you for this post and series. It is especially helpful as a project manager to be spending this extra time delving into the details of items that we "get used to" making day in and day out. You articles that you posted have been extremely helpful and I look forward to reading more of your posts.
Hi Austin,

very nice to see a new face participating in the discussion, highly appreciated!
And many thanks for your kind words, such feedback is really encouraging and motivating.

Regards,

Markus
Network:838



Dec 23, 2016 4:01 AM
Replying to Markus Kopko, PMP
...
Hi Thilo,

just checked the link and it works for me. I do use the FF Brwoser latest version.
Sometimes the map needs a bit of time to be loaded.
May be you have some add blocker or noscript active?

Anyone else with that experience?

Thilo, if it still doesn't work for you please send me your email via pm and i will send you the map directly.

Regards,

Markus
Hi Markus,

today the link worked, no changes were necessary from my side. The map indeed takes some time to load. I probably just had a very slow connection yesterday and maybe not enough patience...

Merry Christmas and a Happy New Year! Have some happy and restful holidays.

Kind regards,

Thilo
Network:838



Hi Markus,

took me a while to find the time to go through the map. So here are my comments:

- the point of restrictions in the assumptions branch and the branch constraints seem very similar, the only difference I see that might be relevant for a project manager is that there could be things that the project is not allowed to touch, even if that means objectives will not be achieved while others may be fair game to change/influence if need be; this differences should be clarified with the Sponsor and/or steering committee

- it might help the user to have a glossary and once you've established it go through the map and use it to make the wording uniform

- again there is some overlap with the other maps, which of course is only natural; in the same vein as the comments above, maybe at the end of this effort it makes sense to go through everything and look if maybe some elements of a map would also fit into others

Regards,

Thilo
...
1 reply by Markus Kopko, PMP
Jan 11, 2017 7:48 AM
Markus Kopko, PMP
...
Hi Thilo,

still a happy new year to you. ;)
No worries, i know that we all have a lot to do (there are some projects to be managed for sure, i guess;) ). I am glad for any inputs.

regarding the restrictions/constraints branches:
i saw your point and have tweeked this now a bit, i have moved the restrictions branch up to the constraints section and named it "other restrictions" in addition to the already existing constraint branches. I guess this way around it makes more sense.
Thank you for that, update will come soon.

I am not sure if i got the point regarding the glossary in the right way ... do you think we should rely on the PMI glossary? To define an additional glossary seems not much useful to me ... or did i got you totally wrong here?

Regarding the overlaps:
Like you said it, this is just natural within this initiative sice we want to align as close to the PMBoK Guide as we can.
For instance: the SOW will not be used in any project. External projects mostly have somewhat contract/business case/other business documents and a SOW will not be needed there. Internal projects often do miss something like contractual documents and a SOW might be more appropriate here.
And of course in some projects you will have both ...
In the end it is a matter of tayloring the MP4PM framework (not to say the PMBoK Guide processes) to the specific project needs.

And the good news is that it is very easy to transfer information already recorded in one map to another where it is also needed, right?

But of course we will try to align all the maps in a way to avoid unnecessary efforts (this will be an ongoing task i guess ...;) ).

Like always Thilo, many thanks for your valuable inputs, highly apprciated!

Hope to see you in the webinar ...;)

Regards,

Markus
Network:132203



Jan 10, 2017 2:42 PM
Replying to Thilo Wack
...
Hi Markus,

took me a while to find the time to go through the map. So here are my comments:

- the point of restrictions in the assumptions branch and the branch constraints seem very similar, the only difference I see that might be relevant for a project manager is that there could be things that the project is not allowed to touch, even if that means objectives will not be achieved while others may be fair game to change/influence if need be; this differences should be clarified with the Sponsor and/or steering committee

- it might help the user to have a glossary and once you've established it go through the map and use it to make the wording uniform

- again there is some overlap with the other maps, which of course is only natural; in the same vein as the comments above, maybe at the end of this effort it makes sense to go through everything and look if maybe some elements of a map would also fit into others

Regards,

Thilo
Hi Thilo,

still a happy new year to you. ;)
No worries, i know that we all have a lot to do (there are some projects to be managed for sure, i guess;) ). I am glad for any inputs.

regarding the restrictions/constraints branches:
i saw your point and have tweeked this now a bit, i have moved the restrictions branch up to the constraints section and named it "other restrictions" in addition to the already existing constraint branches. I guess this way around it makes more sense.
Thank you for that, update will come soon.

I am not sure if i got the point regarding the glossary in the right way ... do you think we should rely on the PMI glossary? To define an additional glossary seems not much useful to me ... or did i got you totally wrong here?

Regarding the overlaps:
Like you said it, this is just natural within this initiative sice we want to align as close to the PMBoK Guide as we can.
For instance: the SOW will not be used in any project. External projects mostly have somewhat contract/business case/other business documents and a SOW will not be needed there. Internal projects often do miss something like contractual documents and a SOW might be more appropriate here.
And of course in some projects you will have both ...
In the end it is a matter of tayloring the MP4PM framework (not to say the PMBoK Guide processes) to the specific project needs.

And the good news is that it is very easy to transfer information already recorded in one map to another where it is also needed, right?

But of course we will try to align all the maps in a way to avoid unnecessary efforts (this will be an ongoing task i guess ...;) ).

Like always Thilo, many thanks for your valuable inputs, highly apprciated!

Hope to see you in the webinar ...;)

Regards,

Markus
...
1 reply by Thilo Wack
Jan 12, 2017 1:56 PM
Thilo Wack
...
Hi Markus,

I hope you had a great start into 2017. Regarding the glossary I'd indeed recommend to stick to the PMI/PMBoK definitions, but moreover, I think that there are some terms (take the example of constraints and restrictions for example) where it would be helpful to establish a glossary so that in all maps you would not use different words for the same thing. I do not think that the user would need a glossary to get definitions on the terms, but like me they might wonder about nuances/subtleties in the word's meaning that just are not there.
Regarding the overlaps, the maps will make it easy to customize things, you just have to know about this option. Users new to project management might not know about all the overlaps and experienced PMs who are new to mind maps might also miss the opportunity because they do not know about the advantages of mind maps. It is just a thing of being aware what you can do with this tool.

Best regards,

Thilo
Network:838



Jan 11, 2017 7:48 AM
Replying to Markus Kopko, PMP
...
Hi Thilo,

still a happy new year to you. ;)
No worries, i know that we all have a lot to do (there are some projects to be managed for sure, i guess;) ). I am glad for any inputs.

regarding the restrictions/constraints branches:
i saw your point and have tweeked this now a bit, i have moved the restrictions branch up to the constraints section and named it "other restrictions" in addition to the already existing constraint branches. I guess this way around it makes more sense.
Thank you for that, update will come soon.

I am not sure if i got the point regarding the glossary in the right way ... do you think we should rely on the PMI glossary? To define an additional glossary seems not much useful to me ... or did i got you totally wrong here?

Regarding the overlaps:
Like you said it, this is just natural within this initiative sice we want to align as close to the PMBoK Guide as we can.
For instance: the SOW will not be used in any project. External projects mostly have somewhat contract/business case/other business documents and a SOW will not be needed there. Internal projects often do miss something like contractual documents and a SOW might be more appropriate here.
And of course in some projects you will have both ...
In the end it is a matter of tayloring the MP4PM framework (not to say the PMBoK Guide processes) to the specific project needs.

And the good news is that it is very easy to transfer information already recorded in one map to another where it is also needed, right?

But of course we will try to align all the maps in a way to avoid unnecessary efforts (this will be an ongoing task i guess ...;) ).

Like always Thilo, many thanks for your valuable inputs, highly apprciated!

Hope to see you in the webinar ...;)

Regards,

Markus
Hi Markus,

I hope you had a great start into 2017. Regarding the glossary I'd indeed recommend to stick to the PMI/PMBoK definitions, but moreover, I think that there are some terms (take the example of constraints and restrictions for example) where it would be helpful to establish a glossary so that in all maps you would not use different words for the same thing. I do not think that the user would need a glossary to get definitions on the terms, but like me they might wonder about nuances/subtleties in the word's meaning that just are not there.
Regarding the overlaps, the maps will make it easy to customize things, you just have to know about this option. Users new to project management might not know about all the overlaps and experienced PMs who are new to mind maps might also miss the opportunity because they do not know about the advantages of mind maps. It is just a thing of being aware what you can do with this tool.

Best regards,

Thilo
...
1 reply by Markus Kopko, PMP
Jan 13, 2017 5:48 AM
Markus Kopko, PMP
...
Hi Thilo,

yes, i had a great start into 2017. Thank you. I hope you had also ... ;)
I am totally with you regarding the terms and the overlaps.
Well, therefore we will do the webinars and i am also planning to provide tutorial videos in addition on my website to show exactly this options and benefits coming with the use of mind maps and mind mapping software in the context of MP4PM. ;)

Regards,

Markus
Network:838



Markus,

totally forgot: Of course, I really would like to attend the webinar. Do you already have an idea regarding the date?

Best,

Thilo
...
1 reply by Markus Kopko, PMP
Jan 13, 2017 4:59 AM
Markus Kopko, PMP
...
Hi Thilo,

you may register already here:

https://www.projectmanagement.com/webinars...authenticated=1

Regards,

Markus
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

I'm a great quitter. I come from a long line of quitters. I was raised to give up.

- George Costanza

ADVERTISEMENT

Sponsors