Discuss the elements of the Project Scope Checklist in some appropriate detail. Do not merely list the items for the Project Scope checklist, but discuss each of them in detail.
Please be thorough and comprehensive in your response to this topical question.
You do NOT have to make a response to another student, so focus on your own discussion board post to ensure that it is thorough, complete and accurate. Ensure that you have met the minimum word count. Use parenthetical citations to the textbook at the points at which you use materials – paraphrased or directly quoted from the textbook.
Your discussion post should be at least 500 words. Please be thorough and comprehensive in your response to this topical question.
Use a MINIMUM OF 3 AUTHORITATIVE RESOURCES ON YOUR REFERENCES LIST (one of which will be the textbook). USE PARENTHETICAL CITATIONS THROUGHOUT YOUR POST at the point at which you use materials (quoted or paraphrased) from your sources. Label your list of resources as the “References� list.
The proper Reference for the textbook for your References list:
Larson, E. W., & Gray, C. F. (2021). Project management: the managerial process. McGraw-Hill Education.
The correct parenthetical citation is: (Larson & Gray, 2021) for paraphrased materials or (Larson & Gray, 2021, p. 123) for a direct quote from a specific page.Discuss the elements of the Project Scope Checklist in some appropriate detail. Do not merely list the items for the Project Scope checklist, but discuss each of them in detail.
Main resource:
1. Project objective. The first step of project scope definition is to define the overall objective to meet your customer’s need(s). For example, as a result of extensive market research a computer software company decides to develop a program that automatically translates verbal sentences in English to Russian. The project should be completed within three years at a cost not to exceed $1.5 million. Another example is to design and construct a portable hazardous-waste thermal treatment system in 13 months at a cost not to exceed $13 million. The project objective answers the questions of what, when, how much, and at times where.
2. Product scope description. This step is a detailed description of the characteristics of the product, service, or outcome of the project. The description is progressively elaborated throughout the project. The product scope answers the question “What end result is wanted?� For example, if the product is a cell phone, its product scope will be its screen size, battery, processor, camera type, memory, and so on.
3. Justification. It is important that project team members and stakeholders know why management authorized the project. What is the problem or opportunity the project is addressing? This is sometimes referred to as the business case for the project, since it usually includes cost/benefit analysis and strategic significance. For example, on a new-release project, the justification may be an expected ROI of 30 percent and an enhanced reputation in the marketplace.
4. Deliverables. The next step is to define major deliverables—the expected, measurable outputs over the life of the project. For example, deliverables in the early design phase of a project might be a list of specifications. In the second phase deliverables might be software coding and a technical manual. The next phase might be the prototype. The final phase might be final tests and approved software. Note: Deliverables and requirements are often used interchangeably.
5. Milestones. A milestone is a significant event in a project that occurs at a point in time. The milestone schedule shows only major segments of work; it represents first, rough-cut estimates of time, cost, and resources for the project. The milestone schedule is built using the deliverables as a platform to identify major segments of work and an end date—for example, testing complete and finished by July 1 of the same year. Milestones should be natural, important control points in the project. Milestones should be easy for all project participants to recognize.
6. Technical requirements. More frequently than not, a product or service will have technical requirements to ensure proper performance. Technical requirements typically clarify the deliverables or define the performance specifications. For example, a technical requirement for a personal computer might be the ability page 109to accept 120-volt alternating current or 240-volt direct current without any adapters or user switches. Another well-known example is the ability of 911 emergency systems to identify the caller’s phone number and the location of the phone. Examples from information systems projects include the speed and capacity of database systems and connectivity with alternative systems. For understanding the importance of key requirements, see Snapshot from Practice 4.1: Big Bertha ERC II versus the USGA’s COR Requirement.
7. Limits and exclusions. The limits of scope should be defined. Failure to do so can lead to false expectations and to expending resources and time on the wrong problem. The following are examples of limits: work on-site is allowed only page 110between the hours of 8:00 p.m. and 5:00 a.m.; system maintenance and repair will be done only up to one month after final inspection; and the client will be billed for additional training beyond that prescribed in the contract. Exclusions further define the boundary of the project by stating what is not included. Examples include: data will be collected by the client, not the contractor; a house will be built, but no landscaping or security devices added; software will be installed, but no training given.
8. Acceptance criteria. Acceptance criteria are a set of conditions that must be met before the deliverables are accepted. The following are examples: all tasks and milestones are complete, new service processes begin with a less than 1 percent defect rate, third-party certification is required, and customer on-site inspection is required.
Scope statements are twofold. There is a short, one- to two-page summary of key elements of the scope, followed by extended documentation of each element (e.g., a detailed milestone schedule or risk analysis report). See Snapshot from Practice 4.2: Scope Statement for an example of a summary page.
The project scope checklist in Step 1 is generic. Different industries and companies will develop unique checklists and templates to fit their needs and specific kinds of projects. A few companies engaged in contracted work refer to scope statements as “statements of work (SOWs).� Other organizations use the term project charter. However, the term project charter has emerged to have a special meaning in the world of project management. A project charter is a document that authorizes the project manager to initiate and lead the project. This document is issued by upper management and provides the project manager with written authority to use organizational resources for project activities. Often the charter will include a brief scope description as well as such items as risk limits, business case, spending limits, and even team composition.