Best writers. Best papers. Let professionals take care of your academic papers

Order a similar paper and get 15% discount on your first order with us
Use the following coupon "FIRST15"
ORDER NOW

Purdue University product scope discussion

In addition, you must also post at least one substantive reply to a colleague’s post. 200 to 300 words.Submit a professional response that demonstrates critical thinking, problem-solving, and knowledge synthesis.When citing resources, don’t forget to use in-text citations and a reference citation at the end using proper APA style. Please consult Purdue’s Online Writing Lab (OWL) website or your APA guide to assist you. See: OWL APA Style Guide for assistance.

Product scope is the sum of all the features and functions of a product, service, or a result (Sonkiya, 2016, para. 3). On the other hand, “project scope is the work that delivers the product” (Usmani, 2018, “The Difference” section, para. 1). If we think back to our ACME Inc breakroom project, the product scope included required features from the company CEO and Ad Hoc committee. Features such as having so many tables and chairs, flat screen televisions, couches, etc., were all requirements that helped in defining the scope for the overall product, a newly renovated breakroom. While the product scope fully defines what is to be delivered to the customer/sponsor, it doesn’t indicate how the project team will deliver the product. As the above definition implies, the project scope includes the different steps necessary to deliver the final product, service, or in the exampled used, a renovated breakroom. Project scope on the ACME project may include identifying activities to be performed, dependencies, schedule creation, cost estimates, resource allocation, procurements and so on (Shenoy, n.d.). In short Sonkiya (2016) concludes “the Product Scope defines the solution itself, and the Project Scope says how to get that solution” (para. 12).

Before the scope of a project can be defined, project teams capture requirements from stakeholders in a variety of ways:

  • Interviews
  • Focus Groups
  • Facilitated Workshops
  • Questionnaires and Surveys
  • Observations
  • Prototypes
  • Benchmarking (PMI, 2013).

Before being baselined, requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders (PMI, 2013, p. 117). These requirements are well documented and act as input into defining the scope of a project. Expert judgment, product analysis, alternative generation, and facilitated workshops are some of the tools and techniques used in selecting the final project requirements. These final requirements are then used to create the project scope statement. Teams then use a work breakdown structure (WBS) to breakdown project deliverables and work into more manageable components (PMI, 2013). The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables(PMI, 2013, p. 126). Teams may also use story maps as a way of tracking and communicating project scope or burn-up charts to illustrate the required projected timeline and costs to complete the given scope (Raman and Nandakumar, 2014).

Scope creep occurs when the customer or stakeholders change or add new requirements to an already defined scope of a project. Since these new requirements weren’t initially included in the overall project plan, scope creep typically impacts other constraints such as time and cost negatively. A formal change control process is one way of controlling changes to a projects scope baseline (PMI, 2013). However, project managers can potentially prevent scope creep by creating a well-defined scope of work, having planned responses to project change requests regarding scope, and maintaining active communication with the customer and stakeholders (MBO Partners, 2018).

References

MBO Partners. (2018). 6 tips to prevent scope creep. Retrieved from https://www.mbopartners.com/blog/how-grow-small-bu…

PMI. (2013). A guide to the project management body of knowledge (5th ed.). Newton Square: Project Management Institute, Inc.

Raman, N. & Nandakumar, M. (2014). 5 tips for effective scope management. Retrieved from https://www.thoughtworks.com/insights/blog/tips-ef…

Shenoy, S. (n.d.). Project scope versus product scope. Retrieved from https://www.pmexamsmartnotes.com/project-scope-vs-…

Sonkiya, S. (2016). Product scope vs project scope. iZenBridge. Retrieved from https://www.izenbridge.com/blog/product-scope-vs-p…

Usmani, F. (2018). Product scope vs project scope. Retrieved from https://pmstudycircle.com/2012/01/product-scope-vs…


0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *