Module 12 Terms Flashcards
Statement of Work
The project scope (or scope statement, or statement of scope) is, simply put, what the result of the project is desired to be. It defines the product of the project. It is sometimes referred to as the statement of work (SOW). A scope statement includes:
Project objectives Project deliverables Product acceptance criteria Technical requirements Project limits and exclusions Project milestones Project constraints Project assumptions
Scope
The project scope (or scope statement, or statement of scope) is, simply put, what the result of the project is desired to be. It defines the product of the project. It is sometimes referred to as the statement of work (SOW). A scope statement includes:
Project objectives Project deliverables Product acceptance criteria Technical requirements Project limits and exclusions Project milestones Project constraints Project assumptions A well-written scope will clearly define every aspect of the project including functions and features, quality expectations, and time constraints. There will be no ambiguity and nothing left to interpretation.
Time
It is important to understand that there are two usages of time when thinking about the project. First, there is the calendar time when something will be available. This refers to a date or time of day. Then there is work time required to produce or procure the item. This translates into hours (time used) of labor or hours of equipment and facilities used. This time used is converted into dollars spent and directly impacts our cost side of the triple constraint.
Cost
Cost also goes back to the scope which defines functions and each function has costs associated with it. In the case of the triple constraint, cost is the dollar expression of scope and time with an addition for money to be spent on meeting quality expectations. The triple constraint often speaks to schedule but must include time used (hours billed) in order to understand budget and cost. So, in terms of the triple constraint, both usages of time are important.
In your project of starting a restaurant, you want the restaurant built quickly because you cannot begin generating revenue until you have an operating business with customers. There is a maximum amount of money you have available. And, you know that to keep customers happy and coming back, you have to serve good food (function), prepare the food well (quality), serve food in a reasonable amount of time (time), and provide a venue with comfortable seating in a pleasant atmosphere—all function and quality issues that could cost money and time. How do you balance these three constraints?
As the owner of the restaurant, you want a high-end Mexican eatery, not a taco stand. This is a scope or functional requirement. When you choose higher end food, costs will go up and perhaps preparation time will increase, so all three of the triple constraints will be impacted.
Scope Creep
Scope creep must be avoided. This issue is dangerous to the health of the project. Scope creep occurs when there are any—but particularly small—incremental additions to the project scope that are not subject to the formal scope change process. This occurs because the scope was not well written due to oversights or limited understanding. As you move through the project, you get more knowledgeable and your understanding gets better, and often you learn things you did not know at the start.
Ambiguities in the initial information or new information can lead to scope creep. Any items that are not clearly and completely defined can lead to scope creep. Over time, if the project scope escalates and work is being performed that was not originally budgeted, it puts a strain on all project resources and can cause the project to run over budget, behind schedule, or have lower quality.
Instead of allowing scope creep, iterative planning is sometimes used.
Scope Reduction
For any real-time savings, the scope must be reduced. Some features of the project may be postponed or eliminated.
To meet a sooner due date, you need to reduce scope or functions or increase resources, thus increasing costs. The concept around triple constraint is that no decision can be made without looking at impact on the project and its quality. Interrelationships are vital when making a decision.
Project Baseline
There is an old saying, “If you do not know where you are going, how will you know when you get there?” That is basically what a project baseline tells you. It establishes the expected scope, the expected cost, and the expected schedule. If you know the baseline, you can tell when you deviate from it.
Project Quality
Being an equilateral triangle, all sides are equal in length, symbolizing that scope, cost, and schedule are “balanced.” The area inside the triangle represents the level of quality. And, with the scope, cost, and schedule as shown, you get the quality desired.
