Project assumptions A project assumption is anything that is held to be true but not proven to be true.
Project boundaries A project boundary clearly states what is included with the project and what's excluded from the project. This helps to eliminate assumptions between the project management team and the project customer.
Project constraints A constraint is anything that limits the project manager's options. Consider a predetermined budget, deadline, resources, or materials the project manager must use within the project—these are all examples of project constraints.
Project objectives These are the measurable goals that determine a project's acceptability by the project customer and the overall success of the project. Objectives often include the cost, schedule, technical requirements, and quality demands.
Project requirements These are the demands set by the customer, regulations, or the performing organization that must exist for the project deliverables to be acceptable. Requirements are often prioritized in a number of ways, from must have, should have, and would like to have.
Project scope This defines all of the work, and only the required work, to complete the project objectives.
Project scope management plan This project management subsidiary plan controls how the scope will be defined, how the project scope statement will be created, how the WBS will be created, how scope verification will proceed, and how the project scope will be controlled throughout the project.
Schedule milestones The project customer may have specific dates when phases of the project should be completed. These milestones are often treated as project constraints.
Scope creep Undocumented, unapproved changes to the project scope.
Scope verification The formal inspection of the project deliverables, which leads to project acceptance.
Stakeholder analysis A scope definition process where the project management team interviews the stakeholders and categorizes, prioritizes, and documents what the project customer wants and needs. Stakeholder analysis demands quantification of stakeholder objectives; goals such as "good," "satisfaction," and "speedy" aren't quantifiable.
Systems engineering This project scope statement creation process studies how a system should work, designs and creates a system model, and then enacts the working system based on the project's goals and the customer's expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the project.
Systems analysis A scope definition approach that studies and analyzes a system, its components, and the relationship of the components within the system.
Value analysis Like value engineering, this approach examines the functions of the project's product in relation to the cost of the features and functions. This is where, to some extent, the grade of the product is in relationship to the cost of the product.
Value engineering This project scope statement creation approach attempts to find the correct level of quality in relation to a reasonable budget for the project deliverable while still achieving an acceptable level of performance of the product.
WBS dictionary A WBS companion document that defines all of the characteristics of each element within the WBS.
WBS template A pre-populated WBS for repetitive projects. Previous projects' WBSs are often used as templates for current similar projects.
Work breakdown structure (WBS) A deliverables-orientated breakdown of the project scope.
Work package The smallest item in the WBS.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.