Statement of Work - Revision history

Abiha: /* Project Organization */

2023-05-09T20:21:34Z

Project Organization

← Older revision		Revision as of 20:21, 9 May 2023
Line 172:		Line 172:

	=== Project Organization ===		=== Project Organization ===
	[[File:raci-chart.png\|thumb\|350px\|Figure 3: Example: RACI Chart.<ref name="figure3">Hartney, J., (2019), ''How to Use a RACI Chart to Simplify Responsibilities''. Available at: https://www.projectengineer.net/how-to-use-a-raci-chart-to-simplify-responsibilities/ (Accessed: 7th may 2023)</ref>]]		[[File:raci-chart.png\|thumb\|350px\|Figure 3: Example: RACI Chart.<ref name="figure3">Hartney, J., (2019), How to Use a RACI Chart to Simplify Responsibilities. Available at: https://www.projectengineer.net/how-to-use-a-raci-chart-to-simplify-responsibilities/ (Accessed: 7th may 2023)</ref>]]

	The Project Organization is a section in the SoW that describes the work roles and responsibilities within the organization. It is a good idea to include this section in any SoW as this helps give the stakeholders a clear understanding of the organizational structure and responsibilities of the team. It is recommended that the project manager uses the Responsibility Assignment Matrix (RAM) tool, which is often called a RACI chart. The RACI chart specifies the roles of all stakeholders <ref name = "PMBOK"></ref>. Furthermore, the RACI chart serves as the baseline of the communications plan by emphasizing who receives information, how frequently, and at what level of detail <ref name = "RACI"> Friedman, S. (2008). Roles, responsibilities, and resources: best practices in managing people. Paper presented at PMI® Global Congress 2008—North America, Denver, CO. Newtown Square, PA: Project Management Institute. (Accessed: 7th May 2023)</ref>.		The Project Organization is a section in the SoW that describes the work roles and responsibilities within the organization. It is a good idea to include this section in any SoW as this helps give the stakeholders a clear understanding of the organizational structure and responsibilities of the team. It is recommended that the project manager uses the Responsibility Assignment Matrix (RAM) tool, which is often called a RACI chart. The RACI chart specifies the roles of all stakeholders <ref name = "PMBOK"></ref>. Furthermore, the RACI chart serves as the baseline of the communications plan by emphasizing who receives information, how frequently, and at what level of detail <ref name = "RACI"> Friedman, S. (2008). Roles, responsibilities, and resources: best practices in managing people. Paper presented at PMI® Global Congress 2008—North America, Denver, CO. Newtown Square, PA: Project Management Institute. (Accessed: 7th May 2023)</ref>.

Abiha: /* Limitations */

2023-05-09T20:21:06Z

Limitations

← Older revision		Revision as of 20:21, 9 May 2023
Line 241:		Line 241:
	'''Risk of over detailing'''		'''Risk of over detailing'''

	One of the limitations of creating a SoW document is the risk of going too much into detail. Creating an excessively detailed SoW document can lead to unnecessary work being undertaken simply because it was mentioned in the document. Over-detailing may occur due to the desire to provide thorough information and instructions but lead to the project being stifled <ref name ="lawbite"> LawBite, (2022) What is a Statement Of Work. https://www.lawbite.co.uk/resources/blog/what-is-a-statement-of-work (Accessed 6th May 2023)</ref>. Therefore, it is important for a project manager to assess which parts of a SoW are important to the given project they are working on.		One of the limitations of creating a SoW document is the risk of going too much into detail. Creating an excessively detailed SoW document can lead to unnecessary work being undertaken simply because it was mentioned in the document. Over-detailing may occur due to the desire to provide thorough information and instructions but lead to the project being stifled <ref name ="lawbite"> LawBite, (2022) What is a Statement Of Work. Available at: https://www.lawbite.co.uk/resources/blog/what-is-a-statement-of-work (Accessed: 6th May 2023)</ref>. Therefore, it is important for a project manager to assess which parts of a SoW are important to the given project they are working on.

	'''Risk of vague and generic detailing'''		'''Risk of vague and generic detailing'''

Abiha: /* Annotated Bibliography */

2023-05-09T20:19:13Z

Annotated Bibliography

← Older revision		Revision as of 20:19, 9 May 2023
Line 272:		Line 272:
	'''Martin, M. G. (1998). Statement of work: the foundation for delivering successful service projects. PM Network, 12(10), 54–57.'''		'''Martin, M. G. (1998). Statement of work: the foundation for delivering successful service projects. PM Network, 12(10), 54–57.'''

	This paper discusses the importance of having a detailed SoW for project managers and customers in order to prevent project failure. Martin, M. G. discusses how the SoW establishes the foundation of the project and how it helps provide all parties with a measurement of work that is ~~satisfactorily~~ completed.		This paper discusses the importance of having a detailed SoW for project managers and customers in order to prevent project failure. Martin, M. G. discusses how the SoW establishes the foundation of the project and how it helps provide all parties with an objective measurement of work that is completed throughout the project.

	'''Friedman, S. (2008). Roles, responsibilities, and resources: best practices in managing people. Paper presented at PMI® Global Congress 2008—North America, Denver, CO. Newtown Square, PA: Project Management Institute.'''		'''Friedman, S. (2008). Roles, responsibilities, and resources: best practices in managing people. Paper presented at PMI® Global Congress 2008—North America, Denver, CO. Newtown Square, PA: Project Management Institute.'''

Abiha: /* Annotated Bibliography */

2023-05-09T20:17:59Z

Annotated Bibliography

← Older revision		Revision as of 20:17, 9 May 2023
Line 262:		Line 262:
	To obtain additional information on this topic, it is recommended to read the key references in the annotated bibliography.		To obtain additional information on this topic, it is recommended to read the key references in the annotated bibliography.

	'''A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed.~~) (2017~~). Project Management Institute.'''		'''Project Management Institute. (2017). A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed.). Project Management Institute.'''

	The Project Management Body of Knowledge (PMBOK Guide) is a collection of project management processes, best practices, terminologies, and guidelines. To gain additional insight on some of the topics that haven't been elaborated further in this article, the reader can with advantage look up the different topics in this book.		The Project Management Body of Knowledge (PMBOK Guide) is a collection of project management processes, best practices, terminologies, and guidelines. To gain additional insight on some of the topics that haven't been elaborated further in this article, the reader can with advantage look up the different topics in this book.

Abiha: /* Conclusion */

2023-05-09T20:17:28Z

Conclusion

← Older revision		Revision as of 20:17, 9 May 2023
Line 255:		Line 255:
	To summarize, this wiki article has extensively addressed the phenomenon of scope creep, exploring its meaning and underlying causes. Additionally, the article has explained the importance of the Statement of Work (SoW) and its essential components. Although there exists no universal one-size-fits-all approach for developing a SoW, the article has recommended practical suggestions on the sections that a SoW should contain. This wiki article has also highlighted the significance of concise language and the influence of project complexity on the SoW. Finally, the article has culminated in a tabular representation of the causes of scope creep mentioned earlier, along with strategies for mitigating them and assessing the extent to which the SoW document fulfills those mitigation measures.		To summarize, this wiki article has extensively addressed the phenomenon of scope creep, exploring its meaning and underlying causes. Additionally, the article has explained the importance of the Statement of Work (SoW) and its essential components. Although there exists no universal one-size-fits-all approach for developing a SoW, the article has recommended practical suggestions on the sections that a SoW should contain. This wiki article has also highlighted the significance of concise language and the influence of project complexity on the SoW. Finally, the article has culminated in a tabular representation of the causes of scope creep mentioned earlier, along with strategies for mitigating them and assessing the extent to which the SoW document fulfills those mitigation measures.

	[[File:Reqreq.png\|center\|~~700px~~\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]		[[File:Reqreq.png\|center\|600px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]

	As seen in the above table, the scope creep can be mitigated through actions that are fulfilled by a SoW document, such as defining deliverables, reviewing requirements with stakeholders, incorporating a RACI chart, etc. However, some of the other cause to scope creep requires additional actions besides incorporating a SoW document, such as the development of a project status reporting tool and educating sponsors to chunk the project into shorter subprojects. The SoW document may not mitigate all the causes of scope creep but is a significant tool in preventing it, which is why it is recommended as an essential tool for project managers.		As seen in the above table, the scope creep can be mitigated through actions that are fulfilled by a SoW document, such as defining deliverables, reviewing requirements with stakeholders, incorporating a RACI chart, etc. However, some of the other cause to scope creep requires additional actions besides incorporating a SoW document, such as the development of a project status reporting tool and educating sponsors to chunk the project into shorter subprojects. The SoW document may not mitigate all the causes of scope creep but is a significant tool in preventing it, which is why it is recommended as an essential tool for project managers.

Abiha: /* Annotated Bibliography */

2023-05-09T20:17:01Z

Annotated Bibliography

← Older revision		Revision as of 20:17, 9 May 2023
Line 260:		Line 260:

	== Annotated Bibliography ==		== Annotated Bibliography ==
	To obtain additional information on this topic, it is recommended ~~that~~ read the key references in the annotated bibliography.		To obtain additional information on this topic, it is recommended to read the key references in the annotated bibliography.

	'''A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed.) (2017). Project Management Institute.'''		'''A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed.) (2017). Project Management Institute.'''

Abiha: /* Annotated Bibliography */

2023-05-09T20:16:48Z

Annotated Bibliography

← Older revision		Revision as of 20:16, 9 May 2023
Line 260:		Line 260:

	== Annotated Bibliography ==		== Annotated Bibliography ==
	It is recommended that ~~the reader takes a look at~~ the key references in the annotated bibliography ~~to obtain additional information on this topic~~.		To obtain additional information on this topic, it is recommended that read the key references in the annotated bibliography.

	'''A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed.) (2017). Project Management Institute.'''		'''A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed.) (2017). Project Management Institute.'''

Abiha: /* Conclusion */

2023-05-09T20:16:17Z

Conclusion

← Older revision		Revision as of 20:16, 9 May 2023
Line 257:		Line 257:
	[[File:Reqreq.png\|center\|700px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]		[[File:Reqreq.png\|center\|700px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]

	As seen in the above table, the scope creep can be mitigated through actions that are fulfilled by a SoW document, such as defining deliverables, reviewing requirements with stakeholders, incorporating a RACI chart, etc. However, some of the other cause to scope creep requires additional actions besides incorporating a SoW document, such as the development of a project ~~charter~~ and educating sponsors to chunk the project into shorter subprojects. The SoW document may not mitigate all the causes of scope creep but is a significant ~~factor~~ in preventing it, which is why it is recommended as an essential tool for project managers.		As seen in the above table, the scope creep can be mitigated through actions that are fulfilled by a SoW document, such as defining deliverables, reviewing requirements with stakeholders, incorporating a RACI chart, etc. However, some of the other cause to scope creep requires additional actions besides incorporating a SoW document, such as the development of a project status reporting tool and educating sponsors to chunk the project into shorter subprojects. The SoW document may not mitigate all the causes of scope creep but is a significant tool in preventing it, which is why it is recommended as an essential tool for project managers.

	== Annotated Bibliography ==		== Annotated Bibliography ==

Abiha: /* Conclusion */

2023-05-09T20:15:06Z

Conclusion

← Older revision		Revision as of 20:15, 9 May 2023
Line 253:		Line 253:
	== Conclusion ==		== Conclusion ==

	To summarize, this wiki article has extensively addressed the phenomenon of scope creep, exploring its meaning and underlying causes. Additionally, the article has explained the importance of the Statement of Work (SoW) and its essential components. Although there exists no universal one-size-fits-all approach for developing a SoW, the article has recommended practical suggestions on the sections that a SoW should contain. This wiki article has also highlighted the significance of concise language and the influence of project complexity on the SoW. Finally, the article has culminated in a tabular representation of the causes of scope creep mentioned earlier, along with strategies for mitigating them and assessing the extent to which the SoW fulfills those mitigation measures.		To summarize, this wiki article has extensively addressed the phenomenon of scope creep, exploring its meaning and underlying causes. Additionally, the article has explained the importance of the Statement of Work (SoW) and its essential components. Although there exists no universal one-size-fits-all approach for developing a SoW, the article has recommended practical suggestions on the sections that a SoW should contain. This wiki article has also highlighted the significance of concise language and the influence of project complexity on the SoW. Finally, the article has culminated in a tabular representation of the causes of scope creep mentioned earlier, along with strategies for mitigating them and assessing the extent to which the SoW document fulfills those mitigation measures.

	[[File:Reqreq.png\|center\|700px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]		[[File:Reqreq.png\|center\|700px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]

Abiha: /* Conclusion */

2023-05-09T20:14:12Z

Conclusion

← Older revision		Revision as of 20:14, 9 May 2023
Line 253:		Line 253:
	== Conclusion ==		== Conclusion ==

	To summarize, this wiki article has extensively addressed the phenomenon of scope creep, exploring its meaning and underlying causes. Additionally, the article has explained the importance of the Statement of Work (SoW) and its essential components. Although there exists no universal one-size-fits-all approach for developing a SoW, the article has recommended practical suggestions on the sections that a SoW should contain~~, along with guidance on structuring each segment~~. This wiki article has also highlighted the significance of concise language and the influence of project complexity on the SoW. Finally, the article has culminated in a tabular representation of the causes of scope creep mentioned earlier, along with strategies for mitigating them and assessing the extent to which the SoW fulfills those mitigation measures.		To summarize, this wiki article has extensively addressed the phenomenon of scope creep, exploring its meaning and underlying causes. Additionally, the article has explained the importance of the Statement of Work (SoW) and its essential components. Although there exists no universal one-size-fits-all approach for developing a SoW, the article has recommended practical suggestions on the sections that a SoW should contain. This wiki article has also highlighted the significance of concise language and the influence of project complexity on the SoW. Finally, the article has culminated in a tabular representation of the causes of scope creep mentioned earlier, along with strategies for mitigating them and assessing the extent to which the SoW fulfills those mitigation measures.

	[[File:Reqreq.png\|center\|700px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]		[[File:Reqreq.png\|center\|700px\|Figure 5: Mitigating Actions Fulfilled by The SoW.]]