Difference between revisions of "What Project Work Is"
(→Content) |
(→Script) |
||
| Line 15: | Line 15: | ||
:Life is life, things happen, and no project can be fully predicted. If any of project baselines cannot be met, a ''project manager'' makes a [[change request]] for the ''customer'' or ''customer's'' representative to approve, decline, or modify. | :Life is life, things happen, and no project can be fully predicted. If any of project baselines cannot be met, a ''project manager'' makes a [[change request]] for the ''customer'' or ''customer's'' representative to approve, decline, or modify. | ||
| − | |||
| − | |||
:''Project scopes'' derive from detailed descriptions of the target [[work product]]s and their specified features and functions. Logically, what needs to be done must be defined before the list of what to do. Sometimes, these detailed descriptions of the product are called [[product scope]]s. In [[business analysis]], they are called [[solution scope]]s. [[Acceptance criteria]] is the most important description of ''product scope''. | :''Project scopes'' derive from detailed descriptions of the target [[work product]]s and their specified features and functions. Logically, what needs to be done must be defined before the list of what to do. Sometimes, these detailed descriptions of the product are called [[product scope]]s. In [[business analysis]], they are called [[solution scope]]s. [[Acceptance criteria]] is the most important description of ''product scope''. | ||
Revision as of 21:24, 26 November 2020
What Project Work Is (hereinafter, the Lectio) is the lesson part of Project Work Essentials lesson that introduces its participants to project management concepts. This lesson belongs to the CNMCT Entrance section of the CNM Cyber Placement.
Content
The predecessor lectio is Phases and Sub-Projects.
Script
- The aggregate of the work that must be completed to deliver a work product is called project scope. Consequently, project scope is all of the project work.
- For big, expensive, and predictable executions, the project work is decomposed and presented as work breakdown structure or WBS. This document may be accompanied by a WBS dictionary, which further describes WBS items.
- Unless a project is Agile, acceptance criteria are a must. They may be presented as a separate document or be a part of a project scope statement. In addition to the 'criteria, this statement summarizes WBS and explains why particular works are included.
- In project management, the project scope becomes the scope baseline when and if the customer or customer's representative approves it. Unless the customer or its representative agrees on something else, a project manager shouldn't start any execution of the project without the baseline.
- Life is life, things happen, and no project can be fully predicted. If any of project baselines cannot be met, a project manager makes a change request for the customer or customer's representative to approve, decline, or modify.
- Project scopes derive from detailed descriptions of the target work products and their specified features and functions. Logically, what needs to be done must be defined before the list of what to do. Sometimes, these detailed descriptions of the product are called product scopes. In business analysis, they are called solution scopes. Acceptance criteria is the most important description of product scope.
- Some customers, like CNM Cyber Team, provide contractors with detailed product descriptions. If not, project managers or business analysts collect requirements from project stakeholders starting with the customer or customer's representatives. If the target deliverable is complex, systems engineers design solutions.
- Product descriptions are not necessarily textual documents. Prototypes can possibly do even a better job. For instance, one amateur coder wrote the original user management system of WorldOpp Middleware. The current code was created using that first system as a prototype.
Key terms
Closing
The successor lectio is Nature of Projects.
