Difference between revisions of "What Project Work Is"

From CNM Wiki
Jump to: navigation, search
(→‎Closing)
 
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[File:Cnm-digital.png|400px|thumb|right|[[CNM Cyber suite]]s]][[What Project Work Is]] (hereinafter, the ''Lectio'') is the [[lectio|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]].
+
[[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]][[What Project Work Is]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of '''[[Project Work Essentials]]''' [[lesson]] that introduces its participants to [[project management]] concepts. This ''lesson'' belongs to the ''CNMCT Entrance'' section of [[CNMCyber Bootcamps]].
  
  
 
==Content==
 
==Content==
−
The predecessor [[lectio]] is [[Nature of Projects]].
+
The predecessor [[lectio]] is [[Agile vs Waterfall Work]].
  
 
===Script===
 
===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.
+
:[[Project work]] is the aggregate of the work that must be done to complete a [[project]].
  
−
:Project work can be divided in 4 phases. The initiating phase stops when the need of the project is realized, the source of its budget is identified, and at least one person on each side of the project work is personalized. The planning phase stops when [[project baseline]]s are approved. The executing phase stops when the ''customer'' or customer's representative accepts the ''work product''. The closing phase ends when all the deliverables are delivered and all the payments are made.
+
:In [[Waterfall project]]s, the [[project customer]] separately approves the work in the [[project executing]] stage. A separate term, [[project scope]], is used for this work only.
  
−
:Among all, the executing phase tends to be the costliest. In this phase, workers are hired and supplies are purchased.
+
:For big, expensive, and predictable executions, the ''project scope'' is decomposed and presented as [[work breakdown structure]] or [[WBS]]. This document may be accompanied by a [[WBS dictionary]], which further describes ''WBS'' items.
  
−
: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.
+
:In [[project management]], the ''project scope'' becomes the [[project 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.''
  
−
:Unless a ''project'' is [[Agile project|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 addition to ''WBS'' and ''WBS dictionary'', a ''project scope baseline'' also includes [[acceptance criteria]] as a separate document or 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 [[request for change]] to 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''.
  
−
:Similarly, the project phases may or may not be consecutive; they also may be overlapping. For instance, if the ''project manager'' quits before the project closure, the initiating phase should be re-open even after the executing phase is complete and a new project manager should be appointed. All the phases entirely end when the closing phase ends. If anything is needed afterwards, a new project should be established.
+
:As a general tendency, the smaller a project, the fewer documents its ''customer'' requires. For some ''customers'', ''acceptance criteria'' satisfy all the needs.
  
−
:''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''.
+
:Some ''customers'', like [[CNMCyber Team]], provide contractors with detailed product descriptions. If not, ''project managers'' or [[business analyst]]s collect [[requirement]]s from [[project stakeholder]]s starting with the ''customer'' or ''customer's representatives''. If the target deliverable is complex, [[systems engineer]]s design solutions.
  
−
:Some ''customers'', like [[CNM Cyber Team]], provide contractors with detailed product descriptions. If not, ''project managers'' or [[business analyst]]s collect [[requirement]]s from [[project stakeholder]]s starting with the ''customer'' or ''customer's representatives''. If the target deliverable is complex, [[systems engineer]]s design solutions.
+
:Product descriptions are not necessarily textual documents. [[Prototype]]s 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 while recreating functions and features of that original system.
  
−
:Product descriptions are not necessarily textual documents. [[Prototype]]s 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.
+
:In [[Agile project]]s, the [[project scope]] is rarely documented at all. The [[project executing]] starts when the [[product backlog]] is approved. This ''backlog'' serves a role of the [[product scope]] and developers makes decisions of what work they should do based on that scope. While the ''Agile project'' progresses, the ''product scope'' is further defined.
  
 
===Key terms===
 
===Key terms===
−
:[[Product scope]], [[project scope]]
+
:[[Project work]], [[project scope]], [[work breakdown structure]] ([[WBS]]), [[WBS dictionary]], [[project scope baseline]], [[project scope statement]], [[request for change]], [[product scope]], [[solution scope]], [[prototype]]
  
 
===Closing===
 
===Closing===
−
:
+
:;Fill in the blank
 +
::To create a project scope to plan your work, you have to have a description of the future _________.
  
−
The successor [[lectio]] is '''[[Parties of Project Work]]'''.
+
The successor [[lectio]] is '''[[Project Parties and Roles]]'''.
  
 
==Presentations==
 
==Presentations==

Latest revision as of 02:56, 21 October 2023

CNMCyber suites

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 CNMCyber Bootcamps.


Content

The predecessor lectio is Agile vs Waterfall Work.

Script

Project work is the aggregate of the work that must be done to complete a project.
In Waterfall projects, the project customer separately approves the work in the project executing stage. A separate term, project scope, is used for this work only.
For big, expensive, and predictable executions, the project scope is decomposed and presented as work breakdown structure or WBS. This document may be accompanied by a WBS dictionary, which further describes WBS items.
In project management, the project scope becomes the project 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.
In addition to WBS and WBS dictionary, a project scope baseline also includes acceptance criteria as a separate document or a part of a project scope statement. In addition to the 'criteria, this statement summarizes WBS and explains why particular works are included.
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 request for change to 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.
As a general tendency, the smaller a project, the fewer documents its customer requires. For some customers, acceptance criteria satisfy all the needs.
Some customers, like CNMCyber 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 while recreating functions and features of that original system.
In Agile projects, the project scope is rarely documented at all. The project executing starts when the product backlog is approved. This backlog serves a role of the product scope and developers makes decisions of what work they should do based on that scope. While the Agile project progresses, the product scope is further defined.

Key terms

Project work, project scope, work breakdown structure (WBS), WBS dictionary, project scope baseline, project scope statement, request for change, product scope, solution scope, prototype

Closing

Fill in the blank
To create a project scope to plan your work, you have to have a description of the future _________.

The successor lectio is Project Parties and Roles.

Presentations

Slideshow

Video

Retrieved from "https://pravka.bskol.com/w/index.php?title=What_Project_Work_Is&oldid=119308"