Difference between revisions of "CNMCyber Coordinator"

From CNM Wiki
Jump to: navigation, search
(Deliverables)
 
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.  
+
[[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''.
  
==Work==
 
The ''Coords'' work on [[project]]s, which can be defined as [[enterprise effort]]s undertaken to create 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 [[#Deliverables|Deliverables]] section of this wikipage.
 
  
===Authorized work===
+
==Position==
: Those projects that are fully funded, authorized, and available to the ''Coords'' are published on the [[CNM Cloud Usable]] wikipage.
+
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 work===
+
===Choice of practice===
: 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.
+
: 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.
  
==What Coords do==
+
: 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:
Each project can have the ''Coord'' who is responsible for it. For each project that the ''Coords'' work on, they document the results of research, developments, and approvals. No one, but the ''Coords'', can be responsible for project documentation.
+
:* 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]].
 +
:* 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]].
  
In addition, the ''Coords'' work on (a) [[#Defining the product|Defining the product]], (b) [[#Creating the product|Creating the product]], (c) [[#Commissioning the product|Commissioning the product]], and (d) [[#Managing the product|Managing the product]].
+
: 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.
  
===Defining the product===
+
===How to start===
: The main goal of the product planning and creation activities is to get the product in a [[state of certainty]], which is determined by the presence of a [[production consent]]. In other words, planning is getting a description of the product and its development process in such a way that allows this development to be certain. To achieve this goal, the responsible ''Coord'':
+
: Are you interested in getting started as the ''Coord''? Please follow a step-by-step instruction as follows:
:# '''Identifies''' those available resources that should or can be used in development at no additional cost. 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.
+
:# '''Get''' professional experience as [[CNM Website Developer]], [[CNM Event Organizer]], and [[CNM Cloud Operator]].
:# '''Collects''' data using identified resources. This study includes communicating with stakeholders, reviewing documents, and testing those prototypes and finished products that are available.
+
:# 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>
:# '''Selects''' those resources and those data that will be involved in the development.
+
:# '''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.
:# '''Inventories''' those data, tools, materials, prototypes and factors that have been identified as being or could be involved in the development.
+
:# '''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.
:# '''Describes''' the future product and its possible production, based on the resources identified in the inventory. The description may include (a) [[business requirement]]s, (b) [[prototype]]s, (c) [[stakeholder requirement]]s, as well as drafts for [[product specification]]s, [[project specification]]s, and, possibly, some elements of [[production consent]].
+
:# '''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
:# '''Makes''' sure that the customer of the product needs exactly the product that meets the described [[business requirement]]s.
+
:# '''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''.
:# '''Brings''' [[stakeholder requirement]]s in line with the [[business requirement]]s.
+
:# '''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.
:# '''Formulates''' the difference between what actually is and what is needed. With regards to the product, this identified difference should be addressed by the [[product specification]].
 
:# '''Checks''' [[product specification]]s for completeness. Completeness is characterized by the presence of conditions for (a) functionality, (b) applicability, and (c) manageability of the product. Conditions of applicability should include product 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 product and instructions for recovery in case of accidents.
 
:# '''Evaluates''' whether it is necessary to involve third-party contractors in the product creation and, if necessary, whether their assistance is required to create [[product specification]]s, [[project specification]]s, and [[production consent]] draft.
 
:# '''Provides''' data to the customer for making a decision either to attract contractors or to create a product on its own, as well as to start financing the creation work.
 
:# '''Brings''' requirements and other development documents to completeness.
 
  
: If further creation will be carried out without the involvement of contractors, the customer can authorize its beginning before the completion of the [[production consent]]. In this case, the requirements are finalized taking into account the data obtained during the creation process.
+
: By the way, you can be paid to ask questions about this wikipage when you identify the endeavor behind that page.
  
: If external contractors are required, the ''Coord'' will further:
+
===Occupation===
:# '''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.
+
: [[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''.
:# '''Invites''' contractors to develop and, in parallel, refine the [[product specification]], [[project specification]], and [[production consent]], including the scope of work, schedule and development budget.
 
:# '''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 product of an intermediary project.
 
:# '''Informs''' the customer about the readiness of the contract or contract for the conclusion. The conclusion of the contract authorizes the financing of the creation of the product by contractors. One of the consultants may be contracted for consultations and/or participation in video conferences.
 
  
:The planning of both the product itself and the process of its creation opens before the start of work on the direct creation of the product and, even if contractors are involved, it is periodically resumed after the start, since the creation always reveals new factors and requirements.
+
: Other close occupations include Project Management Specialists, Computer and Information Systems Managers,  
  
===Creating the product ===
+
Administrative Services Managers
: The main goal of product development activities is to obtain a product in a [[state of capability]], which is determined by the fact that the product meets all the [[product specification]]s that have been approved for it. In addition to the product itself, the process of its creation must also satisfy the [[project specification]]s. To achieve this goal, the responsible ''Coord'':
+
Chief Executives
:# '''Oversees''' the creation 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 product and the project should be.
+
Executive Secretaries and Executive Administrative Assistants
:# '''Tests''' the product and, if necessary, its parts.
+
Secretaries and Administrative Assistants
:# '''Oversees''' the development and execution of the project, including monitoring compliance with the budget, schedule and scope of work.
+
Office and Administrative Support Workers
:# '''Initiates''' changes to the requirements for a product or its creation.
+
Legal Secretaries and Administrative Assistants
:# '''Starts''' a project closed from the public on [[CNM Git]] for work on the product in addition to the project wiki page on [[CNM Wiki]].
+
Human Resources Manager
:# '''Reports''' to the customer on the status of the project, collecting, analyzing and summarizing information and trends.
+
General and Operations Managers
:# '''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 creation of the product.
 
:# '''Makes''' changes to the documentation based on these developments.
 
  
: If third-party contractors are involved in the development, the ''Coord'' will also:
+
===Tools===
:# '''Serves''' as an liaison between the customer and contractors, reporting problems that need to be resolved.
+
:* [[Inplz app]]s
:# '''Organizes''' videoconferences or other meetings of parties interested in the project, especially those necessary to resolve problems arising during the project.
+
:* [[CNM Wiki]]
:# '''Starts''' the process of paying contractors for their work. Prior to creating organizational procedures, this implies a request to the manager or customer.
 
: The direct creation of a product opens after the decision of the customer to start this creation, as a rule, when [[business requirement|business]] and [[stakeholder requirement]]s are present. [[Product specification|product]] and [[project specification]]s, as well as [[prototype]]s can be refined in parallel with the creation of a viable product. The creation of the product is closed with the acceptance of the product and can be resumed if problems with the viability of the product are found out.
 
  
===Commissioning the product===
+
==What Coords produce==
: The main goal of the product transfer into operation is to obtain the product in a [[state of applicability]], which is determined by the fact that the product is not only functional, but can also be used for the purpose for which it was created. To achieve this goal, the responsible ''Coord'':
+
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''.
:# '''Is responsible''' for restricting the contractor's further access to the product.
 
:# '''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 product from accepted from the contractor to put into operation. This "contribution", in particular, may include (a) clarifying with the customer which of the [[#Personnel|Personnel]] will administer the created product, (b) transferring access to the classified documentation on [[CNM Git]] to administrators, (c) together with administrators, detailing the procedure for transferring the product 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 product and ends with the start of use of the product, usually initially during the [[beta testing]] process.
 
  
===Managing the product===
+
===Communications===
: 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 created, 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, [[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''.
:# '''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 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.
 
  
==Goals of Coords' work==
+
: The ''Coords'' run their communications to make development of [[CNMCyber product]]s possible. These communications include:
The terminal results of the work of the ''Coords'' are the [[#Deliverables|Deliverables]] in various [[#Product states|Product states]] and [[#Development areas|Development areas]]. For the most part, products are developed by contractors on the basis of approved descriptions and finalized by the ''Coors'' and / or other members of the [[#Personnel|Personnel]]. Descriptions of products are produced at [[CNM Wiki]] and include descriptions of ideas for the development of future products.
+
:* '''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.
  
===Deliverables===
+
: 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.
: The aim of ''Cloud's'' developments is to create new products or modify existing products, including:
 
:* '''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 [[CNM Cyber]].
 
:* '''Content''', such as texts, illustrations and multimedia materials that can be used in [[CNM app]]s.
 
:* '''Documents''' are usually part of other products, but some of them represent products in their own right. For example, a standard 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]].
 
:* '''Events''', espesially [[CNM 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.
 
:* '''Information''' resources for attracting potential partners and customers of [[CNM 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.
 
:* '''Positions''', which are documented workplaces of associates included in the organizational structure. This very wikipage is the development of one of the [[CNM Cyber]] positions.
 
:* '''Relationships''' with potential and existing clients such as exhibitors, contractors and partners. Stakeholders are involved in communications through (a) hiring contractors to turn customer-approved descriptions into products, (b) hiring employees for developed positions, (c) participation of potential [[CNM Cyber]] participants in events organized by the project.
 
:* '''Software''' that can be used in the ''Cloud''.
 
:* '''Structure''' known as [[organizational structure]] to organize the work of [[#Personnel|Personnel]]; their rights and duties are determined by positions.
 
  
===Personnel development===
+
===Documents===
:In terms of the development of human resources, the results of the work of the Coordinator can be:
+
: 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]].
В плане развития трудовых ресурсов, результатами работы ''Координатора'' могут быть:
 
:# Recruitment of contractors and new Coordinators by:
 
Рекрутирование подрядчиков и новых ''Координаторов'' путём:
 
:#* Development of ads, own website and other resources.
 
Разработки объявлений, собственного сайта и других ресурсов.
 
:#* Placement of ads on specialized sites, social networks such as Telegram and Instagram, as well as other channels.
 
Размещения объявлений на специализированных сайтах, социальных сетях типа Телеграм и Инстаграм, а также других каналах.
 
:#* Conducting video conferences and other events for interested parties.
 
Проведения видеоконференций и других мероприятий для заинтересованных лиц.
 
:#* Finding partners among commercial, public and government organizations.
 
Нахождения партнёров среди коммерческих, общественных и государственных организаций.
 
:# Development of professional knowledge, skills and abilities of the existing workforce and new recruits.
 
Развитие профессиональных знаний, навыков и умений существующих трудовых ресурсов и новых рекрутов.
 
  
===Development areas===
+
: 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:
: Students in practice are also encouraged to suggest their topics and areas. The developments published on this wiki page are grouped by work on Bskol products in the following areas:
+
:* '''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]].
Учеников на практике также призывают [[#Назовите свои|предложить свои темы и области]]. Опубликованные на этой вики-странице разработки сгруппированы по работам над изделиями Bskol в следующих областях:
+
:* '''Legal drafts''' such as papers drafted to be signed as [[contract]]s.
:* '''[[#Administration of the Bskol project, covering personnel, legal, financial and organizational issues.
+
:* '''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.
Администрация Bskol|Администрация]]''' проекта [[Bskol]], охватывающая кадровые, юридические, финансовые и организационные вопросы.
+
:* '''[[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.
:* '''[[#Bratsko Cloud (hereinafter - Cloud). The most complete description of all technical projects is published on the Working on the Cloud page. Based on the approved technical documentation, the results of the Coordinator'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:
 
Брацко Облако|Брацко Облако]]''' (здесь и далее -- ''Облаком''). Наиболее полное описание всех технических проектов опубликовано на странице [[Работы над Облаком]]. Базируясь на утверждённой технической документации, результатами работы ''Координатора'' могут быть нехватающая система или её часть, программное обеспечение, содержимое системы, потребительская услуга и, вообще, работа того, что не работало. Как информационно-технический комплекс, ''Облако'' состоит из:
 
:*# [[#Farms, including tools for their high availability.
 
Фермы|Ферм]], в том числе инструментов по их [[высокая доступность|высокой доступности]].
 
:*# [[#A covert that serves both user applications called "attachments" and users directly.
 
Оплёт|Оплёта]], который обслуживает как пользовательские приложения называемые "приладами", так и напрямую пользователей.
 
:*# Software (software) Some application developments concern only their software, some - only the content used in the provision of services, some developments combine both.
 
Программного обеспечения (ПО) [[#Прилады|Прилад]]. Некоторые разработки прилад касаются только их ПО, некоторые -- только используемого в оказании услуг содержания, некоторые разработки объединяют и то, и другое.
 
:* '''[[#Servicing end users, potential participants and partners of Bskol.
 
Обслуживание клиентов|Обслуживание]]''' конечных потребителей, потенциальных участников и партнёров Bskol.
 
:* '''[[#Presence of project services and its participants in the labor market and business services market.
 
Присутствие на рынке|Присутствие]]''' услуг проекта и его участников на рынке труда и рынке бизнес-услуг.
 
:* '''[[#Services, including vocational guidance, training and employment with the support of volunteers and Prilad, 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.
 
Некоторые изделия могут относиться к нескольким областям. Например, сессия практического тренинга является услугой, но объявления в её ходе могут иметь целью присутствие на рынке. Прилады могут рассматриваться как программное обеспечение, но дееспособные и наполненные содержимым прилады, прежде всего, являются услугами.
 
  
==Results==
+
: 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.
  
===Additional===
+
: 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.
: Additional Deliverables are Deliverables for which development was not initiated, but which were developed as by-products.
 
Дополнительные результаты -- это те [[#Конечные результаты|Конечные результаты]], ради которых разработка не затевалась, но которые были разработаны в качестве побочных продуктов.
 
  
===Intermediary===
+
===Meetings===
: As a rule, Deliverables include several intermediate results. Making a new accessory, for example, is impossible without documents that describe the requirements, and drawing up requirements is impossible without meeting events.
+
: 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 achieve intermediate results, the Coordinator may follow the same procedure as for the final results.
+
: To support development of [[CNMCyber product]]s, 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.
  
===Target===
+
: 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.
: Target results are those results for which development is undertaken. Usually, we are talking about a complex of the [[#Deliverables|Deliverables]].
 
  
==States and readiness==
+
: 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.
  
===Product states===
+
: 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]].
: The ''Coords'' work to bring the item into one or more of the following states:
 
''Координаторы'' работают над приведением изделия в одно или несколько из следующих состояний:
 
:# '''[[State of acknowledgment]]'''. In this state, the future product exists in the form of a noticed and documented idea.
 
:# '''[[State of certainty]]'''. In this state, the future product exists as a valid [[production consent]].
 
:# '''[[State of capability]]'''. In this state, the product has already been created in accordance with all the requirements that have been approved for it.
 
:# '''[[State of applicability]]'''. in this state, the product is not only functional, but can also be used for the purpose for which it was created.
 
:# '''[[State of manageability]]'''. in this state, the product is not only used for the purpose for which it was created, but also controlled, that is, the product 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===
+
===Records===
:* '''[[Higher requirements - a description of the needs for which the development of the product is undertaken.
+
: 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.
Высшие требования]]''' -- описание тех потребностей, для удовлетворения которых предпринимается разработка продукта.
 
:* '''[[Prototype (from the Greek "prōtos" meaning "first", "original" and "typos" meaning "imprint", "imprint", pattern) is an instance, sample or model, following the example of which others are made or finalized. Prototypes of products are often built to test a perception, concept, or process.Prototypes can either be selected from existing products or produced during a project.
 
Прототип]]''' (от греческих "prōtos" в значении "первый", "изначальный" и "typos" в значении "оттиск", "слепок", узор") -- экземпляр, образец или модель по примеру которой изготавливаются или дорабатываются другие. В разработке изделий прототипы часто строятся для проверки восприятия, концепции или процесса. Прототипы могут как подбираться из существующих изделий, так и изготавливаться в ходе проекта.
 
:* '''[[User requirements - a description of the future product made on behalf of various types of its users.
 
Пользовательские требования]]''' -- описание будущего изделия сделанное от лица различных типов его пользователей.
 
:* '''[[Working requirements - a description of the conditions for the manufacture of the future product.
 
Рабочие требования]]''' -- описание условий изготовления будущего изделия.
 
:* '''[[Technical requirements - a set of tasks for product manufacturers regarding its required characteristics.
 
Технические требования]]''' -- комплекс заданий изготовителям изделия касаемых его требуемых характеристик.
 
:* '''[[Manufacturing agreement - terms of manufacture approved by both the customer and the manufacturer, including the scope, schedule and budget of the work. The agreement can take two forms:
 
Соглашение об изготовлении]]''' -- утверждённые как заказчиком, так и изготовителем условия изготовления, включающие объём, график и бюджет работ. ''Договорённость'' может принимать две формы:
 
  
A contract is a legally binding agreement between a customer and a contractor for the manufacture of a product.
+
: 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:
Fabrication Work Instruction -- a detailed description of the procedures required for manufacturing.
+
:* '''Archived files''' such as videos, audios, textual files, as well as coded and programmed scripts.
<ol type="1"><li>[[Контракт]] -- юридически-обязывающая договорённость между заказчиком и подрядчиком на изготовление изделия.</li><li>[[Рабочая инструкция по изготовлению]] -- подробное описание процедур необходимых для изготовления.</li></ol>
+
:* '''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]].
  
A complete agreement must include product acceptance criteria as well as:
+
: Within the [[#Project results|Project results]], the records represent [[project output]]s by their definition.
or schedule and budget,
 
or the principles by which the terms and costs of work will be determined.
 
Полноценное соглашение должно включать критерии приемлемости изделия, а также:<ol type="a"><li>либо график и бюджет,</li><li>либо те принципы, по которым будут определяться сроки и стоимости работ.</li></ol>
 
  
Product acceptance criteria should reflect the scope of work.
+
==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]].
  
===Readiness levels===
+
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]].
: For product states, Coordinators work towards one of the following readiness levels:
 
Для '''[[#Состояния изделий|состояний изделий]]''', ''Координаторы'' работают над одним из следующих уровней готовности:
 
:#''[[Development, when work on the corresponding state has been started, but the state itself has not yet been reached.
 
Уровень разработки|Разработка]]'', когда работа над соответствующим состоянием начата, но само состояние ещё не достигнуто.
 
:#''[[Operations when the state has already been achieved, but requires periodic revision.
 
Уровень операций|Операции]]'', когда состояние уже достигнуто, но требует периодической ревизии.
 
  
:[[The state of certainty is characterized by the presence of several carriers of certainty. Each of the carriers has several levels of readiness:
+
===Authorized endeavors===
Состояние определённости]] характеризуется наличием нескольких [[#Носители определённости|носителей определённости]]. Каждый из носителей имеет несколько уровней готовности:
+
: Those [[#Endeavors|Endeavors]] that are authorized to practice with are listed on the [[CNMCyber Usable]] wikipage.
:#''[[In development, when work on a specific carrier has begun, but it has not yet been proposed for approval.
 
Требование в разработке|В разработке]]'', когда работа над конкретным носителем начата, но он ещё пока не предложен на согласование.
 
:#''[[Under negotiation, when a specific medium is proposed for approval but has not yet been agreed upon.
 
Требование на согласовании|На согласовании]]'', когда конкретный носитель предложен на согласование, но пока ещё не согласован.
 
:#''[[Agreed when the media is agreed. Coordination of all media, except for the Manufacturing Agreement, is carried out by the customer. The contract is negotiated by the contractor. The working instruction for manufacturing becomes operational after running in similar developments.
 
Требование согласовано|Согласовано]]'', когда носитель согласован. Согласование всех носителей, кроме [[Соглашение об изготовлении|Соглашения об изготовлении]], осуществляет заказчик. Согласование [[контракта]] осуществляет подрядчик. [[Рабочая инструкция по изготовлению]] становится рабочей после обкатки в аналогичных разработках.
 
  
==Project factors==
+
===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]].
  
===Administrators in CNM Cyber===
+
===Projects vs operations===
: For the purposes of this wiki page, administration is defined as the management of something and someone. In Bskol, several types of administrators can be distinguished:
+
: The ''Coords'' work and/or facilitate someone else's work on endeavors, which are either:
Для целей этой вики-страницы, администрирование определено как управление чем-либо и кем-либо. В Bskol, можно различить несколько типов администраторов:
+
:* '''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.
:* '''Bskol administrators are those Personnel employees who manage Bskol's development, operations, and product groups. Bskol administrators can be described as super-administrators of Bskol products. In fact, the Bskol administrator is the head and everyone who is assigned to him or her to administer a particular group of developments, operations and products.
+
:* '''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.
Администраторы Bskol''' -- это те сотрудники [[#Personnel|Personnel]], которые управляют группами разработок, операций и изделий Bskol. Администраторов Bskol можно описать как супер-администраторов изделий Bskol. Фактически, администратор Bskol -- это руководитель и все, кто им или ей назначены администрировать ту или иную группу разработок, операций и изделий.
 
:* '''Product administrators are those Personnel employees to whom Bskol administrators have transferred a particular product to control after it has been manufactured. During its creation, the products are administered by the Coordinators. The highest administrator of each product is at least one of the Bskol administrators.
 
Администраторы изделий''' -- те сотрудники [[#Personnel|Personnel]], которым ''администраторы Bskol'' передали в управление то или иное изделие после его изготовления. Во время его создания администрирование изделий ведут ''Координаторы''. Наивысшим администратором каждого изделия является как минимум один из администраторов Bskol.
 
:* '''Attachment administrators are those Personnel employees who are given roles above user roles in attachments. For example, the Edit administrator can protect pages from editing by non-admins. The highest roles in attachments are held by System Administrators; they manage the appointment of administrators in the attachments.
 
Администраторы прилад''' -- те сотрудники [[#Personnel|Personnel]], которым в приладах даны роли выше пользовательских. Например, администратор Правки может защищать страницы от редактирования неадминистраторами. Самыми высокими ролями в приладах владеют [[Сисадмин Bskol|Системными администраторами]]; они и управляют назначением администраторов в приладах.
 
:* '''[[System Administrators is a dedicated position intended for those employees who administer the technological systems of Farms, Olet and Appliance software. The highest administrator of each attachment is at least one of the system administrators, so the latter can be described as super attachment administrators.
 
Сисадмин Bskol|Системныe администраторы]]''' -- это выделенная должность, предназначенная для тех сотрудников, которые администрируют технологические системы Ферм, Оплёта и ПО прилад. Наивысшим администратором каждой прилады является как минимум один из системных администраторов, потому последних можно описать как супер-администраторов прилад.
 
  
===CNM Cyber Customer===
+
: 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.
: The customer provides requirements for future products and pays project budgets. In simple words, the customer orders products and pays for their manufacture. The work of the Coordinator is paid insofar as it is part of the development of the product. The Customer implies that the Coordinator works out projects in accordance with the instructions set out on this wiki page. Out of the goodness of heart and for professional training purposes, the client may do the work of the Coordinator temporarily as long as the client believes that the Coordinator will someday be able to work independently.
 
Заказчик предоставляет требования к будущим изделиям и оплачивает бюджеты проектов. Простыми словами, заказчик заказывает изделия и платит за их изготовление. Работа ''Координатора'' оплачивается постольку, поскольку она является частью разработки изделия. Заказчик подразумевает, что ''Координатор'' отрабaтывает проекты руководствуясь инструкциями изложенными на данной вики-странице. По доброте душевной и в целях профессиональной подготовки, заказчик может делать работу ''Координатора'' временно до той поры, пока заказчик верит в то, что ''Координатор'' когда-то сможет работать самостоятельно.
 
  
===Personnel===
+
===Sets of processes===
:# ''Coordinators contribute to the implementation of projects by acting in accordance with the Development Order.
+
: 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]].
Координаторы'' способствуют реализации проектов действуя согласно [[#Порядок разработок|Порядку разработок]].
 
:# '''[[System administrators ensure the stability of the Cloud's operations and advise on technological developments.
 
Сисадмин Bskol|Системныe администраторы]]''' обеспечивают стабильность операций ''Облака'' и консультируют по технологическим разработкам.
 
:# '''[[Recruiters ensure that the recruiting process is in place, there are candidates for Coordinators and, with the approval of the customer, for other full-time positions in the recruiting "pipeline", and also advise on those developments that relate to recruiting. In their projects, the Coordinators also play the role of recruiters and take over the hiring of contractors. Unlike recruiters, Coordinators discuss requirements and other project documents with candidates. Coordinators turn to recruiters in cases where their own competencies or resources are not enough to attract contractors.
 
Рекрутер Bskol|Рекрутеры]]''' обеспечивают наличие рекрутингового процесса, наличие кандидатов в ''Координаторы'' и, при наличии одобрения заказчика, на другие штатные должности в рекрутинговом "трубопроводе", а также консультируют по тем разработкам, которые касаются рекрутинга. В своих проектах, ''Координаторы'' также играют роли рекрутеров и берут на себя найм подрядчиков. В отличие от рекрутеров, ''Координаторы'' обсуждают с кандидатами требования и другие документы проектов. К рекрутерам ''Координаторы'' обращаются в тех случаях, когда собственных компетенций или ресурсов для привлечения подрядчиков не достаточно.
 
:# '''The 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 leader can be called a "super-coordinator". If the coordinator works on one project, which he himself chooses, the head is responsible for the entire group of developments and operations, including finance, personnel, administration of the same coordinators, and so on. At the moment, the head is replaced by the 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.
 
Хотя ''подрядчики'' формально не входят в персонал проекта, они являются важной составляющей разработок проекта.
 
  
===Timing===
+
: 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.
: ''The coordinator works on one project, usually up to three and, in exceptional cases, up to five weeks.
 
Координатор'' работает над одним проектом обычно до трёх и, в исключительных случаях, до пяти недель.
 
:# In the first week, he or she is introduced to the project. At the end of the familiarization, the Coordinator should be able to explain what is described on the relevant wiki pages and be ready to discuss with the customer of the zero run.
 
В первую неделю он или она знакомится с проектом. По окончанию ознакомления ''Координатор'' должен быть способен объяснить то, что описано на соответствующих проекту вики-страницах, и быть готовым к обсуждению с заказчиком нулевого прогона.
 
:# From the second week to the penultimate week, he or she runs the product following the Design Order.
 
Начиная со второй недели и заканчивая предпоследней, он или она ведёт прогон изделия, следуя [[#Порядок разработок|Порядку разработок]].
 
:# In the final week, he or she completes the project, documenting his or her run and the data that was uncovered during that run.
 
В последнюю неделю он или она завершает работу с проектом, документируя свой прогон и те данные, которые вскрылись в ходе этого прогона
 
: 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 Coordinators, there are no restrictions.
 
Проекты могут накладываться друг на друга. Например, последняя неделя работы над одним проектом может быть первой неделей работы над другим проектом. Для старших ''Координаторов'', ограничений нет.
 
  
==Factors for hiring contractors==
+
===Why endeavors===
===How not to hire===
+
: 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.  
: 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===
+
: 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.
: 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 product 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===
+
==What Coords do==
: 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]].
+
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.
  
===Applications for contractors===
+
===Formalizing the project===
: 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.
+
: 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.
  
==Engagement of Coords==
+
: 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:
 +
:* [[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.
 +
:* [[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]]).
  
Не существует некоего простого индикатора, по которому можно было бы судить, сможет ли человек стать профессиональным ''Координатором'' и, если сможет, то привлекёт его или её такая работа. Потому для участия в проекте [[Bskol]] [[#Поиск кандидатов|приглашаются все желающие]]; каждому из них предлагается [[Подготовка Координаторов|полная подготовка]] и возможность попробовать себя в таком качестве.
+
: 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.
  
===Search for Coords===
+
: To coordinate the project formalization, the responsible ''Coord'':
: Поиск кандидатов осуществляется в соответствии с [[Поиск участников Bskol|Поиском участников Bskol]]. Из всех публиковавшихся, наиболее полное объявление размещено на вики-странице [[Людям с улицы]].
+
:# '''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.
  
===Training of Coords===
+
: The project formalization starts after the [[business need]] is identified and ends when the [[project charter]] is completed.
: Для теоретической подготовки ''Координаторов'', созданы 3 курса -- [[Брацка Вводка]], [[Брацки Техобзор]] и [[Выбор Профессии]]. Практика на последнем из трёх курсов призвана закрепить теоретические знания, а также выявить способность и желание кандидата к работе на проектах.
 
  
===Following positions===
+
===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 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.
:* Если работа ''Координатора'' подходит участнику, он или она двигаются в сторону бизнес-аналитика, инженера систем, координатора работы с партнёрами, организатора мероприятий, создателя информационной структуры или решений, разработчика изделий или удобства пользователя, а также руководителя изделий, информационных ресурсов или разработок и других профессий в проектах.
 
:* В случае неспособности или отсутствия желания, участник продвигается до администратора контрактов или систем, аналитика удобства пользования, бухгалтера, графического дизайнера, инженера-эксплуатационщика, закупщика, специалиста по работе с заказчиками, а также руководителя комплектации и других профессий в операциях.
 
  
: В ходе третьего курса ученики должны быть представлены разным профессиям от программиста до бухгалтера. Специальность будет выбираться по итогам практики и далее надо будет подбирать учебную программу с партнёром и организовывать стажировку. Стажировку организовать мы надеемся сами, а вот учебные заведения подменить будет сложно. Не предвидится ничего не реального, но всё требует разработки. Пока третий курс не готов, ''Координаторы'' могут работать над ним в рамках [[Работы над Bskol|Работ над Bskol]].
+
: 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|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.
  
==Areas of operations==
+
: To coordinate the project studies, the responsible ''Coord'':
 +
:# '''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.
  
===Documenting===
+
: 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 ''Team'' needs help with two types of documentation:
 
:#Organizational documentation for the [[CNM Cyber Team]]. This type shall include:
 
:#*Minutes for meetings of the [[CNM Technology Board]].
 
:#*Processes and procedures developed for and used by the [[CNM Cyber Team]].
 
:#Technical documentation for:
 
:#*[[CNM Cyber]].
 
:#*[[CNM Cloud Next]], the compute server that the ''Team'' uses for learning and testing, and other technology.
 
:All the types of documentation shall be maintained at the [[CNM Wiki]], so any ''Team's'' stakeholder, and a volunteer especially, be able to find needed information.
 
  
===Meeting organizing===
+
===Specifying the deliverables===
:The ''Team'' needs help with organizing of two types of meetings:
+
: 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'':
:#Meetings of the [[CNM Technology Board]], which can be either open or close to the general public.
+
:# '''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.
:#Hiring events for the [[CNM Cyber Taskforce]].
+
:# '''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.
  
:Those meetings that are open to the general public can be organized using partner [[meetup group]]s such as [[CNM Cyber Meetup]].
+
:The product specification opens when [[CNMCyber Customer]] approves the [[project charter]] and ends with the project closure.
  
===Owning the role===
+
===Planning the project===
:The ''Team'' needs help with further development of the ''Coord's'' role. This includes both:
+
: 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'':
:#Creating and editing general instructions, policies, and/or recommendations for the ''Coords''.
+
:# '''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.
:#Contributing to and grooming of the backlog of the ''Coord's'' tasks.
+
:# '''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.
  
===Partnership building===
+
: 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 ''Team'' needs help with sourcing, selecting, and onboarding partners. Historically, the team partnered with two Microsoft stores, in Pentagon City Mall and Tysons Corner Center, several employers, training providers, governmental, and non-profit organizations.
 
  
===Personnel managing===
+
===Hiring the contractors===
:The ''Team'' needs help with volunteer time tracking, as well as helping volunteers to develop their personal plans.
+
: 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]].
  
===Project support===
+
: 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.
:The ''Team'' needs help with supporting its projects such as [[CNM Registration Project]].
 
  
===Public relations administering===
+
: All of those activities shall result in fully-executed [[Careerprise contractor agreement]]. To coordinate the hiring of contractors, the responsible ''Coord'':
:The ''Team'' needs help with drafting newsletters to patrons of [[Career Network Ministry|CNM]] similar to [[Friends Of CNM newsletter]]s.
+
:# '''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.
  
===Testing===
+
: 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]].
:The ''Team'' needs help with user experience testing of its materials and services. The results of this testing shall be well-documented using:
 
:*Discussion pages when [[CNM Wiki]] are tested.
 
:*Emails when anything but [[CNM Wiki]] is tested.
 
  
===Training facilitating===
+
===Working with contractors===
:The ''Team'' needs help with facilitating of three types of training:
+
: 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'':
:#Onboarding training for new volunteers.
 
:#Technology hand-on-training for [[Career Network Ministry|CNM]] patrons who would like to explore [[CNM Cyber]].
 
:#Mentor-[[protégé]] program for some ''Team'' recruits.
 
  
===Volunteer recruiting===
+
:# '''Serves''' as an liaison between [[CNMCyber Customer]] and contractors, reporting problems that need to be resolved.
:The ''Team'' needs help with sourcing and onboarding of new volunteers.
+
:# '''Organizes''' videoconferences or other meetings of parties interested in the project, especially those necessary to resolve problems arising during the project.
 +
:# '''Collects''' data related to the contractor performance.
 +
:# '''Analyses''' the collected data related to contractor performance while organizing that data on [[CNM Wiki]].
 +
:# '''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]].
 +
:# '''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.
 +
:# '''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.
 +
:# '''Presents''' the progress of collaboration with contractors, plans and possible concerns about that collaboration during [[CNMCyber This Week]] meetings.
  
==Sourcing==
+
: The collaboration with contractors opens when their [[Careerprise contractor agreement]] is fully executed. It ends with the closure of the agreement.
Sourcing of potential candidates is an ongoing endeavor, which cannot be limited to the following channels and tools.
 
  
===Channels===
+
===Creating the deliverables===
:The potential candidates may be sourced through various channels such as:
+
: 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]].
:#[[CNM Page]].
 
:#CNM meetings organized in Vienna, VA on Tuesday evenings.
 
:#Partner [[meetup group]]s such as [[CNM Cyber Meetup]] and other partners.
 
:#Newsletters to patrons of [[Career Network Ministry|CNM]] similar to [[Friends Of CNM newsletter]]s.
 
:#Personal networks of the ''Coords''.
 
  
===Handout===
+
: At the ''Cyber'', [[#Contractors|Contractors]] create [[#Project deliverables|Project deliverables]]. To coordinate the deliverable creation, the responsible ''Coord'':
:Handouts with the following text are periodically distributed at [[CNM]] meetings on Tuesday evenings:<blockquote><p>Discover your career, build your credentials, and land your job in the IT field with CNM Cyber</p><p>'''What''': The CNM Cyber Services team seeks its Cyber Project Coordinator.</p><p>'''What help is sought''': An incumbent will coordinate various aspects of the project as required including meetings, announcements, introducing new team members, and documentation of CNM Technology Board Decisions.</p><p>'''Where and when''': The bulk of the job can be done remotely, so this position can be virtual. The schedule can be flexible too. The time commitments start from 2 hours a week.</p><p>'''Who should consider''':</p><p>Anyone who is motivated to learn Information Technology in order to obtain real IT skills and experience that can be put on the resume and used as a leverage for a new position in the information technology field.</p><p>This might be someone thinking of transitioning to IT or increasing their IT skills/knowledge that have been working in IT or someone interested in working in the roles that interface the business with IT such as a business analyst, project manager, product owner, etc.</p><p>No prior tech training is required in order to get started; vice versa, this opportunity could be considered as hands-on training. We need people with any type of skill set, but being motivated to learn new, open systems technology, is what we need the most. We can provide technical direction to anyone that is motivated.</p><p>'''How to join''': If you are interested (or know of someone who may be interested or looking for a way to become more involved), please consider one or both options:<ol><li>Physically, the team organizes recruiting events usually in Vienna, VA on Tuesday evenings. You are welcome to check the tentative schedule at https://www.meetup.com/TechDC/events/calendar in order to RSVP.</li><li>Virtual meetings may be scheduled upon your request -- please email your inquiry to Michael Confoy or Gary "Igor" Ihar at cnmdigitalservices@gmail.com</ol></p><p>'''About CNM Cyber Services''': This team of the Career Network Ministry (CNM) intends to provide CNM with a bundle of online and onsite services collectively called CNM Cyber, which may include websites and video sharing resources, as well as customer relationship, project, learning, and enterprise management systems.</p>
+
:# '''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.
  
==Onboarding==
+
: 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 promising ''Coords'' shall take three or four steps in order to onboard:
 
:#Get graduated from the [[CNM Cyber Orientation|CNM Cyber '''Orientation''']].
 
:#If they are not familiar with project administration, get graduated from the [[CNM DT Placement|CNM DT '''Placement''']].
 
:#If they are familiar with project administration or when they are, perform activities described in the [[#Areas of operations|Areas of '''operations''']].
 
:#Recruit another ''Coord'' in order to get graduated from the onboarding.
 
:#
 
  
===Orientation===
+
===Commissioning the product===
:''Main wikipage: [[CNM Cyber Orientation]]''
+
: 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'':
 +
:# '''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.
 +
:# '''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.
 +
:# '''Collects''' data related to the product commissioning.
 +
:# '''Analyses''' the collected data related to product commissioning while organizing that data on [[CNM Wiki]].
 +
:# '''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 [[CNM Cyber Orientation]] is designed to introduce promising ''Coords'' to the [[Career Network Ministry]], the ''Team'', [[CNM Cyber]], and [[CNM Cloud]].
+
: The product commissioning opens when the deliverables are accepted and ends when the product is ready to be used in ''Cyber'' operations.
  
===Placement===
+
===Managing the product===
:''Main wikipage: [[CNM DT Placement]]''
+
: 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'':
 
+
:# '''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.
:The [[CNM DT Placement]] that shall cover product ownership and [[project management]].
+
:# '''Treats''' the product management monitoring as primary sources of data to revisit the [[#Studying the backgrounds|Studying the backgrounds]] activities.
 
+
:# '''Collects''' data related to the product performance and its administration.
===Backlog===
+
:# '''Analyses''' the collected data related to product management while organizing that data on [[CNM Wiki]].
 +
:# '''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.
 +
:# '''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.
 +
:# '''Revisits''' the [[#Studying the backgrounds|Studying the backgrounds]] activities when new data or new sources of data emerges.
 +
:# '''Reports''' on progress of the product management using the [[CNMCyber Usable]] wikipage.
 +
:# '''Presents''' the progress, plans and possible concerns during [[CNMCyber This Week]] meetings.
  
===Graduation===
+
: Product management opens when the product is put into service and ends when the product gets retired.
  
===Further ideas to consider===
+
==Residents' bootcamp==
:*Orientation shall included one on one meeting with the project leads
+
: ''Main wikipage: [[CNMCyber Bootcamps]]''
:*One online welcome meeting and with Senior ''Coord''
 
:*Participation at/in one of the bi weekly digital meeting via webcast and/or any other virtual meeting platform
 
  
A [[WorldOpp fellow]] is an [[apprentice]] who is both:
+
: 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''.  
#'''Employed''' by [[Educaship Alliance LLC]] particularly in order to design, develop, and deliver [[CNM Cyber]]; and
 
#'''Matriculated''' into either [[WorldOpp Bootcamp]] or post-bootcamp programs such as [[accounting]], [[entrepreneurship]], [[information technology]], and [[project management]] of [[Bracka School]].
 
  
The [[CITPMA cirriculum]] is designed to prepare [[CITPMA|certified informational technology project management associate]]s ([[CITPMA]]s).  
+
: 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.
The curriculum consists of six modules: (1) [[CNM English Essentials]], (2) [[WorldOpp Bootcamp]], (3) [[CNM Tech Essentials]], (4) [[CNM Data Essentials]], and (5) [[CNM DevOps Essentials]].
+
:* 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.
  
==History==
+
: 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==
 
==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