CNMCyber Coordinator

Any CNM Cyber Project Coordinator (hereinafter, the Coord) is the learner matriculated into the WorldOpp Pipeline program who is undergoing initial practical training. This training is a part of the CNM Cyber Placement stage. CNM Cyber (hereinafter, the Cyber) is a collection of services that include (a) information technology called CNM Cloud (hereafter, the Cloud), as well as (b) apprenticeships and internships that are organized at the Cloud.

At the Occupational Information Network, the closest occupation is Information Technology Project Manager. The Certified Information Technology Project Management Associate (CITPMA) credential is awarded to the successful Coords.

Work

The Coords work on projects, which can be defined as enterprise efforts 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 processes. The deliverables of the projects that the Coords coordinate are described in the Deliverables section of this wikipage.

Authorized work

Those projects that are fully funded, authorized, and available to the Coords are published on the CNM Cloud Usable wikipage.

Choice of work

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.

Results

The results of the Coords' work may be classified in four levels:

1. Project scraps, which are intermediate products that either become parts of the Deliverables or have been decommissioned before the end of the project.
2. Project outputs, first of all, its Deliverables.
3. Project outcomes. On the Coord's side, the outcomes are those KSAs that the Coord has obtained during the project coordination. On the other stakeholders' side, the outcomes are something for which the Deliverables have been created.
4. Project impacts, which are consequences of the project, its outputs and outcomes on a society.

What Coords do

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.

In addition, the Coords work on (a) Defining the product, (b) Creating the product, (c) Commissioning the product, and (d) Managing the product.

Defining the product

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:

1. Identifies those available resources that should or can be used in development at no additional cost. Human resources include 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.
2. Collects data using identified resources. This study includes communicating with stakeholders, reviewing documents, and testing those prototypes and finished products that are available.
3. Selects those resources and those data that will be involved in the development.
4. Inventories those data, tools, materials, prototypes and factors that have been identified as being or could be involved in the development.
5. Describes the future product and its possible production, based on the resources identified in the inventory. The description may include (a) business requirements, (b) prototypes, (c) stakeholder requirements, as well as drafts for product specifications, project specifications, and, possibly, some elements of production consent.
6. Makes sure that the Customer of the product needs exactly the product that meets the described business requirements.
7. Brings stakeholder requirements in line with the business requirements.
8. 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.
9. Checks product specifications 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.
10. 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 specifications, project specifications, and production consent draft.
11. 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.
12. 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.

If external contractors are required, the Coord will further:

1. 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.
2. 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.
3. 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.
4. 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.

Creating the product

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 specifications that have been approved for it. In addition to the product itself, the process of its creation must also satisfy the project specifications. To achieve this goal, the responsible Coord:

1. 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.
2. Tests the product and, if necessary, its parts.
3. Oversees the development and execution of the project, including monitoring compliance with the budget, schedule and scope of work.
4. Initiates changes to the requirements for a product or its creation.
5. 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.
6. Reports to the Customer on the status of the project, collecting, analyzing and summarizing information and trends.
7. 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.
8. Makes changes to the documentation based on these developments.

If third-party contractors are involved in the development, the Coord will also:

1. Serves as an liaison between the 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. 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 and stakeholder requirements are present. product and project specifications, as well as prototypes 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

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:

1. Is responsible for restricting the contractor's further access to the product.
2. 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.
3. 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 project manager which of the 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 procedures (SOPs), 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.
4. 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

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:

1. 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.
2. 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.
3. Identifies problems and opportunities to improve the product or replace the product with other solutions.
4. Inventory the problems and opportunities that have been identified.
5. Presents the problems and opportunities identified in the inventory to the Customer for making decisions about opening new projects.
6. 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 terminal results of the work of the Coords are the Deliverables in various Product states and 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. Descriptions of products are produced at CNM Wiki and include descriptions of ideas for the development of future products.

Deliverables

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 apps 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 apps.
• 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 events, 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 clients 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 those descriptions that the Customer approved into the Deliverables, (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; their rights and duties are determined by positions.

Personnel development

In terms of the development of human resources, the results of the work of the Coord can be:

1. Recruitment of contractors and new Coords by:
   • Development of ads, own website and other resources.
   • Placement of ads on specialized sites, social networks such as Telegram, Tik-Tok, and Instagram, as well as other channels.
   • Conducting video conferences and other events for interested parties.
   • Finding partners among commercial, public and government organizations.
2. Development of professional knowledge, skills and abilities of the existing workforce and new recruits.

Development areas

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:

Учеников на практике также призывают предложить свои темы и области. Опубликованные на этой вики-странице разработки сгруппированы по работам над изделиями Bskol в следующих областях:

• [[#Administration of the Bskol project, covering personnel, legal, financial and organizational issues.

Администрация Bskol|Администрация]] проекта Bskol, охватывающая кадровые, юридические, финансовые и организационные вопросы.

• [[#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:

Брацко Облако|Брацко Облако]] (здесь и далее -- Облаком). Наиболее полное описание всех технических проектов опубликовано на странице Работы над Облаком. Базируясь на утверждённой технической документации, результатами работы Координатора могут быть нехватающая система или её часть, программное обеспечение, содержимое системы, потребительская услуга и, вообще, работа того, что не работало. Как информационно-технический комплекс, Облако состоит из:

• 1. [[#Farms, including tools for their high availability.

Фермы|Ферм]], в том числе инструментов по их высокой доступности.

• 1. [[#A covert that serves both user applications called "attachments" and users directly.

Оплёт|Оплёта]], который обслуживает как пользовательские приложения называемые "приладами", так и напрямую пользователей.

• 1. 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.

Некоторые изделия могут относиться к нескольким областям. Например, сессия практического тренинга является услугой, но объявления в её ходе могут иметь целью присутствие на рынке. Прилады могут рассматриваться как программное обеспечение, но дееспособные и наполненные содержимым прилады, прежде всего, являются услугами.

Outputs

Additional

Additional Deliverables are Deliverables for which development was not initiated, but which were developed as by-products.

Дополнительные результаты -- это те Конечные результаты, ради которых разработка не затевалась, но которые были разработаны в качестве побочных продуктов.

Intermediary

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.

Как правило, Конечные результаты включают в себя несколько промежуточных результатов. Изготовление новой прилады, например, невозможно без документов, которые описывают требования, и составление требований невозможно без мероприятий в виде встреч.

To achieve intermediate results, the Coordinator may follow the same procedure as for the final results.

Для достижения промежуточных результатов, Координатор может следовать тому же порядку действий, что и результатов окончательных.

Target

Target results are those results for which development is undertaken. Usually, we are talking about a complex of the Deliverables.

States and readiness

Product states

The Coords work to bring the item into one or more of the following states:

Координаторы работают над приведением изделия в одно или несколько из следующих состояний:

1. State of acknowledgment. In this state, the future product exists in the form of a noticed and documented idea.
2. State of certainty. In this state, the future product exists as a valid production consent.
3. State of capability. In this state, the product has already been created in accordance with all the requirements that have been approved for it.
4. 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.
5. 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

• Business requirements. Description of the needs for which the development of the product is undertaken.
• Prototypes (from the Greek "prōtos" meaning "first", "original" and "typos" meaning "imprint", "imprint", pattern). Instances, samples or models, 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.
• Stakeholder requirements. Description of the future product made on behalf of various types of its stakeholders.
• Product specifications. Set of tasks for product developers regarding its required characteristics.
• Project specifications. Description of the conditions for the creation of the future product.
• Production consent. Terms of production that are approved by both the Customer and the developers, including the scope, schedule and budget of the work. The consent can take two forms:
  1. Contract. A legally binding agreement between the Customer and a contractor for the creation of a product.
  2. Standard operating procedure (SOP). A detailed description of the procedures required for creation of the product.
  A valid consent must include product acceptance criteria as well as either:
  1. schedule and budget.
  2. the principles by which the terms and costs of work will be determined.
  Product acceptance criteria should reflect the scope of work.

Readiness levels

For product states, Coordinators work towards one of the following readiness levels:

Для состояний изделий, Координаторы работают над одним из следующих уровней готовности:

1. [[Development, when work on the corresponding state has been started, but the state itself has not yet been reached.

Уровень разработки|Разработка]], когда работа над соответствующим состоянием начата, но само состояние ещё не достигнуто.

1. [[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:

Состояние определённости]] характеризуется наличием нескольких носителей определённости. Каждый из носителей имеет несколько уровней готовности:

1. [[In development, when work on a specific carrier has begun, but it has not yet been proposed for approval.

Требование в разработке|В разработке]], когда работа над конкретным носителем начата, но он ещё пока не предложен на согласование.

1. [[Under negotiation, when a specific medium is proposed for approval but has not yet been agreed upon.

Требование на согласовании|На согласовании]], когда конкретный носитель предложен на согласование, но пока ещё не согласован.

1. [[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

Administrators in CNM Cyber

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:

Для целей этой вики-страницы, администрирование определено как управление чем-либо и кем-либо. В Bskol, можно различить несколько типов администраторов:

• 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.

Администраторы Bskol -- это те сотрудники 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, которым администраторы 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, которым в приладах даны роли выше пользовательских. Например, администратор Правки может защищать страницы от редактирования неадминистраторами. Самыми высокими ролями в приладах владеют Системными администраторами; они и управляют назначением администраторов в приладах.

• [[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 администраторы]] -- это выделенная должность, предназначенная для тех сотрудников, которые администрируют технологические системы Ферм, Оплёта и ПО прилад. Наивысшим администратором каждой прилады является как минимум один из системных администраторов, потому последних можно описать как супер-администраторов прилад.

Customer

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

1. Coordinators contribute to the implementation of projects by acting in accordance with the Development Order.

Координаторы способствуют реализации проектов действуя согласно Порядку разработок.

1. [[System administrators ensure the stability of the Cloud's operations and advise on technological developments.

Сисадмин Bskol|Системныe администраторы]] обеспечивают стабильность операций Облака и консультируют по технологическим разработкам.

1. [[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|Рекрутеры]] обеспечивают наличие рекрутингового процесса, наличие кандидатов в Координаторы и, при наличии одобрения заказчика, на другие штатные должности в рекрутинговом "трубопроводе", а также консультируют по тем разработкам, которые касаются рекрутинга. В своих проектах, Координаторы также играют роли рекрутеров и берут на себя найм подрядчиков. В отличие от рекрутеров, Координаторы обсуждают с кандидатами требования и другие документы проектов. К рекрутерам Координаторы обращаются в тех случаях, когда собственных компетенций или ресурсов для привлечения подрядчиков не достаточно.

1. 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.

Хотя подрядчики формально не входят в персонал проекта, они являются важной составляющей разработок проекта.

Duration

The Coords work on one project, usually up to three and, in exceptional cases, up to five weeks.

1. In the first week, they shall get familiarized with the project. At the end of the familiarization, the Coord should be able to explain what is described on the relevant wikipages and be ready to discuss its Sprint Zero with the Customer.
2. From the second week to the penultimate week, he or she runs the product following the Design Order.

Начиная со второй недели и заканчивая предпоследней, он или она ведёт прогон изделия, следуя Порядку разработок.

1. 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

How not to hire

Here is an example of how the Coord should not hire contractors:

1. 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.
2. We contact (preferably by phone) to clarify their requirements for payment and promises on terms.
3. We award the contract to the one or the one who offers the best conditions, and let the others know in a polite and respectful way.

How to hire

Here is an example of how the Coord should hire contractors:

1. Know the criteria that determine the state of certainty.
2. Check if the state of certainty has been reached for the product under development.
3. 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 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

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.

Applications for contractors

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.

Engagement of Coords

Не существует некоего простого индикатора, по которому можно было бы судить, сможет ли человек стать профессиональным Координатором и, если сможет, то привлекёт его или её такая работа. Потому для участия в проекте Bskol приглашаются все желающие; каждому из них предлагается полная подготовка и возможность попробовать себя в таком качестве.

Search for Coords

Поиск кандидатов осуществляется в соответствии с Поиском участников Bskol. Из всех публиковавшихся, наиболее полное объявление размещено на вики-странице Людям с улицы.

Training of Coords

Для теоретической подготовки Координаторов, созданы 3 курса -- Брацка Вводка, Брацки Техобзор и Выбор Профессии. Практика на последнем из трёх курсов призвана закрепить теоретические знания, а также выявить способность и желание кандидата к работе на проектах.

Following positions

Координатор -- это временная должность, ограниченная временем прохождения практики. Не каждого человека привлекает работа над созданием чего-то нового. Не каждый и способен работать в условиях неопределённости.

• Если работа Координатора подходит участнику, он или она двигаются в сторону бизнес-аналитика, инженера систем, координатора работы с партнёрами, организатора мероприятий, создателя информационной структуры или решений, разработчика изделий или удобства пользователя, а также руководителя изделий, информационных ресурсов или разработок и других профессий в проектах.
• В случае неспособности или отсутствия желания, участник продвигается до администратора контрактов или систем, аналитика удобства пользования, бухгалтера, графического дизайнера, инженера-эксплуатационщика, закупщика, специалиста по работе с заказчиками, а также руководителя комплектации и других профессий в операциях.

В ходе третьего курса ученики должны быть представлены разным профессиям от программиста до бухгалтера. Специальность будет выбираться по итогам практики и далее надо будет подбирать учебную программу с партнёром и организовывать стажировку. Стажировку организовать мы надеемся сами, а вот учебные заведения подменить будет сложно. Не предвидится ничего не реального, но всё требует разработки. Пока третий курс не готов, Координаторы могут работать над ним в рамках Работ над Bskol.

Areas of operations

Documenting

The Team needs help with two types of documentation:

1. 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.
2. 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

The Team needs help with organizing of two types of meetings:

1. Meetings of the CNM Technology Board, which can be either open or close to the general public.
2. Hiring events for the CNM Cyber Taskforce.

Those meetings that are open to the general public can be organized using partner meetup groups such as CNM Cyber Meetup.

Owning the role

The Team needs help with further development of the Coord's role. This includes both:

1. Creating and editing general instructions, policies, and/or recommendations for the Coords.
2. Contributing to and grooming of the backlog of the Coord's tasks.

Partnership building

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

The Team needs help with volunteer time tracking, as well as helping volunteers to develop their personal plans.

Project support

The Team needs help with supporting its projects such as CNM Registration Project.

Public relations administering

The Team needs help with drafting newsletters to patrons of CNM similar to Friends Of CNM newsletters.

Testing

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

The Team needs help with facilitating of three types of training:

1. Onboarding training for new volunteers.
2. Technology hand-on-training for CNM patrons who would like to explore CNM Cyber.
3. Mentor-protégé program for some Team recruits.

Volunteer recruiting

The Team needs help with sourcing and onboarding of new volunteers.

Sourcing

Sourcing of potential candidates is an ongoing endeavor, which cannot be limited to the following channels and tools.

Channels

The potential candidates may be sourced through various channels such as:

1. CNM Page.
2. CNM meetings organized in Vienna, VA on Tuesday evenings.
3. Partner meetup groups such as CNM Cyber Meetup and other partners.
4. Newsletters to patrons of CNM similar to Friends Of CNM newsletters.
5. Personal networks of the Coords.

Handout

Handouts with the following text are periodically distributed at CNM meetings on Tuesday evenings:

Discover your career, build your credentials, and land your job in the IT field with CNM Cyber

What: The CNM Cyber Services team seeks its Cyber Project Coordinator.

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.

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.

Who should consider:

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.

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.

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.

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:

1. 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.
2. Virtual meetings may be scheduled upon your request -- please email your inquiry to Michael Confoy or Gary "Igor" Ihar at cnmdigitalservices@gmail.com

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.

Onboarding

The promising Coords shall take three or four steps in order to onboard:

1. Get graduated from the CNM Cyber Orientation.
2. If they are not familiar with project administration, get graduated from the CNM DT Placement.
3. If they are familiar with project administration or when they are, perform activities described in the Areas of operations.
4. Recruit another Coord in order to get graduated from the onboarding.

Orientation

Main wikipage: CNM Cyber Orientation

The CNM Cyber Orientation is designed to introduce promising Coords to the Career Network Ministry, the Team, CNM Cyber, and CNM Cloud.

Placement

Main wikipage: CNM DT Placement

The CNM DT Placement that shall cover product ownership and project management.

Further ideas to consider

• Orientation shall included one on one meeting with the project leads
• 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:

1. Employed by Educaship Alliance LLC particularly in order to design, develop, and deliver CNM Cyber; and
2. 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 certified informational technology project management associates (CITPMAs). 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.

See also

Related lectures

• Vacancies at CNM Cyber