■ 1.4 Given a scope definition scenario, demonstrate awareness of the need to get written confirmation of customer expectations in the following areas: o The background of the project (e.g., a problem/opportunity statement, strategic alignment with organizational goals and other initiatives, why the project is being initiated at this time, etc.)
o The deliverable from the project (i.e., what the product will look like, be able to do, who will use it, etc.) o The strategy for creating the deliverable o Targeted completion date and rationale behind that date o Budget dollars available and basis upon which that budget was determined o Areas of risks which the project client is or is not willing to accept o The priority of this project as it relates to all other projects being done within the organization o The sponsor of the project (i.e., who will provide direction and decisions) o Any predetermined tools or resources o Assumptions that resources will be available as needed
■ 1.5 Given a project scope definition scenario, including a confirmed high-level scope definition and project justification, demonstrate the ability to identify and define the following elements:
■ The stakeholders, including the primary project client, the ultimate end users and any other impacted parties (internal or external to the organization), their roles and special needs
■ An all-inclusive set of requirements presented in specific, definitive terms which include:
o Eifferentiation of mandatory versus optional requirements o Success criteria upon which the deliverable will be measured o Completion criteria (for example: what needs to be delivered; such as a fully tested system or a system after being live for three months)
o Requirements that are excluded from the project ■ Targeted completion date, including:
o Relative to a specified start date o Expressed as: 1) a specific date (i.e., mm/dd/yy), 2) a range of dates, or 3) a specific quarter and year (third quarter 2000) o The consequences if that date is not met o A milestone chart including any phase reviews, if appropriate
■ Anticipated budget, including any or all of the following:
o Plus or minus tolerance o Contingency funds and/or any management reserves, if negotiated o The consequences if that budget is not met
■ Which of the above three criteria—for example, technical performance (quality), completion date (schedule), or anticipated budget—is the highest priority to the project client
■ All assumptions made relative to a through e above
■ 1.6 Given a project scope definition scenario, including the client's highest priority between quality, time, and budget, estimate any or all of the following:
■ The potential impact of satisfying the client's highest priority at the expense of the other two
■ Worse case scenario targeted completion date, budget, and quality-level
■ Your confidence level in the projected completion date, budget, and prospects for a high-quality deliverable
■ 1.7 Given a scope definition scenario, recognize and explain the need to investigate specific industry regulations requirements for their impact on the project scope definition and project plan.
Projects begin with the project concept definition and the project charter, but they're fleshed out with the evaluation and shaping of the project's scope. In this chapter, we'll assess the things that go into the formulation of an accurate project scope. I will define what a project scope document is and examine its elements, as well as the famous project management equilibrium: time, quality, and budget. We will revisit our Prestige Hotels project by gathering its key elements and presenting them in a scope document. The presentation of that document will help you to solidify some of the more intangible parts of initiating a project. Finally, I ' l l talk about any regulations or requirements that may enhance or detract from the project ' s scope.
By the time you get ready to formulate the scope of the project, the project manager (PM) has been appointed via charter and some key team members may have already been assigned. Project meetings with the customer will now begin in order to ascertain the scope. This is the appropriate time for the customer and project team to work together to reach a common, detailed understanding of what the project is and, more importantly, what it isn't. A great way to kick off this meeting is to have the customer give an overview of the project in 25 words or less. This little exercise accomplishes two things:
■ It exposes the key functionalities of the deliverables that the customer is looking for.
■ It helps shape the definition of a successful project.
Tip Many times, customers think the project scope definition step is a waste of time. The project is already approved, so we ' re well under way, right? Actually, aside from the project plan formulation phase, this component is the most important part of the entire project, because it determines the project' s likelihood of success. It' s a predictor, because the granularity with which you write the scope document dictates how well you' ve fleshed out the project ' s requirements and thus understand what' s involved.
Was this article helpful?