Difference between revisions of "CNMCyber Coordinator"

From CNM Wiki
Jump to: navigation, search
(Clarifying the project)
 
Line 1: Line 1:
Any [[CNM Cyber Project Coordinator]] (hereinafter, the ''Coord'') is the learner matriculated into the [[WorldOpp Pipeline]] program who is undergoing initial practical training. This training is a part of the [[CNM Cyber Placement]] stage. [[CNM Cyber]] (hereinafter, the ''Cyber'') is a collection of services that include (a) information technology called [[CNM Cloud]] (hereafter, the ''Cloud''), as well as (b) apprenticeships and internships that are organized at the ''Cloud''.
+
[[CNMCyber Coordinator]] (hereinafter, the ''Coord'') is an incumbent of the graduating, final-quarter [[CNMCyber practice]] (hereinafter, the ''Practice'') that [[The Economic Group]] has developed to practically introduce [[CNMCyber patron]]s to workspace overall. The ''Coords'' practice in executing the [[CNM Agile]] framework primarily including coordination of its separate endeavors.
  
At the [[Occupational Information Network]], the closest occupation is [[Information Technology Project Manager]]. The [[CITPMA|Certified Information Technology Project Management Associate]] ([[CITPMA]]) credential is awarded to the successful ''Coords''.
+
The ''Coords'' don't develop [[CNMCyber product]]s directly, on their own. On the contrary, they assist in hiring [[Careerprise contractor]]s and working with them.
  
 +
The ''Practice'' belongs to the fourth quarter of [[CNMCyber Bootcamps]] (hereinafter, the ''Bootcamp''). This quarter's lessons are called [[Cyber Coordinator Bootcamp]]; they are designed to prepare the ''Coords'' to that ''Practice''. The ''Practice'' is offered to those [[CNM Cloud Operator]]s who successfully pass [[Information Technology Project Management Exam]] after taking the fourth quarter's classes. The graduating endeavor encompasses the learner's individual plan to land a professional job. Successful completion of the cyber coordination practice qualifies the ''Coords'' as [[Certified Information Technology Project Management Associate]]s ([[Certified Information Technology Project Management Associate|CITPMA]]s). Graduation from the ''Role'' ends the ''Bootcamp''.
  
==What Coords produce==
 
To facilitate development of [[#Products to be developed|Products to be developed]], the ''Coords'' produce four categories of their first-level results: (1) [[#Meetings|Meetings]], (2) [[#Documents|Documents]], (c) [[#Records|Records]], and (d) [[#Communications|Communications]].
 
  
===Meetings===
+
==Position==
: A [[meeting]] is an occasion in which people meet to exchange data, discuss something, make decisions, and/or collaborate. Meetings occur online and/or offline in forms of verbal conversations, videoconferences, and/or webcasts.
+
The ''Coords'' practice is to facilitate someone else's performance on [[#Projects vs operations|Projects vs operations]] related to [[CNMCyber product]]s. The ''Coord'' [[#Choice of work|chooses]] the paid work from the [[#Authorized work|Authorized work]]; alternatively, the ''Coord'' may propose own work, which may or may not be authorized for compensation. To learn about benefits, competencies, history, supervision, and target audiences, please consult the '''[[CNMCyber practice]]''' wikipage.
 +
 
 +
===Choice of practice===
 +
: By default, the ''Coords'' choose [[#Endeavors|Endeavors]] that suit them best. [[CNMCyber Project Manager]]s may ask a ''Coord'' to take an urgent or specific project when they know anything professional about the ''Coord''. That means that the ''Coords'' have to choose their first endeavor at least.
  
: To support development of [[#Products to be developed|Products to be developed]], the ''Coords'' prepare, moderate, conduct, and close meetings. Those meetings may include:
+
: The work of the ''Coords'' is paid when they work on those endeavors that funding is authorized on the '''[[CNMCyber Usable]]''' wikipage. That page contains links to:
:* '''Hiring events''', which are interviews and other meetings between contractor candidates and CNM Cyber administrators organized to discuss potential entering into a [[contract]] and/or to make that decision.
+
:* Endeavors that the ''Coords'' can work on. Those pages are called "endeavor pages" and are combined in the [[:Category: CNMCyber endeavors]]; for instance, [[WordPress for CNM Cloud]].
:* '''Outreach events''', which are [[CNM Cyber event]]s organized to promote the ''Cyber'', the ''Cloud'', its technologies, needs, and services to outreach to current and potential clients and participants. These meetings are normally published at the [[CNM Cyber Meetup]] group.
+
:* Products that should emerge as a result of the ''Coords'' work. Those pages are called "product pages" and are combined in the [[:Category:CNM Cyber products]]; for instance, [[Educaship WordPress]].
:* '''Product meetings''', which are meetings organized (a) to discuss deliverable features, (b) to make deliverable decisions, and/or (c) to communicate those decisions.
 
:* '''Project meetings''', which are meetings organized (a) to discuss project features, (b) to make project decisions, and/or (c) to communicate those decisions.
 
  
: Within the [[#Project results|Project results]], the outreach events represent [[project output]]s. The other meetings should be considered as [[project scrap]]; those meetings are used to develop [[#Documents|Documents]].
+
: Any ''Coord'' is welcome to pick any endeavor he or she would like to work on. In addition, the ''Coords'' are encouraged to propose their own endeavors.
  
: Moreover, meetings tend to address a number of purposes. For instance, meetings of the [[CNM Technology Board]] may touch both product and project features and decisions. When they are open to the general public, they also serve the outreach purpose.
+
===How to start===
 +
: Are you interested in getting started as the ''Coord''? Please follow a step-by-step instruction as follows:
 +
:# '''Get''' professional experience as [[CNM Website Developer]], [[CNM Event Organizer]], and [[CNM Cloud Operator]].
 +
:# Until [[Cyber Coordinator Bootcamp]] is fully developed, briefly '''review''' the following wikipages:<ol type="a"><li>this very wikipage since it outlines your work,</li><li>[[CNMCyber product]] since this wikipage outlines the products, which development and management you are going to facilitate.</li><li>If you consider working on ''Cyber'' marketables, please consult also [[Careerprise Funnel]].</li></ol>
 +
:# '''Ask''' questions. Questions are a huge part of your work; if you cannot ask, you cannot work. If you prefer videoconferences, attend any [[CNMCyber This Week]] event. You will have opportunities to ask questions and get responses in real time.
 +
:# '''Understand''' why the ''Cyber'' endeavors are undertaken and what value is expected from the ''Coord''. That's simple. If you cannot deliver what [[CNMCyber Customer]] supports, you cannot work. Everything that [[CNMCyber Customer]] supports is stated on this very wikipage.
 +
:# '''Wait''' for 2-3 months if you cannot understand what your objectives are. There is a chance that the course and/or videos will be developed out of this wikipage during that time. The introductory courses will be available at https://cert.cnmcyber.com after registering at https://opplet.net/user/register ; the videos will be published on [[CNM Tube]] and [[YouTube]]. Some of course wiki-materials are linked to [[WorldOpp Orientation]], [[EmployableU Concepts]], and [[CNMCyber Bootcamps]] wikipages
 +
:# '''Pick up''' your first endeavor at the [[CNMCyber Usable]] wikipage when you understand what your objectives are. You may have no idea what that particular endeavor is about. First of all, no endeavor is fully clear and, secondly, to learn about one endeavor is always simpler that to learn about many. When you really studied this very wikipage, you should know how to go about that endeavor. If you cannot pick your project, you cannot start working as the ''Coord''.
 +
:# '''Contact''' [[CNMCyber Customer]] while stating (a) the endeavor you have picked, (b) what you plan to deliver, and (c) how much time you expect to work in order to deliver what you plan to deliver.
  
===Documents===
+
: By the way, you can be paid to ask questions about this wikipage when you identify the endeavor behind that page.
: A [[document]] is a separate piece that (a) presents data, (b) is composed with texts and/or images, and (c) can further be edited or revised. The former document that can no longer be revised, for instance, a signed contract, becomes a [[record]].
 
  
: To facilitate development of [[#Products to be developed|Products to be developed]], the ''Coords'' draft, edit, groom, and manage documents. Those documents may include:
+
===Occupation===
:* '''Blueprints''', which are document prototypes useful to create final documents. For instance, the [[Careerprise contractor agreement]] is used as a blueprint to draw up contracts with individual contractors. As a rule, these target documents are published on [[CNM Wiki]].
+
: [[The Economic Group]] has created and markets the ''Coord's'' role for those who don't necessarily possess any occupation yet. At the [[Occupational Information Network]], the closest occupation is [[Information Technology Project Manager]]; the principal difference is that the ''Coords'' don't make managerial decisions. The [[CITPMA|Certified IT Project Management Associate]] ([[CITPMA]]) credential is awarded to the successful ''Coords''.
:* '''Legal drafts''' such as papers drafted to be signed as [[contract]]s.
 
:* '''Outreach materials''', which are marketing drafts intended to outreach to current and potential clients and participants such as [[Friends Of CNM newsletter]]s.
 
:* '''Product documents''', which are descriptions of former, existing, and future products published at [[CNM Wiki]], as well as deliverable requirements, emails and other messages between product owners and developers, organizational and technical documentation such as [[standard operating procedure]]s ([[SOP]]s), minutes of the meetings, testing and other reports, etc.
 
:* '''Project documents''', which are project requirements, progress reports, emails and other messages between project owners and developers, memos with the results of project approvals, developments, meetings, and research.
 
  
: Within the [[#Project results|Project results]], those draft and final documents are either [[project scrap]]s or [[project output|output]]s. As the ''outputs'', they usually accompany other [[#Products to be developed|Products to be developed]]. For example, products normally come with instructions. However, some of documents represent whole products on their own. For example, to bundle the functional product with the instructions, those instructions were needed to be developed before.
+
: Other close occupations include Project Management Specialists, Computer and Information Systems Managers,  
  
===Records===
+
Administrative Services Managers
: A [[record]] is a piece of matter that (a) presents data and (b) cannot further be edited or revised unless losing the status of a record. For instance, a signed contract, which is a [[record]], can be used as a [[prototype]] to create new [[document]]s.
+
Chief Executives
 +
Executive Secretaries and Executive Administrative Assistants
 +
Secretaries and Administrative Assistants
 +
Office and Administrative Support Workers
 +
Legal Secretaries and Administrative Assistants
 +
Human Resources Manager
 +
General and Operations Managers
  
: To support development of [[#Products to be developed|Products to be developed]], the ''Coords'' collect records, place them in designated spaces, and, if applicable, manage their storage. Special [[standard operating procedure]]s ([[standard operating procedure|SOP]]s) shall designate spaces for that purpose. Those records may include:
+
===Tools===
:* '''Archived files''' such as videos, audios, textual files, as well as coded and programmed scripts.
+
:* [[Inplz app]]s
:* '''Databases''' of contacts, competencies of contractors, characteristics of tested software, etc.
+
:* [[CNM Wiki]]
:* '''Enterprise records''' such as [[contract]]s, which are legally-binding agreements, applications and reports that are officially submitted to governmental bodies and partners, identification and other personal documents of the ''Cyber's'' employees that the law requires to keep in the enterprise system, accounting records, etc. At the ''Cyber'', enterprise records are stored at [[CNM Venture]].
 
:* '''Product records''' such as approved requirements for the project deliverable are posted at [[CNM Wiki]]. To be product records, they need to be protected from unauthorized edits and belong to the [[:Category: Product records|Product records]] category.
 
:* '''Project records''' are kept at several spaces depending on their nature. Project reports are posted at the [[CNM Cloud Usable]] wikipage. Legally-binding documents are stored at [[CNM Venture]]. Accepted deliverables are stored at [[CNM Git]].
 
:* '''Publications''' such as minutes of meetings and others textual records that reflect past events, content of [[CNM Git]], [[CNM Page|Page]], [[CNM Social|Social]], and [[CNM Wiki|Wiki]], as well as those postings on [[YouTube]], [[CNM Cyber Meetup]], and other [[social media]] that the ''Coords'' may make. There is no single place for publications' storage at the ''Cyber''; they are posted at different media. [[CNM Wiki]] can be used for development of publications; appearance of [[CNM app]]s at the [[WWW]] can also be considered as publications.
 
:* '''Technology records''' such as access credentials and detailed descriptions of software used in the ''Cloud''. At the ''Cyber'', technology records are stored at [[CNM Git]].
 
  
: Within the [[#Project results|Project results]], the records represent [[project output]]s by their definition.
+
==What Coords produce==
 +
To facilitate development and/or management of [[CNMCyber product]]s, the ''Coords'' produce four categories of their first-level results. They are (1) [[#Meetings|Meetings]], (2) [[#Documents|Documents]], (c) [[#Records|Records]], and (d) [[#Communications|Communications]]. For the ''Coords'', those results represent measurable outputs of the ''Practice''.
  
 
===Communications===
 
===Communications===
: For the purposes of this very wikipage, [[communications]] are defined as distribution of the messages that are related to the ''Cyber'', the ''Cloud'', as well as endeavors to develop those. Particularly, the ''communications'' are used to exchange the [[#Documents|Documents]] and [[#Records|Records]]; the [[#Meetings|Meetings]] are used to facilitate the ''communications''.
+
: For the purposes of this very wikipage, [[communications]] are defined as distribution of the messages that are related to the ''Cyber'', the ''Cloud'', as well as efforts to develop those. Particularly, the ''communications'' are used to exchange the [[#Documents|Documents]] and [[#Records|Records]]; the [[#Meetings|Meetings]] are used to facilitate the ''communications''.
  
: The ''Coords'' run their communications to make development of [[#Products to be developed|Products to be developed]] possible. These communications include:
+
: The ''Coords'' run their communications to make development of [[CNMCyber product]]s possible. These communications include:
 
:* '''Internal communications''' such as project and product communications, meeting invitations, reminders, moderation and discussion messages, and follow-ups.
 
:* '''Internal communications''' such as project and product communications, meeting invitations, reminders, moderation and discussion messages, and follow-ups.
 
:* '''External communications''' such as marketing campaigns, as well as distribution of outreach messages.
 
:* '''External communications''' such as marketing campaigns, as well as distribution of outreach messages.
  
: Within the [[#Project results|Project results]], internal communications represent [[project scrap]]s; they are needed to produce [[project output]]s. External communications, especially marketing campaigns, represent [[project output]]s.
+
: Marketing communications are described in the [[#Market presence|Market presence]] section of this very wikipage. Within the [[#Project results|Project results]], internal communications represent [[project scrap]]s; they are needed to produce [[project output]]s. External communications, especially marketing campaigns and products, represent [[project output]]s.
  
==What Coords do==
+
===Documents===
Each project can have the ''Coord'' who is responsible for it. To facilitate production of the [[#Project deliverables|Project deeliverables]], the ''Coords'' do a cycle of endeavors that consists of several stages. Similar procedures are normally needed to produce [[project scrap]]s and by-products. That means that the ''Coords'' are expected to follow the same cycle to create [[#What Coords produce|What Coords produce]].
+
: Generally speaking, a [[document]] is a separate piece that (a) presents data, (b) is composed with texts and/or images, and (c) can further be edited or revised. The former document that can no longer be revised, for instance, a signed contract, becomes a [[record]].
  
===Initiating the project===
+
: Probably, ''documents'' are the single most important output of the ''Coords's'' work. To facilitate development of [[CNMCyber product]]s, the ''Coords'' draft, edit, groom, and manage documents. Those documents may include:
: Project initiation aims to setup the stage for [[#Defining the deliverable|Defining the deliverable]] and [[#Defining the project|Defining the project]] activities.
+
:* '''Blueprints''', which are document prototypes useful to create final documents. For instance, the [[Careerprise contractor agreement]] wikipage is used as a blueprint to draw up contracts with individual contractors. As a rule, these target documents are published on [[CNM Wiki]].
 +
:* '''Legal drafts''' such as papers drafted to be signed as [[contract]]s.
 +
:* '''Product documents''', which are descriptions of former, existing, and future products published on [[CNM Wiki]], as well as deliverable requirements, emails and other messages between product owners and developers, organizational and technical documentation such as [[standing operating procedure]]s ([[SOP]]s), minutes of the meetings, testing and other reports, etc.
 +
:* '''[[Project document]]s''', which are project requirements, progress reports, emails and other messages between project owners and developers, memos with the results of project approvals, developments, meetings, and research.
  
is the processes under which the project is created and defined to the extent necessary to begin planning the project. This step involves the project setup, and ensures that the performing organization is clear about the purposes and priorities surrounding the project.  There are usually certain issues that require setup, like funding or stakeholder issues.
+
: Although outreach materials such as those that are used in organizing of [[CNMCyber event]]s and website texts are documents, the ''Coords'' don't normally create them. [[Careerprise contractor]]s, [[CNM Cloud Operator]]s, [[CNM Event Organizer]]s, and [[CNM Website Developer]]s shall create them; however, if no contractors, developers, operators, or organizers are available, the ''Coords'' may step in.
  
This is a small but necessary step, and its importance is easily underestimated.
+
: Within the [[#Project results|Project results]], those draft and final documents are either [[project scrap]]s or [[project output|output]]s. As the ''outputs'', they usually accompany other [[CNMCyber product]]s. For example, products normally come with instructions. However, some of documents represent whole products on their own. For example, to bundle the functional product with the instructions, those instructions were needed to be developed before.
  
There are two crucial parts to this phase:
+
===Meetings===
 +
: Generally speaking, a [[meeting]] is an occasion in which people meet to exchange data, discuss something, make decisions, and/or collaborate. Meetings occur online and/or offline in forms of verbal conversations, videoconferences, and/or webcasts.
  
    Develop Project Charter
+
: To support development of [[CNMCyber product]]s, the ''Coords'' prepare, moderate, conduct, and close meetings. Those meetings may include:
    Identify Stakeholders
+
:* '''Hiring events''', which are interviews and other meetings between contractor candidates and [[CNMCyber Project Manager]] organized to discuss potential entering into a [[contract]] and/or to make that decision.
 +
:* '''Product meetings''', which are meetings organized (a) to discuss deliverable features, (b) to make deliverable decisions, and/or (c) to communicate those decisions.
 +
:* '''Project meetings''', which are meetings organized (a) to discuss project features, (b) to make project decisions, and/or (c) to communicate those decisions.
  
Developing the Project Charter
+
: Although [[CNMCyber event]]s can be considered as meetings, the ''Coords'' don't normally organize them. Either [[Careerprise contractor]]s or [[CNM Event Organizer]]s shall organize them; however, if neither ''contractors'' nor organizers are available, the ''Coords'' may step in.
  
The Project Charter is the document which defines and authorizes the project.  It outlines the organization’s vision for the project and the business case for it.  Essentially it represents what the organization is thinking when creating the project and puts a foundation under the planning phase. It can contain the following things:
+
: At the same time, the ''Coords'' shall participate, synchronically or asynchronically, in [[CNMCyber This Week]] events, which are weekly meetings of the ''Coords'' who present (a) what they accomplished last week, (b) what they plan to accomplish next week, and (c) what assistance do they need.
  
    Scope statement
+
: Within the [[#Project results|Project results]], the meetings immediately produce [[project scrap]]s. Their archived recordings are [[#Records|Records]]. The meetings are used to develop [[#Documents|Documents]].
    A general scope statement which identifies the vision for what the project will accomplish.  For example, the construction of a new commercial building could involve a certain number of offices, design to a certain standard, etc.  It is a good idea to identify the key deliverables, but it is not the function of the project charter to identify all deliverables. It should be limited to the non-negotiable ones such as the submission of a design package for approval before construction commences.  A final scope statement will be developed for the project during the planning phase, but the project charter can (and should) identify the scope of the project as envisioned when the project is created.
 
    Milestones
 
    Similar to the deliverables, the major milestones can and should be identified in the project charter but it is not the role of the project charter to list all milestones. A project charter should not contain a detailed schedule, but a description of the key milestones can aid in the communicating the project as envisioned by the organization.
 
    Business case
 
    A description of why the organization is undertaking the project is helpful to put everyone on the same page from the beginning.  Business metrics such as expected profit or revenue, or required Return on Investment (ROI) can make it clear to the project management team what the expected benefit will be.  Maybe there is a single problem that is being solved.  Stating this explicitly can guide in decision making during the project.
 
    Funding amount
 
    Most projects start out with a funding level approved by the organization.  Stating the amount in the project charter can establish the boundaries of the project and ensure that nobody thinks too big or too small.
 
    Funding status
 
    Funding always comes with conditions, even when a pot of money has been approved.  I’ve seen projects that have a certain funding level approved but run into funding issues later on, for example,
 
  
        money moves to a future fiscal year and ends up on other projects.
+
===Records===
        there are no contingencies available when the cost escalates.
+
: Generally speaking, a [[record]] is a piece of matter that (a) presents data and (b) cannot further be edited or revised unless losing the status of a record. For instance, a signed contract, which is a [[record]], can be used as a [[prototype]] to create new [[document]]s.
        it wasn’t actually approved to begin with, due to communication issues at the funding level.
 
    Success Criteria
 
    Every project contains criteria for its success and the organization performing the project should identify these on a level “outside” the project (i.e. the project charter).  There are usually primary success factors like paving a road that’s smooth, or developing a website that’s beautiful.  But it’s the secondary success factors that are usually overlooked and present the bigger risk to the project.  These might include providing enough compaction to the asphalt, or providing the correct underlying database.
 
    Stakeholders
 
    Although it is not the responsibility of the project charter to identify all stakeholders, it should identify the primary stakeholders who are integral to the project and under whose auspices the project was created. For example, for the paving project above, the land developer is the project sponsor and the city (local government) is a major stakeholder who should be addressed during the project charter.  The primary objectives of each party should be identified so it is clear why the project has been created.
 
  
Identifying Stakeholders
+
: To support development of [[CNMCyber product]]s, the ''Coords'' collect records, place them in designated spaces, and, if applicable, manage their storage. Special [[standing operating procedure]]s ([[standing operating procedure|SOP]]s) shall designate spaces for that purpose. Those records may include:
 +
:* '''Archived files''' such as videos, audios, textual files, as well as coded and programmed scripts.
 +
:* '''Databases''' of contacts, competencies of contractors, characteristics of tested software, etc.
 +
:* '''Enterprise records''' such as [[contract]]s, which are legally-binding agreements, applications and reports that are officially submitted to governmental bodies and partners, identification and other personal documents of ''Cyber's'' employees that the law requires to keep in the enterprise system, accounting records, etc. At the ''Cyber'', enterprise records are stored at [[CNM Corp]].
 +
:* '''Product records''' such as approved requirements for the project deliverable are posted at [[CNM Wiki]]. To be product records, they need to be protected from unauthorized edits and belong to the [[:Category: Product records|Product records]] category.
 +
:* '''Project records''' are kept at several spaces depending on their nature. Project reports are posted at the [[CNMCyber Usable]] wikipage. Legally-binding documents are stored at [[CNM Corp]]. Accepted deliverables are stored at [[CNM Lab]].
 +
:* '''Publications''' such as minutes of meetings and others textual records that reflect past events, content of [[CNM Lab]], [[CNM Page|Page]], [[CNMCyber.com]], and [[CNM Wiki|Wiki]], as well as those postings on [[YouTube]], [[CNMCyber Meetup]], and other [[social media]] that the ''Coords'' may make. There is no single place for publications' storage at the ''Cyber''; they are posted at different media. [[CNM Wiki]] can be used for development of publications; appearance of [[CNM app]]s at the [[WWW]] can also be considered as publications.
 +
:* '''Technology records''' such as access credentials and detailed descriptions of software used in the ''Cloud''. At the ''Cyber'', technology records are stored at [[CNM Lab]].
  
Stakeholder identification has special significance to the project charter, even though it is listed among the other items, above.  It is a good idea to conduct a stakeholder analysis to determine all of the stakeholders as part of the development of the project charter.
+
: Within the [[#Project results|Project results]], the records represent [[project output]]s by their definition.
  
Stakeholders come in many forms and have vastly different needs as it relates to the project. They can be:
+
==Endeavors==
 +
For the purposes of this very wikipage, ''endeavors'' refer to both [[#Projects vs operations|development projects and management operations]]. Each endeavor can have the ''Coord'' who coordinates this endeavor and, particularly, facilitates the [[#Contractors|Contractors]]' performance. Each ''Coord'' [[#Choice of work|chooses his or her endeavor to coordinate]].
  
    Supporters.  For example, a county that will receive tax revenue from a new factory.
+
Endeavors may include several projects and/or operations, but the ''Coord'' must concentrate only on one project or operation during one week. The endeavors are listed in the [[:Category: CNMCyber endeavors|"CNMCyber endeavors" category]].
    Opposed.  For example, local landowners who don’t like the new factory in their back yard.
 
  
They can also have varying levels of support.  You often don’t know how strongly they support or oppose the project until you consult with them.  Many projects have run into trouble because assumptions were made about stakeholder interests that were not based on direct communication with those stakeholders.
+
===Authorized endeavors===
 +
: Those [[#Endeavors|Endeavors]] that are authorized to practice with are listed on the [[CNMCyber Usable]] wikipage.
  
Often the overall stakeholder position is complex because there are conflicting opinions within the stakeholder itself.  For example, the county that will receive tax revenue from a new factory could have a contingent of taxpayers who are strongly opposed, pulling the politicians in different directions than they originally state.  It can also cause changes to the stakeholder’s position during the project.  Therefore it is often advisable to analyze the underlying factors governing a stakeholder’s position, even for stakeholders that are supporters.
+
===Endeavor documents===
 +
: At [[CNM Wiki]], ''Cyber'' endeavors are documented using two types of wikipages:
 +
:# The progress on particular endeavors is reported at the [[CNMCyber Usable]] wikipage.
 +
:# Endeavor pages document everything, but progress reports. Those pages are listed at the [[:Category: CNMCyber endeavors|"CNMCyber endeavors" category]] and include [[project document]]s such as [[project charter]], [[asset register]], [[competency register]], [[stakeholder register]], [[requirements traceability matrix]], [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]].
  
 +
===Projects vs operations===
 +
: The ''Coords'' work and/or facilitate someone else's work on endeavors, which are either:
 +
:* '''Product development projects''' are development endeavors; they are undertaken to create new products or new features of existing products, which is addressed in the [[#Projects|Projects]] section of this wikipage. Projects are temporary endeavors; they close when [[CNMCyber Team]] receive all of the required deliverables and [[#Contractors|Contractors]] receive their compensation. While working on projects, the ''Coords'' are engaged in the [[#Formalizing the project|Formalizing the project]], [[#Specifying the deliverables|Specifying the deliverables]], [[#Planning the project|Planning the project]], [[#Creating the deliverables|Creating the deliverables]], and [[#Commissioning the product|Commissioning the product]] activities.
 +
:* '''Product management operations''' are operational endeavors; they are undertaken to manage existing [[CNMCyber product]]s, including their service, maintenance, audits and revisions, as well as end of life. [[Ongoing operation]]s can be viewed as permanent endeavors, which possibly close only when all of the existing products reach their end of life. While working on projects, the ''Coords'' are engaged in the [[#Managing the product|Managing the product]] activities.
  
: A [[project charter]] stands a [[project]] out of undocumented change making or development. To coordinate this chartering, the responsible ''Coord'':
+
: Regardless of work on projects or operations, the ''Coords'' are always engaged in the [[#Studying the backgrounds|Studying the backgrounds]] activities and can be engaged in the [[#Hiring the contractors|Hiring the contractors]] and [[#Working with contractors|Working with contractors]] activities.
:# '''Identifies''' those available resources that should or can be used in project activities. Human resources include [[#Personnel|Personnel]]. Other resources include those presented in the initial [[WorldOpp Pipeline]] courses, on [[CNM Wiki]], existing prototypes and finished products, and materials available on the [[World Wide Web]] and other sources. For off-the-shelf products, developer websites and professional resources like https://stackoverflow.com/ are usually helpful.
 
:# '''Collects''' data using identified resources. This study includes communicating with stakeholders, reviewing documents, and testing those prototypes and finished products that are available.
 
:# '''Selects''' those resources and those data that will be used in the project activities.
 
:# '''Inventories''' those data, tools, materials, prototypes and factors that have been identified as being or could be involved in the development.
 
:# '''Describes''' the future deliverable and its possible production, based on the resources identified in the inventory. The description may include (a) [[business requirement]]s, (b) [[deliverable depiction]]s, (c) [[stakeholder requirement]]s, as well as drafts for [[deliverable specification]]s, [[work specification]]s, and, possibly, some elements of a [[deliverable charter]].
 
:# '''Makes''' sure that the [[#Customer|Customer]] who requested the deliverable needs exactly the deliverable that meets the described [[business requirement]]s.
 
:# '''Provides''' data to the [[#Customer|Customer]] for making a decision either to attract external contractors or to produce the deliverable with internal personnel. The positive decision assumes the financing of the production work.
 
:# '''Brings''' requirements and other development documents to completeness. At some cases, this activity may end after the production of a functional part of the deliverable.
 
  
: If further production will be carried out without the involvement of contractors, the [[#Customer|Customer]] can authorize its beginning before the completion of the [[deliverable charter]]. In this case, the requirements are finalized taking into account the data obtained during the production process.
+
===Sets of processes===
 +
: Any endeavor can be viewed as sets of [[process]]es. On that very wikipage, those processes are grouped in nine sections of [[#What Coords do|What Coords do]].
  
:The defining of the deliverables themselves opens before the start of work on the direct production of the deliverables. Even if developers have been hired, the planning periodically resumes after the start, since the production always reveals new factors and requirements.
+
: However, every of those groups, in fact, are separate developments on their own. For instance, the [[#Formalizing the project|project formalization]] shall result in a [[project charter]], but this document may be considered as an output of a separate development that requires its own formalization, studies, specification, planning, creation, and commissioning. Sometimes, it also requires hiring contractors and working with them. Thus, the sections of [[#What Coords do|What Coords do]] show just some level of tentative divisions and do not represent definite classifications.
  
===Defining the deliverables===
+
===Why endeavors===
: The main goal of the deliverable defining activities is to get the deliverable in a [[state of certainty]], which is determined by the presence of a validated [[deliverable charter]]. In other words, planning is getting a description of the deliverable in such a way that allows this development to be certain. To achieve this goal, the responsible ''Coord'':
+
: In business, a combination of two or more projects and, possibly, some ongoing operations, is often called a ''program''. In this sense, a ''program'' refers to a set of structured activities that is undertaken on a systematic basis.  
:# '''Makes''' sure that the [[#Customer|Customer]] who requested the deliverable needs exactly the deliverable that meets the described [[business requirement]]s.
 
:# '''Brings''' [[stakeholder requirement]]s in line with the [[business requirement]]s.
 
:# '''Formulates''' the difference between what actually is and what is needed. With regards to the deliverable, this identified difference should be addressed by the [[deliverable specification]].
 
:# '''Checks''' [[deliverable specification]]s for completeness. Completeness is characterized by the presence of conditions for (a) functionality, (b) applicability, and (c) manageability of the deliverable. Conditions of applicability should include deliverable documentation, such as system diagrams, a list of necessary accesses, as well as the availability of a working instruction for operation such as [[standard operating procedure]] ([[SOP]]), measures to protect the deliverable and instructions for recovery in case of accidents.
 
:# '''Evaluates''' whether it is necessary to involve third-party contractors in the deliverable production and, if necessary, whether their assistance is required to create [[deliverable specification]]s, [[work specification]]s, and [[deliverable charter]] draft.
 
:# '''Provides''' data to the [[#Customer|Customer]] for making a decision either to attract external contractors or to produce the deliverable with internal personnel. The positive decision assumes the financing of the production work.
 
:# '''Brings''' requirements and other development documents to completeness. At some cases, this activity may end after the production of a functional part of the deliverable.
 
  
: If further production will be carried out without the involvement of contractors, the [[#Customer|Customer]] can authorize its beginning before the completion of the [[deliverable charter]]. In this case, the requirements are finalized taking into account the data obtained during the production process.
+
: The term, ''endeavor'', is chosen to separate the work that is available to the ''Coords'' from complex and lengthy ''programs''. Since the ''Coords'' choose their endeavors to coordinate, ''Coords<nowiki>'</nowiki>'' endeavors are not undertaken systematically.
  
:The defining of the deliverables themselves opens before the start of work on the direct production of the deliverables. Even if developers have been hired, the planning periodically resumes after the start, since the production always reveals new factors and requirements.
+
==What Coords do==
 
+
The ''Coords<nowiki>'</nowiki>'' work can be divided in nine [[#Sets of processes|Sets of processes]]. Every [[#Endeavors|Endeavor]] shall start with [[#Formalizing the project|Formalizing the project]], go through at least [[#Studying the backgrounds|Studying the backgrounds]] and [[#Creating the deliverables|Creating the deliverables]], as well as end from the [[#Managing the product|Managing the product]] activities.
===Defining the project===
 
: The main goal of the project defining activities is to decide how the deliverable will be developed. Those activities result in a validated [[project charter]]. In other words, planning is getting a description of the deliverable in such a way that allows this development to be certain. To achieve this goal, the responsible ''Coord'':
 
:# '''Makes''' sure that the [[#Customer|Customer]] who requested the deliverable needs exactly the deliverable that meets the described [[business requirement]]s.
 
:# '''Brings''' [[stakeholder requirement]]s in line with the [[business requirement]]s.
 
:# '''Formulates''' the difference between what actually is and what is needed. With regards to the deliverable, this identified difference should be addressed by the [[deliverable specification]].
 
:# '''Checks''' [[deliverable specification]]s for completeness. Completeness is characterized by the presence of conditions for (a) functionality, (b) applicability, and (c) manageability of the deliverable. Conditions of applicability should include deliverable documentation, such as system diagrams, a list of necessary accesses, as well as the availability of a working instruction for operation such as [[standard operating procedure]] ([[SOP]]), measures to protect the deliverable and instructions for recovery in case of accidents.
 
:# '''Evaluates''' whether it is necessary to involve third-party contractors in the deliverable production and, if necessary, whether their assistance is required to create [[deliverable specification]]s, [[work specification]]s, and [[deliverable charter]] draft.
 
:# '''Provides''' data to the [[#Customer|Customer]] for making a decision either to attract external contractors or to produce the deliverable with internal personnel. The positive decision assumes the financing of the production work.
 
:# '''Brings''' requirements and other development documents to completeness. At some cases, this activity may end after the production of a functional part of the deliverable.
 
 
 
: If further production will be carried out without the involvement of contractors, the [[#Customer|Customer]] can authorize its beginning before the completion of the [[deliverable charter]]. In this case, the requirements are finalized taking into account the data obtained during the production process.
 
 
 
:The defining of the deliverables themselves opens before the start of work on the direct production of the deliverables. Even if developers have been hired, the planning periodically resumes after the start, since the production always reveals new factors and requirements.
 
 
 
===Hiring contractors===
 
: The main goal of the deliverable planning and production activities is to get the deliverable in a [[state of certainty]], which is determined by the presence of a validated [[deliverable charter]]. In other words, planning is getting a description of the deliverable and its development process in such a way that allows this development to be certain. To achieve this goal, the responsible ''Coord'':
 
 
 
: If external contractors are required, the ''Coord'' will further:
 
:# '''Prepares''' the hiring of contractors for development, including developing texts for solicitation announcements and options for their placement, forming a list of consultants and potential developers, as well as organizing a community on the [[CNM Social]] and scheduling video conferences to which everyone interested in development will be invited.
 
:# '''Invites''' contractors to develop and, in parallel, refine the [[deliverable specification]], [[work specification]], and [[deliverable charter]].
 
:# '''Assists''' in the process of hiring development contractors, including the selection of the most promising candidates, negotiations, the conclusion of a development contract and the commissioning of contractors. Historically, requirements are refined during the recruitment process. If the requirements cannot be formulated during the recruitment process, they themselves become the target deliverable of an intermediary project.
 
:# '''Informs''' the [[#Customer|Customer]] about the readiness of the contract or contract for the conclusion. The conclusion of the contract authorizes the financing of the production of the deliverable by contractors. One of the consultants may be contracted for consultations and/or participation in video conferences.
 
  
:The planning of both the deliverable itself and the process of its production opens before the start of work on the direct production of the deliverable and, even if contractors are involved, it is periodically resumed after the start, since the production always reveals new factors and requirements.
+
===Formalizing the project===
 +
: For the purposes of this very wikipage, project formalization refers to the set of efforts that is undertaken to the extent necessary to start researching the backgrounds for envisioning of [[#Project deliverables|Project deliverables]] and their production. This formalization aims to setup the stage for [[#Studying the backgrounds|Studying the backgrounds]] activities.
  
===Creating the deliverables===
+
: The formalization shall produce a [[project charter]], which is a document that (a) formalizes a [[project]] out of undocumented change making or development and (b) authorizes the project administration. The charter contains [[CNMCyber Customer]]'s [[business requirement]]s or those product and/or project requirements of [[CNMCyber Customer]] that are not negotiable. These requirements shall address some [[business need]]; the terms ''business requirement'' and ''business need'' are synonims and often used interchangeably. At [[CNMCyber]], they may be stated in one or more of the following:
: The main goal of deliverable development activities is to obtain the deliverable in a [[state of capability]], which is determined by the fact that the deliverable meets all the [[deliverable specification]]s that have been approved for it. In addition to the deliverable itself, the process of its production must also satisfy the [[work specification]]s. To achieve this goal, the responsible ''Coord'':
+
:* [[Business case]]. A description of [[CNMCyber Customer]]'s vision for what and/or how the project shall accomplish. The case may or may not state [[success criteria]] or those [[key performance indicator]]s ([[key performance indicator|PKI]]s) that would or would not constitute the project's success. Any successful project shall satisfy specific [[business need]]s. Generally speaking, the business case constitutes why the project exists.
:# '''Oversees''' the production of the product, playing the roles of the [[product owner]] and [[project owner]] in the absence of other employees assigned to these roles. Thus, the ''Coord'' decides how, within the framework of the agreed requirements, the deliverable and the project should be.
+
:* [[Statement of work]] ([[Statement of work|SOW]]). A document that states hard requirements related to product and project scope, budget, as well as schedule. The statement lists "hard" deliverables and key factors that affect the project work. The statement may or may not indicate project tools, policies, regulatory and governance terms. The budget part of the statement may or may not describe milestones. The schedule part of the statement may or may not describe funds available, work authorization process, and/or constraints to the funds' availability. The statement is often employed as a part of a [[request for proposal]] ([[request for proposal|RFP]]).
:# '''Tests''' the deliverable and, if necessary, its parts.
 
:# '''Oversees''' the development and execution of the project, including monitoring compliance with the budget, schedule and scope of work.
 
:# '''Initiates''' changes to the requirements for the deliverable or its production.
 
:# '''Starts''' a project closed from the public on [[CNM Git]] for work on the deliverable in addition to the project wikipage on [[CNM Wiki]].
 
:# '''Reports''' to the [[#Customer|Customer]] on the status of the project, collecting, analyzing and summarizing information and trends.
 
:# '''Provides''' acceptance of the product, including the documentation that was agreed upon by the contract, or motivates the need to refuse acceptance after the contractor informs about the complete completion of work on the direct production of the product.
 
:# '''Makes''' changes to the documentation based on these developments.
 
  
===Working with contractors===
+
: On a slang, non-negotiable requirements are called "hard requirements". The ''charter'' contains all of the hard requirements that come from [[CNMCyber Customer]]. However, some of hard requirements derive from the laws, availability of workforce, and other environmental factors. They shall be added to a [[requirements traceability matrix]] ([[requirements traceability matrix|RTM]]) during the [[#Studying the backgrounds|Studying the backgrounds]] activities.
: If third-party contractors are involved in the development, the ''Coord'' will also:
 
:# '''Serves''' as an liaison between the [[#Customer|Customer]] and contractors, reporting problems that need to be resolved.
 
:# '''Organizes''' videoconferences or other meetings of parties interested in the project, especially those necessary to resolve problems arising during the project.
 
:# '''Starts''' the process of paying contractors for their work. The process shall be described in a special [[standard operating procedure]] ([[standard operating procedure|SOP]]). Prior to creating it, this start of the process implies a request to the manager or [[#Customer|Customer]].
 
: The direct production of a deliverable opens after the decision of the [[#Customer|Customer]] to start this production, as a rule, when [[business requirement|business]] and [[stakeholder requirement]]s are present. [[deliverable specification|deliverable]] and [[work specification]]s, as well as [[prototype]]s can be refined in parallel with the production of a viable product. The production of the deliverable is closed with the acceptance of the deliverable and can be resumed if problems with the viability of the deliverable are found out.
 
  
===Defining the operations===
+
: To coordinate the project formalization, the responsible ''Coord'':
Hiring servicers
+
:# '''Collects''' data related to the [[business requirement]]s from [[CNMCyber Customer]].
 +
:# '''Analyses''' the collected data related to [[business need]]s while organizing that data on [[CNM Wiki]].
 +
:# '''Drafts''' a [[project charter]].
 +
:# '''Makes''' sure that the [[statement of work]] ([[statement of work|SOW]]) in the drafted [[project charter]] addresses the [[business need]] and supports the [[business case]].
 +
:# '''Submits''' the drafted [[project charter]] for [[CNMCyber Customer]]'s approval.
 +
:# '''Publishes''' the [[project charter]], after its approval, on [[CNM Wiki]].
 +
:# '''Requests''' (a) assistance of the [[#Administrators|Administrators]] when additional resources are needed and/or (b) changes to the [[project charter]] when new data from existing and/or new sources of data prompt so.
 +
:# '''Reports''' on progress of the project formalization using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
===Commissioning the product===
+
: The project formalization starts after the [[business need]] is identified and ends when the [[project charter]] is completed.
: The main goal of the deliverable transfer into operation is to obtain the deliverable in a [[state of applicability]], which is determined by the fact that the deliverable is not only functional, but can also be used for the purpose for which it was produced. To achieve this goal, the responsible ''Coord'':
 
:# '''Is responsible''' for restricting the contractor's further access to the deliverable.
 
:# '''Publishes''' the documentation received from the contractor on the ''Cloud'' resources. Internal, closed to the public, documentation, such as administrator access to installed software, is published on [[CNM Git]]. The documentation that can be open to the public without restrictions is published on [[CNM Wiki]].
 
:# '''Contributes''' to the implementation of the transfer of the deliverable from accepted from the contractor to put into operation. This "contribution", in particular, may include (a) clarifying with the project manager which of the [[#Personnel|Personnel]] will administer the produced product, (b) transferring access to the classified documentation on [[CNM Git]] to administrators, (c) together with administrators, detailing the procedure for transferring the deliverable to operations, (d) [[standard operating procedure]]s ([[SOP]]s), product protection measures and disaster recovery procedures, and (e) hiring service contractors. Maintenance may include prompt assistance at the request of administrators, periodic product revisions, and timely software updates, if applicable.
 
:# '''Makes''' changes reflecting the real state of affairs on this very wikipage, as well as related project wikipages.
 
: The transition to production opens no later than the receipt of the finished deliverable and ends with the start of use of the product, usually initially during the [[beta testing]] process.
 
  
===Managing the product===
+
===Studying the backgrounds===
: The main goal of product management activities is to get the product in a [[state of manageability]], which is determined by the fact that the product is not only used for the purpose for which it was produced, but also controlled. This management includes both the improvement and improvement of product performance, as well as decisions to end-of-life or replace. To achieve this goal, the responsible ''Coord'':
+
: For the purposes of this very wikipage, endeavor studies refer to the set of efforts that is undertaken to the extent necessary to start envisioning, planning and managing for the [[project deliverable]]s, their production and management. These studies aim to setup the stage for [[#Specifying the deliverables|Specifying the deliverables]], [[#Planning the project|Planning the project]], and [[#Managing the product|Managing the product]] activities.
:# '''Monitors''' product usage, administrator performance, user feedback, and trends in markets associated with the product. We are talking about commercial versions of analogues, component parts, as well as changes in the factors and procedures for their conception, capacity, application and refinement.
 
:# '''Organizes''' video conferences or other meetings of parties interested in the product, especially those necessary to discuss the product, the work of administrators, user feedback and market trends.
 
:# '''Identifies''' problems and opportunities to improve the product or replace the product with other solutions.
 
:# '''Inventory''' the problems and opportunities that have been identified.
 
:# '''Presents''' the problems and opportunities identified in the inventory to the [[#Customer|Customer]] for making decisions about opening new projects.
 
:# '''Makes''' changes reflecting the real state of affairs on this very wikipage, as well as related project wikipages.
 
: Product management opens at the latest when the product is put into service and ends when the product gets retired.
 
  
==Projects==
+
: Endeavor studies shall produce data needed for (a) envisioning of the product, (b) planning its production, and (c) managing the produced product. At [[CNMCyber]], the project studies shall produce the following outputs:
The ''Coords'' work on [[project]]s, which can be defined as [[enterprise effort]]s undertaken to produce a unique [[deliverable]], functional features of which are identified or can be identified before the ''efforts'' start. Any ''project'' can be viewed as a set of [[process]]es. The ''deliverables'' of the ''projects'' that the ''Coords'' coordinate are described in the [[#Products to be developed|Products to be developed]] section of this wikipage.
+
:* [[Asset register]], which is a database of assets that can be used in the project. Particularly, those assets include non-human sources of data that are useful for production of project deliverables.
 +
:* [[Competency register]], which is a database of those competencies that can be valuable to ''Cyber'' efforts and their owners, potential and current [[#Contractors|Contractors]] and members of [[CNMCyber Team]].
 +
:* Product user group at [[CNMCyber.com]], which is a space for project stakeholders to receive project updates and contribute their questions and comments. The group shall be open 24/7 for asynchronous activities; a functioning group shall also meet simultaneously via video-conference on a weekly basis. The groups of [[#COTS software|COTS software]] users tend to be titled in the "CNM/Opplet COTS-name Users" format.
 +
:* Product pages at [[CNM Wiki]], which are wikipages on which the product is being developed. The pages that represent [[#COTS software|COTS software]] tend to be titled in the "CNM/Opplet COTS-name" format. They belong to the [[:Category:CNM Cyber products|"CNMCyber products" category]].
 +
:* Endeavor pages at [[CNM Wiki]], which are wikipages on which the endeavor is being developed. The pages that represent endeavors on [[#COTS software|COTS software]] tend to be titled in the "COTS-name for CNMCyber/Cloud/Opplet/Farms" format. They belong to the [[:Category: CNMCyber endeavors|"CNMCyber endeavors" category]].
 +
:* [[Requirements traceability matrix]], which is a grid that links requirements and their sources.
 +
:* [[Stakeholder register]], which is a database that lists [[stakeholder]]s of the endeavor. Those stakeholders include the [[#Administrators|Administrators]], [[CNMCyber Team]], those [[#Contractors|Contractors]] that work on the endeavor, as well as regulatory bodies that define and/or constrain endeavor's efforts issuing applicable laws and binding requirements. The complete register contains analysis of stakeholders.
  
===Authorized projects===
+
: To coordinate the project studies, the responsible ''Coord'':
: Those projects that are fully funded, authorized, and available to the ''Coords'' are published on the [[CNM Cloud Usable]] wikipage.
+
:# '''Identifies''' those available resources that should or can be used in project activities. Human resources include [[CNMCyber Team]]. Other resources include those presented in the initial [[WorldOpp Pipeline]] courses, on [[CNM Wiki]], existing tools, materials, prototypes, and finished products available at [[CNMCyber]], on the [[World Wide Web]] and other sources. For off-the-shelf products, developer websites and professional resources like https://stackoverflow.com/ are usually helpful.
 +
:# '''Analyses''' the identified resources with regard to their nature, usefulness, and potential impact while organizing that data on [[CNM Wiki]].
 +
:# '''Selects''' those resources and those data that may be used in the project activities.
 +
:# '''Composes''' the [[asset register]], [[competency register]], and [[stakeholder register]].
 +
:# '''Forms''' a product user group at [[CNMCyber.com]] if this group hasn't formed yet; refreshes the group if it has already formed.
 +
:# '''Organizes''' weekly video conferences, as well as other meetings and activities of the user group. Topics of those events shall address the product, its production when the product is under development, work of its administrators, user feedback and market trends.
 +
:# '''Invites''' everyone who is interested in product's development to the user group.
 +
:# '''Offers''' those experts and specialists who have knowledge, skills, and abilities useful for product specifications or project planning to discuss the deliverable and/or project.
 +
:# '''Interviews''' those experts and specialists who agreed to discuss the deliverable and/or project.
 +
:# '''Collects''' data related to (a) the project deliverables and their production when this deliverable hasn't been deployed yet and (b) product performance when the deliverable has already been deployed, as well as its industry trends.
 +
:# '''Makes''' sure that all of the collected data sources are listed in the [[asset register]], [[competency register]], or [[stakeholder register]].
 +
:# '''Publishes''' the collected data on [[CNM Wiki]]. Product data shall be published on the product pages; project data shall be published on the project pages. The published data shall refer to its sources; however, personal data publication requires permissions. From a legal point of view, we cannot publish the confidential information of our contractors, for instance.
 +
:# '''Creates''' a [[requirements traceability matrix]] to trace the product and project requirements from the selected sources to perspective project deliverables.
 +
:# '''Updates''' the [[asset register]], [[competency register]], [[stakeholder register]], [[requirements traceability matrix]], as well as project and product pages when ever new data from existing and/or new sources emerge.
 +
:# '''Requests''' assistance of the [[#Administrators|Administrators]] when additional resources are needed.
 +
:# '''Reports''' on progress of the project studies using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
===Project results===
+
: The project studies start after the [[project charter]] is approved. Collection of requirements, product envisioning, project planning, production, as well as commissioning and management of a product always reveals new factors and data. That is why the studies end with the project closure.
: The results of the projects may be classified in four levels:
 
:# '''[[Project scrap]]s''', which are intermediate products that either become parts of the [[#Products to be developed|Products to be developed]] or have been decommissioned before the end of the project. Nevertheless, the outputs cannot be produced without those scraps. As they say, sausage making is messy, but no sausage can be produced without that mess.
 
:# '''[[Project output]]s''' are the things that are produced during the project and kept after its end. Besides the [[#Project deliverables|Project deliverables]], the outputs may include other-than-the-project [[#Records|Records]] such as publications and [[#Documents|Documents]] such as blueprints that have been developed and commissioned in order to produce the [[#Project deliverables|Project deliverables]].
 
:# '''[[Project outcome]]s'''. On the ''Coord's'' side, the outcomes are those [[KSA]]s that the ''Coord'' has obtained during the project coordination. On the other stakeholders' side, the outcomes are something for which the [[#Project deliverables|Project deliverables]] have been produced.
 
:# '''[[Project impact]]s''', which are consequences of the project, its outputs and outcomes on a society. Beyond the ''Coord's'' work, some projects, for instance, may initiate further meetings, documents, actions, and changes.
 
  
===Projects of projects===
+
===Specifying the deliverables===
:The most of projects consist of several projects. For instance, [[#Project results|Project results]] and results of the ''Coords<nowiki>'</nowiki>'' work are different phenomena. Among the ''Coords<nowiki>'</nowiki>'' outputs, [[#Meetings|Meetings]], [[#Documents|Documents]], and [[#Communications|Communications]] usually belong to project scraps. If we consider the ''Coords<nowiki>'</nowiki>'' work as micro-projects, we can say that outputs of micro-projects tend to become scraps for small projects and, furthermore, outputs of small projects tend to become scraps for macro-projects.
+
: The main goal of the product specification activities is to get the deliverable in a [[state of certainty]], which is determined by the presence of a validated [[product specification]]. This specification is needed to compare the created deliverables against their requirements. To coordinate the product specification, the responsible ''Coord'':
 +
:# '''Collects''' data related to [[stakeholder requirement]]s for the project deliverables and [[product specification]]s using the [[asset register]], [[competency register]], and [[stakeholder register]]. This collection includes communications with stakeholders and review of documents and other assets that are registered.
 +
:# '''Examines''' available prototypes, unfinished and finished products against the collected data.
 +
:# '''Analyses''' the collected product data while organizing that data on [[CNM Wiki]].
 +
:# '''Clarifies''' the collected data based on the examined prototypes and finished products.
 +
:# '''Identifies''' those target audiences who are supposed to use future deliverables.
 +
:# '''Creates''' imaginary personas that would represent each of the identified audience.
 +
:# '''Produces''' [[stakeholder requirement]]s for each created persona using [[CNM Wiki]].
 +
:# '''Composes''' [[product specification]]s based on the produced [[stakeholder requirement]]s using [[CNM Wiki]].
 +
:# '''Traces''' in a [[requirements traceability matrix]] the formalized [[stakeholder requirement]]s from their sources to perspective project deliverables.
 +
:# '''Makes''' sure that (a) the [[product specification]] supports the [[stakeholder requirement]]s and (b) all the deliverable data is published on [[CNM Wiki]].
 +
:# '''Checks''' [[product specification]]s for completeness. This completeness shall be characterized by the presence of conditions for (a) functionality, (b) applicability, and (c) manageability of the deliverables. Conditions for functionality should include measures for product's performance. Conditions for applicability should include measures for product's deployment, testing, diagnostics, accessibility, serviceability, protection, and capacity to recover after disasters; these measures must be documented in product's [[standing operational procedure]] ([[standing operational procedure|SOP]]). Conditions for manageability should include measures for product's monitoring, periodic audits and revisions, as well as timely software updates for the [[#COTS software|COTS software]] products.
 +
:# '''Updates''' the [[stakeholder requirement]]s and [[product specification]]s when ever new data from existing and/or new sources emerge.
 +
:# '''Requests''' assistance of the [[#Administrators|Administrators]] when additional resources are needed.
 +
:# '''Reports''' on progress of the product specification using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
: As a rule, any project deliverable utilizes outputs from other projects as its scrap. Making a new accessory, for example, is impossible without documents that describe the requirements, and drawing up requirements is impossible without meeting events.
+
:The product specification opens when [[CNMCyber Customer]] approves the [[project charter]] and ends with the project closure.
  
===Choice of projects===
+
===Planning the project===
: The ''Coords'' have the right to choose the project that suit them best. The work of the ''Coords'' is paid when they work on those projects that are published on the [[CNM Cloud Usable]] wikipage. In addition, the ''Coords'' are encouraged to propose their own projects.
+
: The main goal of the project planning is to decide how the project deliverables will be developed. Those activities shall result in validated [[acceptance criteria]]. In other words, planning is getting a description of project activities that allows this development to be certain. To coordinate the project planning, the responsible ''Coord'':
 +
:# '''Collects''' data related to [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]] using the [[asset register]], [[competency register]], and [[stakeholder register]]. This collection includes communications with stakeholders and review of documents and other assets that are registered.
 +
:# '''Examines''' the existing products that are going to be further developed if they are available.
 +
:# '''Analyses''' the collected project data while organizing that data on [[CNM Wiki]].
 +
:# '''Formulates''' the difference between what actually is and what is needed to be. The existing products are what actually is, while the specified deliverable is what is needed to be. The project activities shall address this identified difference; they represent what needs to be done.
 +
:# '''Drafts''' a [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]], based on the resources recorded in the registers.
 +
:# '''Makes''' sure that the [[acceptance criteria]] supports the [[project scope baseline]] and [[project schedule baseline]].
 +
:# '''Submits''' the drafted [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]] for [[CNMCyber Customer]]'s confirmation.
 +
:# '''Publishes''' the [[project scope baseline]], [[project schedule baseline]], and [[acceptance criteria]], after their confirmation, on [[CNM Wiki]]. To make future negotiations successful, neither the [[project cost baseline]] nor other financial data should be available to the general public.
 +
:# '''Requests''' (a) assistance of the [[#Administrators|Administrators]] when additional resources are needed and/or (b) changes to the [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and/or [[acceptance criteria]] when new data from existing and/or new sources of data prompt so.
 +
:# '''Reports''' on progress of the project planning using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
==Products to be developed==
+
: Similarly to [[#Specifying the deliverables|Specifying the deliverables]], the project planning opens when [[CNMCyber Customer]] approves the [[project charter]] and ends with the project closure. However, the project plan not entirely, but depends on product specification, while the specification rarely does. The deliverable to be dictates what needs to be done, not vice versa. Only impossibility of the specified deliverable production can initiate the change to its product specification.
The ''Coords'' [[#What Coords work on|work on]] [[#Meetings|Meetings]], [[#Documents|Documents]], [[#Records|Records]], and [[#Communications|Communications]] to facilitate development of the [[project output]]s or those products that the project directly produces. Those products belong to various [[#Product categories|Product categories]], [[#Product states|Product states]], and [[#Development areas|Development areas]].
 
  
===Project deliverables===
+
===Hiring the contractors===
: Projects are undertaken to create project deliverables. Project customers initiate projects in order to get something in return. Normally, customers fund projects because of its expected deliverables. Any project is expected to deliver some outputs. In other words, project deliverables are those products for which development the project exists.
+
: At the ''Cyber'', the main goal of hiring of project contractors is to expand the ''Coords<nowiki>'</nowiki>'' expertise and resources in order to accomplish the project. The contractors must be hired to produce anything beyond [[#What Coords produceWhat Coords produce]]; however, the contractors can also be hired to produce special [[#Communications|Communications]], [[#Documents|Documents]], [[#Meetings|Meetings]], and/or [[#Records|Records]].
  
: For instance, when a contractor is hired to produce a particular thing, that very thing should be the deliverable of that project. Literally, the contractor is expected to ''deliver'' the deliverable to complete the project.
+
: In order to be hired, though, the prospective contractors need to be sourced first and selected second. Moreover, the sourcing, selecting, and hiring require their own "cycle phases" such as request formalization, background studies, contractor competencies' specification, recruitment plan, as well as this plan execution.
  
: Project deliverables are rarely simple things. At the ''Cyber'', any project deliverable is a package of the [[#Products to be developed|Products to be developed]]. For instance, the [[Farm for Campus]] project is expected to deliver [[CNM Campus Farm]] and [[Campus Farm Lab]] as software, their presentations on various media resources, updates to the [[CNM Cyber Orientation]] course, and a set of exercises for the learners.
+
: All of those activities shall result in fully-executed [[Careerprise contractor agreement]]. To coordinate the hiring of contractors, the responsible ''Coord'':
 +
:# '''Evaluates''' whether third-party contractors are needed and, if they are needed, what [[#Types of contractors|Types of contractors]] should be looked for.
 +
:# '''Provides''' data to [[CNMCyber Customer]] for making the decision either to bring external contractors on the board or not to bring. The positive decision assumes [[CNMCyber Customer]]'s willingness to finance the contractor's work.
 +
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities to identify those available resources that should or can be used in sourcing, selecting, and hiring of contractors.
 +
:# '''Collects''' data related to sourcing, selecting, and hiring of contractors that are able and available to satisfy ''Cyber'' needs using the [[asset register]], [[competency register]], and [[stakeholder register]]. This collection includes communications with stakeholders and review of documents and other assets that are registered.
 +
:# '''Analyses''' the collected sourcing, selecting, and hiring data while organizing that data on [[CNM Wiki]].
 +
:# '''Composes''' solicitation materials including a [[request for proposal]] ([[request for proposal|RFP]]), which is a solicitation announcement, and the list of its placement options.
 +
:# '''Submits''' the composed materials to the [[CNMCyber Project Manager]] for their publication.
 +
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities to update a list of potential contractors in the [[stakeholder register]].
 +
:# '''Invites''' the listed contractors to discuss project's deliverables and [[product specification]]s, as well as the project including [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]].
 +
:# '''Treats''' the discussions with the contractor candidates as primary sources of data to revisit the [[#Studying the backgrounds|Studying the backgrounds]] activities. Hiring people is a great way to learn about aspects of an endeavor. Conducted interviews shall add to the [[CNM Wiki]] documentation. Particularly, that means publishing on [[CNM Wiki]] the data related to the deliverables and schedules extracted from the discussions. As a rule, meetings with contractors serve two different purposes: (a) selection of right candidates and (b) learning about the deliverables and/or project. Historically, requirements are refined during the recruitment process. If the requirements cannot be formulated during the recruitment process, they themselves shall become deliverables of an intermediary project.
 +
:# '''Assists''' in selection of the most promising candidates, negotiations, and other processes aimed to source and select contractors.
 +
:# '''Makes''' sure that the contractors are being selected not only because of their ability to speak, write, look well, get in touch on time, respond quickly, and so on, but, primarily, because of their ability to satisfy the [[#Funded demands|Funded demands]] this contractor is being hired to resolve. Specifically, [[CNMCyber Customer]]'s:<ol type="a"><li>Approval of [[acceptance criteria]] makes possible hiring of developers.</li><li>Validation of a [[standing operating procedure]] ([[standing operating procedure|SOP]]) makes possible hiring of servicers.</li><li>Authorization of paid hours makes possible hiring of on-call specialists.</li></ol>If no job vacancy document is available at the moment, the candidates shall be offered to help developing it on a volunteer basis. If the need exists, but all internal and external resources to develop the document are exhausted, the ''Coord'' shall initiate a preliminary project to produce that document.
 +
:# '''Initiates''' a preliminary project to document the [[#Funded demands|Funded demands]] if own efforts of the ''Coord'' didn't produce that document.
 +
:# '''Drafts''' a [[Careerprise contractor agreement]] while using its blueprint and entering subject matters to negotiate or agree.
 +
:# '''Provides''' the prospective and/or selected contractor with the drafted agreement.
 +
:# '''Informs''' [[CNMCyber Customer]] about the readiness of the contract or contract for the full execution. The execution of the contract authorizes the financing of the production of the deliverables by contractors. One of the consultants may be contracted for consultations and/or participation in video conferences.
 +
:# '''Requests''' (a) assistance of the [[#Administrators|Administrators]] when additional resources are needed and/or (b) changes to the [[request for proposal]] ([[request for proposal|RFP]]) when new data from existing and/or new sources of data prompt so.
 +
:# '''Reports''' on new contractor hires using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
===Deliverables vs by-products===
+
: The hiring of contractors opens when [[CNMCyber Customer]] approves the ''Coord's'' request for the hire. It ends with full execution of the [[Careerprise contractor agreement]].
: Those [[project output]]s that are not [[#Project deliverables|Project deliverables]] may be called project by-products. Their range is huge; there are some imaginary scenarios:
 
:* A contractor submitted more products than the contract had required. If they are further deployed, those additional products would be by-products of this project.
 
:* Contractor's performance demonstrated advanced competencies in something unrelated to the project. The updated records are by-products of this project.
 
:* While organizing a meeting, the ''Coord'' encountered the problem of the policy's incompleteness. The project customer agreed to fund the policy's updates. The updated policy is a by-product of the project
 
  
===Product categories===
+
===Working with contractors===
: The aim of ''Cloud's'' developments is to produce new products or modify existing products. Those new and modified products that are produced during those developments are called [[deliverable]]s. They may include one or more of the following:
+
: The main goal of collaboration with endeavor contractors is to enable the [[#Contractors|Contractors]] to deliver rightly right project deliverables or other requested services. To coordinate collaboration with contractors, the responsible ''Coord'':
:* '''Administrative procedures''' for personnel, financial, accounting and legal operations of the organizational structure behind the ''Cloud''.
 
:* '''Applications''' known as [[CNM app]]s that can be used by current and potential students, apprentices and employees of the ''Cyber''.
 
:* '''Content''', such as texts, illustrations and multimedia materials that can be used in [[CNM app]]s.
 
:* '''[[#Documents|Documents]]''' are the single most important deliverable of the ''Coords's'' work. Because of that fact, a separate section of this wikipage, [[#Documents|Documents]], is dedicated to them.
 
:* '''Events''', especially [[CNM Cyber event]]s, in which real people participate physically or remotely, such as interviews of candidates for contractors, meetings of professionals and conferences for potential participants. A separate section of this wikipage, [[#Meetings|Meetings]], is dedicated to them.
 
:* '''Information''' resources for attracting potential partners and clients of the ''Cyber'', such as websites, social media materials, and mailing lists, as well as standard messages, invitations and advertisements.
 
:* '''Labor resources'''. All products require work on them. However, the development of human resources is also one of the end products of the project, and in terms of developing the professional competencies of the ''Coords'', its main goal.
 
:* '''Marketing campaigns''', which are endeavors to reach out to current and potential customers in order to gain their attention, build their interest, arise their desire to utilize the ''Cyber'' opportunities and not the products of the competitors, as well as to motivate them to act in that direction.
 
:* '''Partnerships''', which are contractual agreements to mutually develop and market offers. Historically, the ''Cyber'' team partnered with two Microsoft stores, in Pentagon City Mall and Tysons Corner Center, several employers, training providers, governmental, and non-profit organizations.
 
:* '''Positions''', which are documented workplaces of associates included in the organizational structure. This very wikipage is the development of one of the ''Cyber'' positions. Moreover, the ''Coords'' are welcomed to own their role, which assumes both (a) developing and updating general instructions, policies, and/or recommendations for the ''Coords'' and (b) contributing to and grooming of the backlog of the ''Coord's'' tasks at the [[CNM Cloud Usable]] and related wikipages.
 
:* '''Relationships''' with potential and existing clients such as exhibitors, contractors and partners. Stakeholders are involved in communications through (a) hiring contractors to turn those descriptions that the [[#Customer|Customer]] approved into the [[#Products to be developed|Products to be developed]], (b) hiring employees for developed positions, (c) participation of potential the ''Cyber'' participants in events organized by the project.
 
:* '''Software''' that can be used in the ''Cloud''.
 
:* '''Structures''' such as an [[organizational structure]] to organize the work of [[#Personnel|Personnel]]; their rights and duties are determined by positions.
 
:* '''Testing''' of project inputs and [[deliverable]]s under development. At the ''Cyber'', those projects that are undertaken in order to obtain testing results only are rare. The ''Coords'' execute the overwhelming majority of testing while obtaining other deliverables or simply utilizing existing ''Cyber'' products such as this very wikipage.
 
  
===Personnel development===
+
:# '''Serves''' as an liaison between [[CNMCyber Customer]] and contractors, reporting problems that need to be resolved.
:In terms of the development of human resources, the results of the work of the ''Coord'' can be:
+
:# '''Organizes''' videoconferences or other meetings of parties interested in the project, especially those necessary to resolve problems arising during the project.
:# Sourcing and orientation of contractors and new ''Coords'' by:
+
:# '''Collects''' data related to the contractor performance.
:#* Development of ads, own website and other resources.
+
:# '''Analyses''' the collected data related to contractor performance while organizing that data on [[CNM Wiki]].
:#* Placement of ads on specialized sites, social networks such as [[Telegram]], [[TikTok]], and [[Instagram]], as well as other channels.
+
:# '''Initiates''' the process of paying contractors for their work. The process shall be described in a special [[standing operating procedure]] ([[standing operating procedure|SOP]]). Prior to creating it, this start of the process implies a request to the manager or [[CNMCyber Customer]].
:#* Conducting video conferences and other events for interested parties.
+
:# '''Requests''' (a) assistance of the [[#Administrators|Administrators]] when additional resources are needed and/or (b) changes to the fully-executed [[Careerprise contractor agreement]] when new data from existing and/or new sources of data prompt so.
:#* Finding partners among commercial, public and government organizations.
+
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities when new data or new sources of data emerges in order to revisit further the [[#Specifying the deliverables|Specifying the deliverables]] and [[#Planning the project|Planning the project]] activities.  
:# Development of professional knowledge, skills and abilities of the existing workforce and new recruits. That includes facilitating of training and participating in mentor-[[protégé]] arrangements.
+
:# '''Presents''' the progress of collaboration with contractors, plans and possible concerns about that collaboration during [[CNMCyber This Week]] meetings.
  
===Development areas===
+
: The collaboration with contractors opens when their [[Careerprise contractor agreement]] is fully executed. It ends with the closure of the agreement.
: Students in practice are encouraged to suggest their project topics and development areas. Those projects that are published on the [[CNM Cloud Usable]] wikipage are grouped in the following areas:
 
:* '''Administration''' of the ''Cyber'' project, covering personnel, legal, financial and organizational issues.
 
:* '''Cloud'''. The most complete description of all technical projects is published on the [[CNM Cloud Usable]] wikipage. Based on the approved technical documentation, the results of the ''Coord's'' work can be a missing system or part of it, software, system content, consumer service, and, in general, the work of what did not work. As an information technology complex, the ''Cloud'' consists of:
 
:*# [[CNM Farms]], including tools for their [[high availability]] and recovery.
 
:*# [[Opplet]] that serves both end-user applications called [[CNM app]]s and end-users directly.
 
:*# [[CNM app]]s as software. Some application developments concern only their software, some - only the content used in the provision of services, some developments combine both.
 
:* '''Support''' for end-users, potential participants and partners of the ''Cyber''.
 
:* '''Outreach''' to participants in the labor market and business services market.
 
:* '''Career services''', including vocational guidance, training and employment with the support of volunteers and [[CNM app]]s, as well as business services for project participants.
 
  
: Some products may belong to more than one area. For example, a hands-on training session is a service, but the announcements during it may be for the purpose of being in the market. Apps can be considered software, but apps that are capable and full of content are services first and foremost.
+
===Creating the deliverables===
 +
: The main goal of deliverable creation activities is to create rightly right deliverables. "Right" means that every deliverable shall be in a [[state of capability]], which is determined by the fact that the deliverable meets all the [[product specification]]s that have been approved for this deliverable. "Rightly" means that the aggregate of creation activities match the agreed [[acceptance criteria]].
  
==States and readiness==
+
: At the ''Cyber'', [[#Contractors|Contractors]] create [[#Project deliverables|Project deliverables]]. To coordinate the deliverable creation, the responsible ''Coord'':
 +
:# '''Initiates''' hiring of development contractors.
 +
:# '''Plays''' roles of the [[product owner]] and/or [[project owner]] in the absence of other members of [[CNMCyber Team]] assigned to those roles. In that case, the ''Coord'' decides how, within the framework of the approved requirements, the deliverable and the project should be.
 +
:# '''Tests''' the deliverable and, if necessary, its parts.
 +
:# '''Collects''' data related to the deliverables under development and their production.
 +
:# '''Analyses''' the collected project data while organizing that data on [[CNM Wiki]].
 +
:# '''Monitors''' the development and execution of the project, including compliance with the budget, schedule and scope of work.
 +
:# '''Inquiries''' about changes to the [[project charter]], [[product specification]], [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and/or [[acceptance criteria]] when new data from existing and/or new sources of data prompt so.
 +
:# '''Organizes''' a closed-from-the-public-view project space on [[CNM Lab]] for work on the deliverable in addition to the project wikipage on [[CNM Wiki]].
 +
:# '''Invites''' the hired contractor to the project space.
 +
:# '''Reports''' to [[CNMCyber Customer]] on the status of the project, collecting, analyzing and summarizing information and trends.
 +
:# '''Treats''' creation of deliverables as primary source of data to revisit the [[#Studying the backgrounds|Studying the backgrounds]] activities.
 +
:# '''Makes''' sure that the created deliverables (a) represent a complete bundle of products that are listed in the [[Careerprise contractor agreement]] and (b) satisfy their [[acceptance criteria]].
 +
:# '''Recommends''', after the contractor informs about the completion of project work, either (a) acceptance of the deliverables or (b) refusal to accept those deliverables while providing [[CNMCyber Customer]] with explanations for that refusal.
 +
:# '''Requests''' assistance of the [[#Administrators|Administrators]] when additional resources are needed.
 +
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities when new data or new sources of data emerges in order to revisit further the [[#Specifying the deliverables|Specifying the deliverables]] and [[#Planning the project|Planning the project]] activities.
 +
:# '''Reports''' on progress of the deliverable creation using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
===Product states===
+
: The deliverable creation opens when [[CNMCyber Customer]] authorizes its financing and ends when the deliverables are accepted. To expedite the project, the creation may start before its [[acceptance criteria]] have developed.
: The ''Coords'' work to bring the item into one or more of the following states:
 
:# '''[[State of acknowledgment]]'''. In this state, the future deliverable exists in the form of a noticed and documented idea.
 
:# '''[[State of certainty]]'''. In this state, the future deliverable exists as a validated [[deliverable charter]].
 
:# '''[[State of capability]]'''. In this state, the functional deliverable has already been produced in accordance with all the requirements that have been approved for it.
 
:# '''[[State of applicability]]'''. In this state, the deliverable is not only functional, but can also be used for the purpose for which it was produced in ways that are described by a validated [[operation credential]].
 
:# '''[[State of manageability]]'''. In this state, the deliverable is not only used for the purpose for which it was produced, but also controlled, that is, the product undergoes periodic revisions and is either improved and its characteristics are improved, or withdrawn from service.
 
: In practice, these states do not always represent a hierarchy of five levels, in which the higher level includes the states of the lower levels. However, the ''Coords'' should strive for this ideal, for example, it is impossible to fully talk about applicability without capacity, manageability without certainty, and so on.
 
  
===Devices of certainty===
+
===Commissioning the product===
:# '''[[Business requirement]]s'''. Description of the needs for which the development of the deliverable is undertaken.
+
: The main goal of the product commissioning is to obtain the product in its [[state of applicability]], which is determined by the fact that the deliverable is not only functional, but can also be sustainably used for the purpose for which it has been created. In simple words, the commissioning is a transfer of the accepted deliverables from the contractor into ''Cyber'' operations. To coordinate this commissioning, the responsible ''Coord'':
:# '''[[Stakeholder requirement]]s'''. Description of the future deliverable made on behalf of various types of its stakeholders.
+
:# '''Clarifies''' with [[CNMCyber Project Manager]]s which members of [[CNMCyber Team]] will: (a) deploy the newly-deployed product if it hasn't been deployed yet, (b) test the newly-deployed product, (c) restrict access of the development contractors to the product and product's classified documentation, (d) access the classified documentation on [[CNM Lab]], (e) establish new product operations based on its [[standing operating procedure]] ([[standing operating procedure|SOP]]), and (f) manage hiring of service contractors.
:# '''[[Deliverable depiction]]s'''. Representation in words, images, wireframes, mockup models, and/or [[prototype]]s of a deliverable to be created. [[Prototype]]s (from the Greek "prōtos" meaning "first", "original" and "typos" meaning "imprint", "pattern"). Instances, samples or models, following the example of which others are made or finalized. Prototypes of the deliverable are often built to test a perception, concept, or process. Prototypes can either be selected from existing products or produced during a project.
+
:# '''Initiates''' (a) deployment of the newly-deployed product if it hasn't been deployed yet, (b) [[beta testing]] of the newly-deployed product, (c) restrictions of the development contractors' access to the product and product's classified documentation, (d) new administrator's access to the classified documentation on [[CNM Lab]], (e) establishment of new product operations based on its [[standing operating procedure]] ([[standing operating procedure|SOP]]), and (f) hiring of service contractors.
:# '''[[Deliverable specification]]s'''. Set of tasks for deliverable developers regarding its required characteristics.
+
:# '''Collects''' data related to the product commissioning.
:# '''[[Work specification]]s'''. Description of the conditions for the production of the future deliverable.
+
:# '''Analyses''' the collected data related to product commissioning while organizing that data on [[CNM Wiki]].
:# '''[[Deliverable charter]]'''. The subject and related matters of a [[contract]] to create a [[deliverable]]. The complete charter includes its [[business requirement]]s, [[stakeholder requirement]]s, [[product concept]]s, [[deliverable specification]]s, and [[work specification]]s, as well as:<ol type="a"><li>[[Project scope baseline]]. </li><li>[[Project schedule baseline]]. </li><li>[[Project budget baseline]]. </li><li>[[Acceptance criteria]]. </li></ol>The validated charter must be approved by both the [[#Customer|Customer]] and the developers. The contract is a legally binding agreement between the [[#Customer|Customer]] and a contractor for the production of a product. The complete contract may consist of the matter and other details such as dates, statuses, ownership, representation, indemnification, confidentiality, communications, warranties, and miscellaneous provisions.  
+
:# '''Publishes''' the documentation received from the contractor on the ''Cloud'' resources. Internal, closed to the public, documentation, such as administrator access to installed software, is published on [[CNM Lab]]. The documentation that can be open to the public without restrictions is published on [[CNM Wiki]].
 +
:# '''Requests''' assistance of the [[#Administrators|Administrators]] when additional resources are needed.
 +
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities when new data or new sources of data emerges in order to update the [[#Managing the product|Managing the product]] activities.
 +
:# '''Reports''' on progress of the product commissioning using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
The consent can take two forms:<ol type="1"><li></li><li>[[Standard operating procedure]] ([[SOP]]). A detailed description of the procedures required for production of the deliverable.</li></ol>A valid consent must include deliverable acceptance criteria as well as either:<ol type="a"><li>schedule and budget.</li><li>the principles by which the terms and costs of work will be determined.</li></ol>Deliverable acceptance criteria should reflect the scope of work.
+
: The product commissioning opens when the deliverables are accepted and ends when the product is ready to be used in ''Cyber'' operations.
  
===Status reports===
+
===Managing the product===
: While working on the deliverable, the ''Coords'' are expected to report their project status. In [[CNM Agile]] framework, these statuses are reported at the product line wikipage, [[CNM Cloud Usable]], using the following readiness levels for each [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]]:
+
: Two main goals of product management are (a) to obtain the product in a [[state of manageability]] and (b) to keep it in this state. The state is determined by the fact that the product is not only used for the purpose for which it was produced, but also controlled. This management includes both maintenance and improvement of product performance, as well as decisions to end its life or replace. To coordinate the product management, the responsible ''Coord'':
:* '''[[Not started status|Not started]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] hasn't started yet.
+
:# '''Monitors''' product usage, administrator performance, user feedback, industry trends, best practices, and situations in those markets that are associated with the product, its alternatives, and components.
:* '''[[In progress status|In progress]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been started, but the state/device has not yet been submitted for the approval.
+
:# '''Treats''' the product management monitoring as primary sources of data to revisit the [[#Studying the backgrounds|Studying the backgrounds]] activities.
:* '''[[Cancel status|Cancel]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been cancelled.
+
:# '''Collects''' data related to the product performance and its administration.
:* '''[[Submitted status|Submitted]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been submitted for the approval.
+
:# '''Analyses''' the collected data related to product management while organizing that data on [[CNM Wiki]].
:* '''[[Done status|Done]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been approved. With exceptions of the [[state of certainty]], the [[#Customer|Customer]] approves the status. With regard to the [[state of certainty]], its approval also requires the developer's consent.
+
:# '''Identifies''' problems and opportunities to improve the product or replace the product with other solutions.
 
+
:# '''Inventories''' the problems and opportunities that have been identified using ''Cyber's'' [[idea management software]] when it is available; temporarily, [[CNM Wiki]] shall be used.
==Project factors==
+
:# '''Presents''' the problems and opportunities identified in the inventory to [[CNMCyber Customer]] for making decisions about opening new projects.
 
+
:# '''Requests''' assistance of the [[#Administrators|Administrators]] when additional resources are needed.
===Administrators at Cyber===
+
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities when new data or new sources of data emerges.
: For the purposes of this very wikipage, [[administration]] is defined as the set of endeavors undertaken to run something. At the ''Cyber'', several types of administrators can be distinguished depending on the category of that "thing":
+
:# '''Reports''' on progress of the product management using the [[CNMCyber Usable]] wikipage.
:* '''Cyber administrators''' are those of the [[#Personnel|Personnel]] who manage the ''Cyber's'' development, operations, and product groups. The project manager is the CNM Cyber administrator by default; he or she can appoint other members of the [[#Personnel|Personnel]] to administer a particular group of developments, operations and products or the ''Cyber'' as a whole.
+
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
:* '''Product administrators''' are those of the [[#Personnel|Personnel]] whom CNM Cyber administrators have granted administration of a particular product. During its production, the deliverables are administered by the ''Coords''. The superior administrator of each product is at least one of the CNM Cyber administrators.
 
:* '''Application administrators''' are administrative user roles in [[CNM app]]s. For example, an administrator of [[CNM Wiki]] can protect select wikipages from editing by non-admins. Application administrators are a software feature, which only system administrators may assign. Organizationally, CNM Cyber administrators must request assigning admin roles to select members of the [[#Personnel|Personnel]] and, vice versa, request removing them when there is no longer need.
 
:* '''System administrators''' are dedicated positions intended for those associates who administer the technological systems of [[CNM Farms]]', [[Opplet]]'s, and [[CNM app]]s' software. The highest administrator of each attachment is at least one of the system administrators, so the latter can be described as super administrators of applications.
 
 
 
===Customer===
 
: The customer provides requirements for future products and pays project budgets. In simple words, the customer orders products and pays for their production. The work of the ''Coord'' is paid insofar as it is part of the development of the product. The customer implies that the ''Coord'' works out projects in accordance with the instructions set out on this wikipage. Out of the goodness of heart and for professional training purposes, the customer may do the work of the ''Coord'' temporarily as long as the customer believes that the ''Coord'' will someday be able to work independently.
 
 
 
===Personnel===
 
:# '''Coords''' or coordinators contribute to the implementation of projects by acting in accordance with the [[#What Coords do|What Coords do]] section.
 
:# '''System administrators''' ensure the stability of the ''Cloud's'' operations and advise on technological developments.
 
:# '''Recruiters''' ensure that the recruiting process is in place, there are candidates for Coords and, with the approval of the [[#Customer|Customer]], for other full-time positions in the recruiting "pipeline", and also advise on those developments that relate to recruiting. In their projects, the ''Coords'' also play the role of recruiters and take over the hiring of contractors. Unlike recruiters, the ''Coords'' discuss requirements and other project documents with candidates. The ''Coords'' turn to recruiters in cases where their own competencies or resources are not enough to attract contractors.
 
:# '''Project manager''' is responsible for resolving administrative, personnel, financial, legal and organizational issues. In particular, the manager assigns projects to the Coordinators, places advertisements for hiring contractors, gives the coordinators recruiter access and pays the project budgets. The manager can be called a "super-coordinator". If the coordinator works on one project, which he himself chooses, the manager is responsible for the entire group of developments and operations, including finance, personnel, administration of the ''Coords'', and so on. At the moment, the head is replaced by the [[#Customer|Customer]], but he does it temporarily, before such a person or people are found.
 
: Although contractors are not formally part of the project staff, they are an important part of project development.
 
 
 
===Durations===
 
: The ''Coords'' work on one project, usually up to three and, in exceptional cases, up to five weeks.
 
:# In the first week, they shall get familiarized with the project. At the end of the familiarization, the ''Coord'' should be able to explain what is described on the relevant wikipages and be ready to discuss its [[Sprint Zero]] with the [[#Customer|Customer]].
 
:# From the second week to the penultimate week, they facilitate the project work in accordance with the [[#What Coords do|What Coords do]] section.
 
:# In the final week, they close the project or project part, documenting their work and the data that was uncovered during that work.
 
: Projects can overlap. For example, the last week of work on one project may be the first week of work on another project. For senior ''Coords'', there are no restrictions.
 
 
 
==Contractors==
 
With the exception of the [[#Records|Records]], the ''Coords'' rarely develop and service the [[#Project deliverables|Project deliverables]] directly or, or least, without someone else's assistance. For the most part, contractors develop and service them. The contractors perform on the basis of approved descriptions and finalized by the ''Coors'' and/or other members of the [[#Personnel|Personnel]]. The ''Coords'' participate in hiring of those contractors.
 
 
 
===Developers vs servicers===
 
===How not to hire===
 
: Here is an example of how the ''Coord'' '''should not''' hire contractors:
 
:# We find a person or several people who agree to take on this development and speak, write, look well, get in touch on time, respond quickly, and so on.
 
:# We contact (preferably by phone) to clarify their requirements for payment and promises on terms.
 
:# We award the contract to the one or the one who offers the best conditions, and let the others know in a polite and respectful way.
 
 
 
===How to hire===
 
: Here is an example of how the ''Coord'' '''should''' hire contractors:
 
:# Know the criteria that determine the [[state of certainty]].
 
:# Check if the [[state of certainty]] has been reached for the deliverable under development.
 
:# If the [[state of certainty]]:
 
:#* '''Not achieved''', check whether the resources available to the ''Coord'' without the involvement of external consultants have been exhausted. If resources are exhausted, look for external resources, such as advertising for consultants or trying to find contractors to help achieve this state. If both internal and external resources are exhausted, but the state has not been reached, issue an additional project, making the contract its desired product.
 
:#* '''Achieved''', proceed further according to the [[#How not to hire|How not to hire]] section; after completing the previous points, it makes sense.
 
: The contract must include a description of what we are to receive that satisfies measurable eligibility criteria, as well as when and for how much we will receive it. If something from the three "scope of work, terms, budget" is not defined, then we will get what we need in one case out of 100. In 99 other cases, we will get either what we do not need, or for that money , which we do not count on, or when we no longer need it.
 
  
===Contractors' interviews===
+
: Product management opens when the product is put into service and ends when the product gets retired.
: Hiring people is a great way to learn about aspects of a project and the resulting product. Perfectly conducted interviews add to the documentation for [[CNM Wiki]].
 
  
===Contractor applications===
+
==Residents' bootcamp==
: We can publish received applications, but we do not publish the names of contractors, as they did not give us permission to publish. From a legal point of view, we cannot publish the confidential information of our contractors.
+
: ''Main wikipage: [[CNMCyber Bootcamps]]''
  
==Recruiting the Coords==
+
: The ''Bootcamp'' is designed to introduce the learners to various positions, help to select the promising one, and place the learner as an apprentice into both the job and educational program. In their ''Practice'', the learners work as the ''Residents''.
  
There is no single simple indicator by which one can judge whether a person can become a successful ''Coord'' and, if so, whether similar jobs would attract and motivate him or her. One never knows unless one tries. The ''Cyber'' provides everyone with opportunities to:
+
: The ''Resident'' is a temporary position, limited by the duration of the ''Bootcamp''. Not everyone is attracted to work on creating something new. Not everyone is able to work in conditions of uncertainty.
# Get trained to start working in an entry-level position. Three courses, (a) [[CNM Cyber Welcome Session]], (b) [[CNM Cyber Orientation]], and (c) [[CNM Cyber Placement]] are designed to provide the learners with theoretical knowledge.
+
:* If the job of the ''Resident'' suits the participant, he or she moves towards the business analyst, systems engineer, partner coordinator, event organizer, information structure or solution creator, product or user experience designer, and product, information resources or development manager, and other occupations in projects.
# Start working in an entry-level position of the ''Coord'' in order to get introduced to various professions practically.
 
# Identify the target profession and further continue with professional preparation.
 
 
 
===Coords' sourcing===
 
: ''Main wikipage: [[WorldOpp Sourcing]]''
 
 
 
: [[WorldOpp Sourcing]] encompasses the [[WorldOpp Outreach]] campaigns to attract attention of potential candidates and [[CNM Cyber Welcome Session]] to bring the candidates on the board.
 
 
 
===Coords' orientation===
 
: ''Main wikipage: [[CNM Cyber Orientation]]''
 
 
 
:The [[CNM Cyber Orientation]] is designed to introduce promising ''Coords'' to the [[job market]], the ''Cyber'', its team, services, and the ''Cloud''.
 
 
 
===Coords' placement===
 
: ''Main wikipage: [[CNM Cyber Placement]]''
 
 
 
: The [[CNM Cyber Placement]] is designed to introduce the learners to various positions, help to select the promising one, and place the learner as an apprentice into both the job and educational program. In their practice, the learners work as the ''Coords''.
 
 
 
: The ''Coord'' is a temporary position, limited by the duration of the internship. Not everyone is attracted to work on creating something new. Not everyone is able to work in conditions of uncertainty.
 
:* If the job of the ''Coord'' suits the participant, he or she moves towards the business analyst, systems engineer, partner coordinator, event organizer, information structure or solution creator, product or user experience designer, and product, information resources or development manager, and other occupations in projects.
 
 
:* If unable or unwilling, the participant is promoted to Contract or Systems Administrator, Usability Analyst, Accountant, Graphic Designer, Operations Engineer, Purchasing, Account Manager, and Procurement Manager and other occupations in operations.
 
:* If unable or unwilling, the participant is promoted to Contract or Systems Administrator, Usability Analyst, Accountant, Graphic Designer, Operations Engineer, Purchasing, Account Manager, and Procurement Manager and other occupations in operations.
  
: During the [[CNM Cyber Placement]] course, students should be introduced to different professions from a programmer to an accountant. The specialty will be selected based on the results of the practice, and then it will be necessary to select a curriculum with a partner and organize an internship. We hope to organize the internship ourselves, but it will be difficult to replace educational institutions. Nothing unreal is foreseen, but everything needs to be worked out. Until the third course is ready, the ''Coords'' can work on it.
+
: During the ''Bootcamp'', students should be introduced to different professions from a programmer to an accountant. The specialty will be selected based on the results of the ''Practice'', and then it will be necessary to select a curriculum with a partner and organize an internship. We hope to organize the internship ourselves, but it will be difficult to replace educational institutions. Nothing unreal is foreseen, but everything needs to be worked out. Until the third course is ready, the ''Residents'' can work on it.
 
 
==History==
 
  
 
==See also==
 
==See also==
 
===Related lectures===
 
===Related lectures===
:*[[Vacancies at CNM Cyber]]
+
:*[[Vacancies at CNMCyber]]
  
 
[[Category: CNM Cyber Welcome Session]][[Category: Articles]]
 
[[Category: CNM Cyber Welcome Session]][[Category: Articles]]

Latest revision as of 00:10, 15 April 2024

CNMCyber Coordinator (hereinafter, the Coord) is an incumbent of the graduating, final-quarter CNMCyber practice (hereinafter, the Practice) that The Economic Group has developed to practically introduce CNMCyber patrons to workspace overall. The Coords practice in executing the CNM Agile framework primarily including coordination of its separate endeavors.

The Coords don't develop CNMCyber products directly, on their own. On the contrary, they assist in hiring Careerprise contractors and working with them.

The Practice belongs to the fourth quarter of CNMCyber Bootcamps (hereinafter, the Bootcamp). This quarter's lessons are called Cyber Coordinator Bootcamp; they are designed to prepare the Coords to that Practice. The Practice is offered to those CNM Cloud Operators who successfully pass Information Technology Project Management Exam after taking the fourth quarter's classes. The graduating endeavor encompasses the learner's individual plan to land a professional job. Successful completion of the cyber coordination practice qualifies the Coords as Certified Information Technology Project Management Associates (CITPMAs). Graduation from the Role ends the Bootcamp.


Position

The Coords practice is to facilitate someone else's performance on Projects vs operations related to CNMCyber products. The Coord chooses the paid work from the Authorized work; alternatively, the Coord may propose own work, which may or may not be authorized for compensation. To learn about benefits, competencies, history, supervision, and target audiences, please consult the CNMCyber practice wikipage.

Choice of practice

By default, the Coords choose Endeavors that suit them best. CNMCyber Project Managers may ask a Coord to take an urgent or specific project when they know anything professional about the Coord. That means that the Coords have to choose their first endeavor at least.
The work of the Coords is paid when they work on those endeavors that funding is authorized on the CNMCyber Usable wikipage. That page contains links to:
Any Coord is welcome to pick any endeavor he or she would like to work on. In addition, the Coords are encouraged to propose their own endeavors.

How to start

Are you interested in getting started as the Coord? Please follow a step-by-step instruction as follows:
  1. Get professional experience as CNM Website Developer, CNM Event Organizer, and CNM Cloud Operator.
  2. Until Cyber Coordinator Bootcamp is fully developed, briefly review the following wikipages:
    1. this very wikipage since it outlines your work,
    2. CNMCyber product since this wikipage outlines the products, which development and management you are going to facilitate.
    3. If you consider working on Cyber marketables, please consult also Careerprise Funnel.
  3. Ask questions. Questions are a huge part of your work; if you cannot ask, you cannot work. If you prefer videoconferences, attend any CNMCyber This Week event. You will have opportunities to ask questions and get responses in real time.
  4. Understand why the Cyber endeavors are undertaken and what value is expected from the Coord. That's simple. If you cannot deliver what CNMCyber Customer supports, you cannot work. Everything that CNMCyber Customer supports is stated on this very wikipage.
  5. Wait for 2-3 months if you cannot understand what your objectives are. There is a chance that the course and/or videos will be developed out of this wikipage during that time. The introductory courses will be available at https://cert.cnmcyber.com after registering at https://opplet.net/user/register ; the videos will be published on CNM Tube and YouTube. Some of course wiki-materials are linked to WorldOpp Orientation, EmployableU Concepts, and CNMCyber Bootcamps wikipages
  6. Pick up your first endeavor at the CNMCyber Usable wikipage when you understand what your objectives are. You may have no idea what that particular endeavor is about. First of all, no endeavor is fully clear and, secondly, to learn about one endeavor is always simpler that to learn about many. When you really studied this very wikipage, you should know how to go about that endeavor. If you cannot pick your project, you cannot start working as the Coord.
  7. Contact CNMCyber Customer while stating (a) the endeavor you have picked, (b) what you plan to deliver, and (c) how much time you expect to work in order to deliver what you plan to deliver.
By the way, you can be paid to ask questions about this wikipage when you identify the endeavor behind that page.

Occupation

The Economic Group has created and markets the Coord's role for those who don't necessarily possess any occupation yet. At the Occupational Information Network, the closest occupation is Information Technology Project Manager; the principal difference is that the Coords don't make managerial decisions. The Certified IT Project Management Associate (CITPMA) credential is awarded to the successful Coords.
Other close occupations include Project Management Specialists, Computer and Information Systems Managers,

Administrative Services Managers Chief Executives Executive Secretaries and Executive Administrative Assistants Secretaries and Administrative Assistants Office and Administrative Support Workers Legal Secretaries and Administrative Assistants Human Resources Manager General and Operations Managers

Tools

What Coords produce

To facilitate development and/or management of CNMCyber products, the Coords produce four categories of their first-level results. They are (1) Meetings, (2) Documents, (c) Records, and (d) Communications. For the Coords, those results represent measurable outputs of the Practice.

Communications

For the purposes of this very wikipage, communications are defined as distribution of the messages that are related to the Cyber, the Cloud, as well as efforts to develop those. Particularly, the communications are used to exchange the Documents and Records; the Meetings are used to facilitate the communications.
The Coords run their communications to make development of CNMCyber products possible. These communications include:
  • Internal communications such as project and product communications, meeting invitations, reminders, moderation and discussion messages, and follow-ups.
  • External communications such as marketing campaigns, as well as distribution of outreach messages.
Marketing communications are described in the Market presence section of this very wikipage. Within the Project results, internal communications represent project scraps; they are needed to produce project outputs. External communications, especially marketing campaigns and products, represent project outputs.

Documents

Generally speaking, a document is a separate piece that (a) presents data, (b) is composed with texts and/or images, and (c) can further be edited or revised. The former document that can no longer be revised, for instance, a signed contract, becomes a record.
Probably, documents are the single most important output of the Coords's work. To facilitate development of CNMCyber products, the Coords draft, edit, groom, and manage documents. Those documents may include:
  • Blueprints, which are document prototypes useful to create final documents. For instance, the Careerprise contractor agreement wikipage is used as a blueprint to draw up contracts with individual contractors. As a rule, these target documents are published on CNM Wiki.
  • Legal drafts such as papers drafted to be signed as contracts.
  • Product documents, which are descriptions of former, existing, and future products published on CNM Wiki, as well as deliverable requirements, emails and other messages between product owners and developers, organizational and technical documentation such as standing operating procedures (SOPs), minutes of the meetings, testing and other reports, etc.
  • Project documents, which are project requirements, progress reports, emails and other messages between project owners and developers, memos with the results of project approvals, developments, meetings, and research.
Although outreach materials such as those that are used in organizing of CNMCyber events and website texts are documents, the Coords don't normally create them. Careerprise contractors, CNM Cloud Operators, CNM Event Organizers, and CNM Website Developers shall create them; however, if no contractors, developers, operators, or organizers are available, the Coords may step in.
Within the Project results, those draft and final documents are either project scraps or outputs. As the outputs, they usually accompany other CNMCyber products. For example, products normally come with instructions. However, some of documents represent whole products on their own. For example, to bundle the functional product with the instructions, those instructions were needed to be developed before.

Meetings

Generally speaking, a meeting is an occasion in which people meet to exchange data, discuss something, make decisions, and/or collaborate. Meetings occur online and/or offline in forms of verbal conversations, videoconferences, and/or webcasts.
To support development of CNMCyber products, the Coords prepare, moderate, conduct, and close meetings. Those meetings may include:
  • Hiring events, which are interviews and other meetings between contractor candidates and CNMCyber Project Manager organized to discuss potential entering into a contract and/or to make that decision.
  • Product meetings, which are meetings organized (a) to discuss deliverable features, (b) to make deliverable decisions, and/or (c) to communicate those decisions.
  • Project meetings, which are meetings organized (a) to discuss project features, (b) to make project decisions, and/or (c) to communicate those decisions.
Although CNMCyber events can be considered as meetings, the Coords don't normally organize them. Either Careerprise contractors or CNM Event Organizers shall organize them; however, if neither contractors nor organizers are available, the Coords may step in.
At the same time, the Coords shall participate, synchronically or asynchronically, in CNMCyber This Week events, which are weekly meetings of the Coords who present (a) what they accomplished last week, (b) what they plan to accomplish next week, and (c) what assistance do they need.
Within the Project results, the meetings immediately produce project scraps. Their archived recordings are Records. The meetings are used to develop Documents.

Records

Generally speaking, a record is a piece of matter that (a) presents data and (b) cannot further be edited or revised unless losing the status of a record. For instance, a signed contract, which is a record, can be used as a prototype to create new documents.
To support development of CNMCyber products, the Coords collect records, place them in designated spaces, and, if applicable, manage their storage. Special standing operating procedures (SOPs) shall designate spaces for that purpose. Those records may include:
  • Archived files such as videos, audios, textual files, as well as coded and programmed scripts.
  • Databases of contacts, competencies of contractors, characteristics of tested software, etc.
  • Enterprise records such as contracts, which are legally-binding agreements, applications and reports that are officially submitted to governmental bodies and partners, identification and other personal documents of Cyber's employees that the law requires to keep in the enterprise system, accounting records, etc. At the Cyber, enterprise records are stored at CNM Corp.
  • Product records such as approved requirements for the project deliverable are posted at CNM Wiki. To be product records, they need to be protected from unauthorized edits and belong to the Product records category.
  • Project records are kept at several spaces depending on their nature. Project reports are posted at the CNMCyber Usable wikipage. Legally-binding documents are stored at CNM Corp. Accepted deliverables are stored at CNM Lab.
  • Publications such as minutes of meetings and others textual records that reflect past events, content of CNM Lab, Page, CNMCyber.com, and Wiki, as well as those postings on YouTube, CNMCyber Meetup, and other social media that the Coords may make. There is no single place for publications' storage at the Cyber; they are posted at different media. CNM Wiki can be used for development of publications; appearance of CNM apps at the WWW can also be considered as publications.
  • Technology records such as access credentials and detailed descriptions of software used in the Cloud. At the Cyber, technology records are stored at CNM Lab.
Within the Project results, the records represent project outputs by their definition.

Endeavors

For the purposes of this very wikipage, endeavors refer to both development projects and management operations. Each endeavor can have the Coord who coordinates this endeavor and, particularly, facilitates the Contractors' performance. Each Coord chooses his or her endeavor to coordinate.

Endeavors may include several projects and/or operations, but the Coord must concentrate only on one project or operation during one week. The endeavors are listed in the "CNMCyber endeavors" category.

Authorized endeavors

Those Endeavors that are authorized to practice with are listed on the CNMCyber Usable wikipage.

Endeavor documents

At CNM Wiki, Cyber endeavors are documented using two types of wikipages:
  1. The progress on particular endeavors is reported at the CNMCyber Usable wikipage.
  2. Endeavor pages document everything, but progress reports. Those pages are listed at the "CNMCyber endeavors" category and include project documents such as project charter, asset register, competency register, stakeholder register, requirements traceability matrix, project scope baseline, project schedule baseline, project cost baseline, and acceptance criteria.

Projects vs operations

The Coords work and/or facilitate someone else's work on endeavors, which are either:
Regardless of work on projects or operations, the Coords are always engaged in the Studying the backgrounds activities and can be engaged in the Hiring the contractors and Working with contractors activities.

Sets of processes

Any endeavor can be viewed as sets of processes. On that very wikipage, those processes are grouped in nine sections of What Coords do.
However, every of those groups, in fact, are separate developments on their own. For instance, the project formalization shall result in a project charter, but this document may be considered as an output of a separate development that requires its own formalization, studies, specification, planning, creation, and commissioning. Sometimes, it also requires hiring contractors and working with them. Thus, the sections of What Coords do show just some level of tentative divisions and do not represent definite classifications.

Why endeavors

In business, a combination of two or more projects and, possibly, some ongoing operations, is often called a program. In this sense, a program refers to a set of structured activities that is undertaken on a systematic basis.
The term, endeavor, is chosen to separate the work that is available to the Coords from complex and lengthy programs. Since the Coords choose their endeavors to coordinate, Coords' endeavors are not undertaken systematically.

What Coords do

The Coords' work can be divided in nine Sets of processes. Every Endeavor shall start with Formalizing the project, go through at least Studying the backgrounds and Creating the deliverables, as well as end from the Managing the product activities.

Formalizing the project

For the purposes of this very wikipage, project formalization refers to the set of efforts that is undertaken to the extent necessary to start researching the backgrounds for envisioning of Project deliverables and their production. This formalization aims to setup the stage for Studying the backgrounds activities.
The formalization shall produce a project charter, which is a document that (a) formalizes a project out of undocumented change making or development and (b) authorizes the project administration. The charter contains CNMCyber Customer's business requirements or those product and/or project requirements of CNMCyber Customer that are not negotiable. These requirements shall address some business need; the terms business requirement and business need are synonims and often used interchangeably. At CNMCyber, they may be stated in one or more of the following:
  • Business case. A description of CNMCyber Customer's vision for what and/or how the project shall accomplish. The case may or may not state success criteria or those key performance indicators (PKIs) that would or would not constitute the project's success. Any successful project shall satisfy specific business needs. Generally speaking, the business case constitutes why the project exists.
  • Statement of work (SOW). A document that states hard requirements related to product and project scope, budget, as well as schedule. The statement lists "hard" deliverables and key factors that affect the project work. The statement may or may not indicate project tools, policies, regulatory and governance terms. The budget part of the statement may or may not describe milestones. The schedule part of the statement may or may not describe funds available, work authorization process, and/or constraints to the funds' availability. The statement is often employed as a part of a request for proposal (RFP).
On a slang, non-negotiable requirements are called "hard requirements". The charter contains all of the hard requirements that come from CNMCyber Customer. However, some of hard requirements derive from the laws, availability of workforce, and other environmental factors. They shall be added to a requirements traceability matrix (RTM) during the Studying the backgrounds activities.
To coordinate the project formalization, the responsible Coord:
  1. Collects data related to the business requirements from CNMCyber Customer.
  2. Analyses the collected data related to business needs while organizing that data on CNM Wiki.
  3. Drafts a project charter.
  4. Makes sure that the statement of work (SOW) in the drafted project charter addresses the business need and supports the business case.
  5. Submits the drafted project charter for CNMCyber Customer's approval.
  6. Publishes the project charter, after its approval, on CNM Wiki.
  7. Requests (a) assistance of the Administrators when additional resources are needed and/or (b) changes to the project charter when new data from existing and/or new sources of data prompt so.
  8. Reports on progress of the project formalization using the CNMCyber Usable wikipage.
  9. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
The project formalization starts after the business need is identified and ends when the project charter is completed.

Studying the backgrounds

For the purposes of this very wikipage, endeavor studies refer to the set of efforts that is undertaken to the extent necessary to start envisioning, planning and managing for the project deliverables, their production and management. These studies aim to setup the stage for Specifying the deliverables, Planning the project, and Managing the product activities.
Endeavor studies shall produce data needed for (a) envisioning of the product, (b) planning its production, and (c) managing the produced product. At CNMCyber, the project studies shall produce the following outputs:
  • Asset register, which is a database of assets that can be used in the project. Particularly, those assets include non-human sources of data that are useful for production of project deliverables.
  • Competency register, which is a database of those competencies that can be valuable to Cyber efforts and their owners, potential and current Contractors and members of CNMCyber Team.
  • Product user group at CNMCyber.com, which is a space for project stakeholders to receive project updates and contribute their questions and comments. The group shall be open 24/7 for asynchronous activities; a functioning group shall also meet simultaneously via video-conference on a weekly basis. The groups of COTS software users tend to be titled in the "CNM/Opplet COTS-name Users" format.
  • Product pages at CNM Wiki, which are wikipages on which the product is being developed. The pages that represent COTS software tend to be titled in the "CNM/Opplet COTS-name" format. They belong to the "CNMCyber products" category.
  • Endeavor pages at CNM Wiki, which are wikipages on which the endeavor is being developed. The pages that represent endeavors on COTS software tend to be titled in the "COTS-name for CNMCyber/Cloud/Opplet/Farms" format. They belong to the "CNMCyber endeavors" category.
  • Requirements traceability matrix, which is a grid that links requirements and their sources.
  • Stakeholder register, which is a database that lists stakeholders of the endeavor. Those stakeholders include the Administrators, CNMCyber Team, those Contractors that work on the endeavor, as well as regulatory bodies that define and/or constrain endeavor's efforts issuing applicable laws and binding requirements. The complete register contains analysis of stakeholders.
To coordinate the project studies, the responsible Coord:
  1. Identifies those available resources that should or can be used in project activities. Human resources include CNMCyber Team. Other resources include those presented in the initial WorldOpp Pipeline courses, on CNM Wiki, existing tools, materials, prototypes, and finished products available at CNMCyber, on the World Wide Web and other sources. For off-the-shelf products, developer websites and professional resources like https://stackoverflow.com/ are usually helpful.
  2. Analyses the identified resources with regard to their nature, usefulness, and potential impact while organizing that data on CNM Wiki.
  3. Selects those resources and those data that may be used in the project activities.
  4. Composes the asset register, competency register, and stakeholder register.
  5. Forms a product user group at CNMCyber.com if this group hasn't formed yet; refreshes the group if it has already formed.
  6. Organizes weekly video conferences, as well as other meetings and activities of the user group. Topics of those events shall address the product, its production when the product is under development, work of its administrators, user feedback and market trends.
  7. Invites everyone who is interested in product's development to the user group.
  8. Offers those experts and specialists who have knowledge, skills, and abilities useful for product specifications or project planning to discuss the deliverable and/or project.
  9. Interviews those experts and specialists who agreed to discuss the deliverable and/or project.
  10. Collects data related to (a) the project deliverables and their production when this deliverable hasn't been deployed yet and (b) product performance when the deliverable has already been deployed, as well as its industry trends.
  11. Makes sure that all of the collected data sources are listed in the asset register, competency register, or stakeholder register.
  12. Publishes the collected data on CNM Wiki. Product data shall be published on the product pages; project data shall be published on the project pages. The published data shall refer to its sources; however, personal data publication requires permissions. From a legal point of view, we cannot publish the confidential information of our contractors, for instance.
  13. Creates a requirements traceability matrix to trace the product and project requirements from the selected sources to perspective project deliverables.
  14. Updates the asset register, competency register, stakeholder register, requirements traceability matrix, as well as project and product pages when ever new data from existing and/or new sources emerge.
  15. Requests assistance of the Administrators when additional resources are needed.
  16. Reports on progress of the project studies using the CNMCyber Usable wikipage.
  17. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
The project studies start after the project charter is approved. Collection of requirements, product envisioning, project planning, production, as well as commissioning and management of a product always reveals new factors and data. That is why the studies end with the project closure.

Specifying the deliverables

The main goal of the product specification activities is to get the deliverable in a state of certainty, which is determined by the presence of a validated product specification. This specification is needed to compare the created deliverables against their requirements. To coordinate the product specification, the responsible Coord:
  1. Collects data related to stakeholder requirements for the project deliverables and product specifications using the asset register, competency register, and stakeholder register. This collection includes communications with stakeholders and review of documents and other assets that are registered.
  2. Examines available prototypes, unfinished and finished products against the collected data.
  3. Analyses the collected product data while organizing that data on CNM Wiki.
  4. Clarifies the collected data based on the examined prototypes and finished products.
  5. Identifies those target audiences who are supposed to use future deliverables.
  6. Creates imaginary personas that would represent each of the identified audience.
  7. Produces stakeholder requirements for each created persona using CNM Wiki.
  8. Composes product specifications based on the produced stakeholder requirements using CNM Wiki.
  9. Traces in a requirements traceability matrix the formalized stakeholder requirements from their sources to perspective project deliverables.
  10. Makes sure that (a) the product specification supports the stakeholder requirements and (b) all the deliverable data is published on CNM Wiki.
  11. Checks product specifications for completeness. This completeness shall be characterized by the presence of conditions for (a) functionality, (b) applicability, and (c) manageability of the deliverables. Conditions for functionality should include measures for product's performance. Conditions for applicability should include measures for product's deployment, testing, diagnostics, accessibility, serviceability, protection, and capacity to recover after disasters; these measures must be documented in product's standing operational procedure (SOP). Conditions for manageability should include measures for product's monitoring, periodic audits and revisions, as well as timely software updates for the COTS software products.
  12. Updates the stakeholder requirements and product specifications when ever new data from existing and/or new sources emerge.
  13. Requests assistance of the Administrators when additional resources are needed.
  14. Reports on progress of the product specification using the CNMCyber Usable wikipage.
  15. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
The product specification opens when CNMCyber Customer approves the project charter and ends with the project closure.

Planning the project

The main goal of the project planning is to decide how the project deliverables will be developed. Those activities shall result in validated acceptance criteria. In other words, planning is getting a description of project activities that allows this development to be certain. To coordinate the project planning, the responsible Coord:
  1. Collects data related to project scope baseline, project schedule baseline, project cost baseline, and acceptance criteria using the asset register, competency register, and stakeholder register. This collection includes communications with stakeholders and review of documents and other assets that are registered.
  2. Examines the existing products that are going to be further developed if they are available.
  3. Analyses the collected project data while organizing that data on CNM Wiki.
  4. Formulates the difference between what actually is and what is needed to be. The existing products are what actually is, while the specified deliverable is what is needed to be. The project activities shall address this identified difference; they represent what needs to be done.
  5. Drafts a project scope baseline, project schedule baseline, project cost baseline, and acceptance criteria, based on the resources recorded in the registers.
  6. Makes sure that the acceptance criteria supports the project scope baseline and project schedule baseline.
  7. Submits the drafted project scope baseline, project schedule baseline, project cost baseline, and acceptance criteria for CNMCyber Customer's confirmation.
  8. Publishes the project scope baseline, project schedule baseline, and acceptance criteria, after their confirmation, on CNM Wiki. To make future negotiations successful, neither the project cost baseline nor other financial data should be available to the general public.
  9. Requests (a) assistance of the Administrators when additional resources are needed and/or (b) changes to the project scope baseline, project schedule baseline, project cost baseline, and/or acceptance criteria when new data from existing and/or new sources of data prompt so.
  10. Reports on progress of the project planning using the CNMCyber Usable wikipage.
  11. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
Similarly to Specifying the deliverables, the project planning opens when CNMCyber Customer approves the project charter and ends with the project closure. However, the project plan not entirely, but depends on product specification, while the specification rarely does. The deliverable to be dictates what needs to be done, not vice versa. Only impossibility of the specified deliverable production can initiate the change to its product specification.

Hiring the contractors

At the Cyber, the main goal of hiring of project contractors is to expand the Coords' expertise and resources in order to accomplish the project. The contractors must be hired to produce anything beyond #What Coords produceWhat Coords produce; however, the contractors can also be hired to produce special Communications, Documents, Meetings, and/or Records.
In order to be hired, though, the prospective contractors need to be sourced first and selected second. Moreover, the sourcing, selecting, and hiring require their own "cycle phases" such as request formalization, background studies, contractor competencies' specification, recruitment plan, as well as this plan execution.
All of those activities shall result in fully-executed Careerprise contractor agreement. To coordinate the hiring of contractors, the responsible Coord:
  1. Evaluates whether third-party contractors are needed and, if they are needed, what Types of contractors should be looked for.
  2. Provides data to CNMCyber Customer for making the decision either to bring external contractors on the board or not to bring. The positive decision assumes CNMCyber Customer's willingness to finance the contractor's work.
  3. Revisits the Studying the backgrounds activities to identify those available resources that should or can be used in sourcing, selecting, and hiring of contractors.
  4. Collects data related to sourcing, selecting, and hiring of contractors that are able and available to satisfy Cyber needs using the asset register, competency register, and stakeholder register. This collection includes communications with stakeholders and review of documents and other assets that are registered.
  5. Analyses the collected sourcing, selecting, and hiring data while organizing that data on CNM Wiki.
  6. Composes solicitation materials including a request for proposal (RFP), which is a solicitation announcement, and the list of its placement options.
  7. Submits the composed materials to the CNMCyber Project Manager for their publication.
  8. Revisits the Studying the backgrounds activities to update a list of potential contractors in the stakeholder register.
  9. Invites the listed contractors to discuss project's deliverables and product specifications, as well as the project including project scope baseline, project schedule baseline, project cost baseline, and acceptance criteria.
  10. Treats the discussions with the contractor candidates as primary sources of data to revisit the Studying the backgrounds activities. Hiring people is a great way to learn about aspects of an endeavor. Conducted interviews shall add to the CNM Wiki documentation. Particularly, that means publishing on CNM Wiki the data related to the deliverables and schedules extracted from the discussions. As a rule, meetings with contractors serve two different purposes: (a) selection of right candidates and (b) learning about the deliverables and/or project. Historically, requirements are refined during the recruitment process. If the requirements cannot be formulated during the recruitment process, they themselves shall become deliverables of an intermediary project.
  11. Assists in selection of the most promising candidates, negotiations, and other processes aimed to source and select contractors.
  12. Makes sure that the contractors are being selected not only because of their ability to speak, write, look well, get in touch on time, respond quickly, and so on, but, primarily, because of their ability to satisfy the Funded demands this contractor is being hired to resolve. Specifically, CNMCyber Customer's:
    1. Approval of acceptance criteria makes possible hiring of developers.
    2. Validation of a standing operating procedure (SOP) makes possible hiring of servicers.
    3. Authorization of paid hours makes possible hiring of on-call specialists.
    If no job vacancy document is available at the moment, the candidates shall be offered to help developing it on a volunteer basis. If the need exists, but all internal and external resources to develop the document are exhausted, the Coord shall initiate a preliminary project to produce that document.
  13. Initiates a preliminary project to document the Funded demands if own efforts of the Coord didn't produce that document.
  14. Drafts a Careerprise contractor agreement while using its blueprint and entering subject matters to negotiate or agree.
  15. Provides the prospective and/or selected contractor with the drafted agreement.
  16. Informs CNMCyber Customer about the readiness of the contract or contract for the full execution. The execution of the contract authorizes the financing of the production of the deliverables by contractors. One of the consultants may be contracted for consultations and/or participation in video conferences.
  17. Requests (a) assistance of the Administrators when additional resources are needed and/or (b) changes to the request for proposal (RFP) when new data from existing and/or new sources of data prompt so.
  18. Reports on new contractor hires using the CNMCyber Usable wikipage.
  19. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
The hiring of contractors opens when CNMCyber Customer approves the Coord's request for the hire. It ends with full execution of the Careerprise contractor agreement.

Working with contractors

The main goal of collaboration with endeavor contractors is to enable the Contractors to deliver rightly right project deliverables or other requested services. To coordinate collaboration with contractors, the responsible Coord:
  1. Serves as an liaison between CNMCyber Customer and contractors, reporting problems that need to be resolved.
  2. Organizes videoconferences or other meetings of parties interested in the project, especially those necessary to resolve problems arising during the project.
  3. Collects data related to the contractor performance.
  4. Analyses the collected data related to contractor performance while organizing that data on CNM Wiki.
  5. Initiates the process of paying contractors for their work. The process shall be described in a special standing operating procedure (SOP). Prior to creating it, this start of the process implies a request to the manager or CNMCyber Customer.
  6. Requests (a) assistance of the Administrators when additional resources are needed and/or (b) changes to the fully-executed Careerprise contractor agreement when new data from existing and/or new sources of data prompt so.
  7. Revisits the Studying the backgrounds activities when new data or new sources of data emerges in order to revisit further the Specifying the deliverables and Planning the project activities.
  8. Presents the progress of collaboration with contractors, plans and possible concerns about that collaboration during CNMCyber This Week meetings.
The collaboration with contractors opens when their Careerprise contractor agreement is fully executed. It ends with the closure of the agreement.

Creating the deliverables

The main goal of deliverable creation activities is to create rightly right deliverables. "Right" means that every deliverable shall be in a state of capability, which is determined by the fact that the deliverable meets all the product specifications that have been approved for this deliverable. "Rightly" means that the aggregate of creation activities match the agreed acceptance criteria.
At the Cyber, Contractors create Project deliverables. To coordinate the deliverable creation, the responsible Coord:
  1. Initiates hiring of development contractors.
  2. Plays roles of the product owner and/or project owner in the absence of other members of CNMCyber Team assigned to those roles. In that case, the Coord decides how, within the framework of the approved requirements, the deliverable and the project should be.
  3. Tests the deliverable and, if necessary, its parts.
  4. Collects data related to the deliverables under development and their production.
  5. Analyses the collected project data while organizing that data on CNM Wiki.
  6. Monitors the development and execution of the project, including compliance with the budget, schedule and scope of work.
  7. Inquiries about changes to the project charter, product specification, project scope baseline, project schedule baseline, project cost baseline, and/or acceptance criteria when new data from existing and/or new sources of data prompt so.
  8. Organizes a closed-from-the-public-view project space on CNM Lab for work on the deliverable in addition to the project wikipage on CNM Wiki.
  9. Invites the hired contractor to the project space.
  10. Reports to CNMCyber Customer on the status of the project, collecting, analyzing and summarizing information and trends.
  11. Treats creation of deliverables as primary source of data to revisit the Studying the backgrounds activities.
  12. Makes sure that the created deliverables (a) represent a complete bundle of products that are listed in the Careerprise contractor agreement and (b) satisfy their acceptance criteria.
  13. Recommends, after the contractor informs about the completion of project work, either (a) acceptance of the deliverables or (b) refusal to accept those deliverables while providing CNMCyber Customer with explanations for that refusal.
  14. Requests assistance of the Administrators when additional resources are needed.
  15. Revisits the Studying the backgrounds activities when new data or new sources of data emerges in order to revisit further the Specifying the deliverables and Planning the project activities.
  16. Reports on progress of the deliverable creation using the CNMCyber Usable wikipage.
  17. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
The deliverable creation opens when CNMCyber Customer authorizes its financing and ends when the deliverables are accepted. To expedite the project, the creation may start before its acceptance criteria have developed.

Commissioning the product

The main goal of the product commissioning is to obtain the product in its state of applicability, which is determined by the fact that the deliverable is not only functional, but can also be sustainably used for the purpose for which it has been created. In simple words, the commissioning is a transfer of the accepted deliverables from the contractor into Cyber operations. To coordinate this commissioning, the responsible Coord:
  1. Clarifies with CNMCyber Project Managers which members of CNMCyber Team will: (a) deploy the newly-deployed product if it hasn't been deployed yet, (b) test the newly-deployed product, (c) restrict access of the development contractors to the product and product's classified documentation, (d) access the classified documentation on CNM Lab, (e) establish new product operations based on its standing operating procedure (SOP), and (f) manage hiring of service contractors.
  2. Initiates (a) deployment of the newly-deployed product if it hasn't been deployed yet, (b) beta testing of the newly-deployed product, (c) restrictions of the development contractors' access to the product and product's classified documentation, (d) new administrator's access to the classified documentation on CNM Lab, (e) establishment of new product operations based on its standing operating procedure (SOP), and (f) hiring of service contractors.
  3. Collects data related to the product commissioning.
  4. Analyses the collected data related to product commissioning while organizing that data on CNM Wiki.
  5. Publishes the documentation received from the contractor on the Cloud resources. Internal, closed to the public, documentation, such as administrator access to installed software, is published on CNM Lab. The documentation that can be open to the public without restrictions is published on CNM Wiki.
  6. Requests assistance of the Administrators when additional resources are needed.
  7. Revisits the Studying the backgrounds activities when new data or new sources of data emerges in order to update the Managing the product activities.
  8. Reports on progress of the product commissioning using the CNMCyber Usable wikipage.
  9. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
The product commissioning opens when the deliverables are accepted and ends when the product is ready to be used in Cyber operations.

Managing the product

Two main goals of product management are (a) to obtain the product in a state of manageability and (b) to keep it in this state. The state is determined by the fact that the product is not only used for the purpose for which it was produced, but also controlled. This management includes both maintenance and improvement of product performance, as well as decisions to end its life or replace. To coordinate the product management, the responsible Coord:
  1. Monitors product usage, administrator performance, user feedback, industry trends, best practices, and situations in those markets that are associated with the product, its alternatives, and components.
  2. Treats the product management monitoring as primary sources of data to revisit the Studying the backgrounds activities.
  3. Collects data related to the product performance and its administration.
  4. Analyses the collected data related to product management while organizing that data on CNM Wiki.
  5. Identifies problems and opportunities to improve the product or replace the product with other solutions.
  6. Inventories the problems and opportunities that have been identified using Cyber's idea management software when it is available; temporarily, CNM Wiki shall be used.
  7. Presents the problems and opportunities identified in the inventory to CNMCyber Customer for making decisions about opening new projects.
  8. Requests assistance of the Administrators when additional resources are needed.
  9. Revisits the Studying the backgrounds activities when new data or new sources of data emerges.
  10. Reports on progress of the product management using the CNMCyber Usable wikipage.
  11. Presents the progress, plans and possible concerns during CNMCyber This Week meetings.
Product management opens when the product is put into service and ends when the product gets retired.

Residents' bootcamp

Main wikipage: CNMCyber Bootcamps
The Bootcamp is designed to introduce the learners to various positions, help to select the promising one, and place the learner as an apprentice into both the job and educational program. In their Practice, the learners work as the Residents.
The Resident is a temporary position, limited by the duration of the Bootcamp. Not everyone is attracted to work on creating something new. Not everyone is able to work in conditions of uncertainty.
  • If the job of the Resident suits the participant, he or she moves towards the business analyst, systems engineer, partner coordinator, event organizer, information structure or solution creator, product or user experience designer, and product, information resources or development manager, and other occupations in projects.
  • If unable or unwilling, the participant is promoted to Contract or Systems Administrator, Usability Analyst, Accountant, Graphic Designer, Operations Engineer, Purchasing, Account Manager, and Procurement Manager and other occupations in operations.
During the Bootcamp, students should be introduced to different professions from a programmer to an accountant. The specialty will be selected based on the results of the Practice, and then it will be necessary to select a curriculum with a partner and organize an internship. We hope to organize the internship ourselves, but it will be difficult to replace educational institutions. Nothing unreal is foreseen, but everything needs to be worked out. Until the third course is ready, the Residents can work on it.

See also

Related lectures