click below
click below
Normal Size Small Size show me how
C722 - module 18, 19
Project Management
Term | Definition |
---|---|
project charter's | most important function is that it authorizes the project. It is, essentially, the contract document showing the agreement by the key stakeholders. Without this, no work on the project can occur |
project scope | checklist, statement of work, work breakdown structure, living documents |
checklist | are one way of monitoring that activities and tasks have been addressed |
statement of work | provide much more detailed descriptions of what must be planned |
work breakdown structure | details each activity that must be completed |
living documents | are all planning documents. This means that they all need to be periodically reviewed to ensure that the plans are still valid. Approved changes are possible at any time in the project life cycle and can cause plans to change |
product scope | is used to describe the portion of the scope statement that defines the features and functions of the project outcome or deliverables. This is often equated to the "what" of project management, meaning "what will the project create |
make / buy decision | do the work yourself, or hire out |
project requirements | is a characteristic, function, or capability that must be present in the project final outcome |
requirements traceability matrix | this not only includes the requirement, but it also identifies the business need that will be satisfied and the specific stakeholder who provided the requirement |
project deliverables | are the features and functions of the project outcome that form the product scope |
resource responsibility matrix | The required items of education, experience, skills, and abilities are dependent on the specific roles and responsibilities of each project team member |
histogram | is a graph of a frequency distribution in which rectangles with bases on the horizontal axis are given widths equal to the class intervals and heights equal to the corresponding frequencies |
resource levelling | is the process of minimizing the variation in need of a specific resource over several time periods. |
Knowledge, Skills, and Abilities (KSA) | The skills required by the project team is a key question for the project manager |
purpose of WBS | is a methodical deconstruction of deliverables into activities and then tasks to be performed |
deliverable | is a specific product or functionality that the project will provide. Deliverables can be the final outcome of a project or intermediate outcomes that are integrated into the final project outcome |
activity | is a portion of work that will be executed as part of the project to create the specified deliverables |
task | is often used to describe specific actions taken to complete an activity |
8/80 rule | do not assign anything that takes less than 8 hours, allow sufficient work to occupy them and you do not micromanage. This is essentially one business day. You do not want to assign a task that takes more than 80 hours or two work weeks to complete |
hierarchical numbering | One is a WBS number as a coding scheme used to associate tasks to activities, to deliverables, and finally to the overall project and program. |