CNM Event Organizer

A CNM Event Organizer (formerly known as CNM Cyber event host; hereinafter, the Org) is an incumbent of the second-quarter CNM practice job (hereinafter, the Practice) that The Economic Group has developed to practically introduce CNM learners to event organizing. The Orgs generally practice in organizing CNMCyber events (hereinafter, the Events) or other meetings and conferences, including their preparation, moderation, and post-event activities. The Orgs may develop either:

1. Those events that the Orgs are authorized to produce, or
2. Those requirements that would allow hiring Careerprise contractors to develop those CNMCyber events that the Orgs don't produce directly, on their own.

The Practice belongs to the second quarter of CNMCyber Bootcamp (hereinafter, the Bootcamp). This quarter's lessons are designed to prepare the Orgs to that Practice. The Practice is offered to those Certified Website Development Associates who successfully pass CNM Event Organizing Exam at the end of Bootcamp's second quarter. Successful completion of the event organizing practice qualifies the Residents as Certified Event Organizing Associates.

Position

Choice of practice

The Orgs can choose between:

• Authorized events that CNMCyber Customer authorized for funding. Any Org is welcome to pick any event that he or she would like to practice with.
• Their own events for which they can request CNMCyber Customer's authorization.

By default, the Orgs choose those Events that suit them best. Since timing of some CNMCyber events cannot be moved, the Orgs can pick those events which schedule work for the Orgs.

Effort cycles

To perform effectively, the Org is encouraged to follow the DREPD cycles, particularly:

1. Discover the needs via reviewing the CNMCyber Event Projects wikipage, other events on the market, and communicating with stakeholders.
2. Research event requirements and available resources -- one can call it "researching this very knowledge base, similar events on the market, and, if anything is unclear, asking questions about what should be done and whether requirements to how it should be done are available" in order to prioritize and prepare assumptions for the those parts that are not covered by the requirements.
3. Envision the event including all of its possible details; and, finally;
4. Plan the design of the upcoming meeting.
5. Discover the needs via facilitating the already designed meeting and commissioning the event records in order to restart the cycle.

How to start

Are you interested in getting started as the Org? Please follow a step-by-step instruction as follows:

1. Succeed as a CNM Website Developer.
2. Until the second quarter lessons of the Bootcamp are developed, briefly review the following wikipages:
   1. This very wikipage since it describes your event organizing Practice specifically,
   2. CNMCyber event wikipage since it describes the events you are about to organize,
   3. CNMCyber Event Projects since this wikipage describes those events that are authorized to practice with.
   You can also refresh your knowledge of the CNM practice job wikipage.
3. Ask questions.
4. At the CNMCyber Event Projects wikipage, pick up the event you would like to organize or advance.
5. Present your pick during a CNMCyber This Week event, while stating (a) the event you 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.
6. Wait for CNMCyber Customer's approval or feedback to start your Practice this week or modify your proposal.

Occupations

The Org's Practice touches many occupations. They may include one or more of the following:

• Convention planning such as Meeting, Convention, and Event Planners as long as the Orgs plan the Events.
• Document management such as Document Management Specialists, Information and Record Clerks, Production, Planning, and Expediting Clerks as long as the Orgs manage documents before the Events and their records after the Events.
• Event marketing such as Desktop Publishers, Market Research Analysts and Marketing Specialists, Online Merchants, Public Relations Specialists, Sales Engineers as long as the Orgs communicate the upcoming Events and their records to the public, as well as position them on the market.

Tools

• CNMCyber Meetup group (hereinafter, the Group) as a channel for onsite Events; and/or
• WorldOpp (fb) Facebook page (hereafter, the FB Page) to connect with the Events participants.
• CNM Tube
• CNM Talk
• OBS Studio

What Orgs produce

The Orgs produce two categories of measurable outputs:

1. Internal documents that the Org who practice utilize in the organizing process and that the other Orgs may further utilize in their Practice as prototypes and training materials.
2. Public deliverables that event consumers will obtain as results of the event.

Public deliverables

Outreach materials

• Outreach materials, which are marketing drafts intended to outreach to current and potential clients and participants such as Friends Of CNM newsletters.
• Webpage texts

Internal documents

For the purposes of this very wikipage, internal documents refer to those documents which target audience differs from the general public regardless of whether those documents are available to the public or not. A particular Org who practices with a particular CNMCyber event shall use internal documents for development process; the other Orgs who will further work on other events, may use those documents as prototypes and training materials. As work products of the Orgs, documents shall be published at CNM Wiki.

Event wikipages

For the purposes of this very wikipage, event wikipages refer to those pages of CNM Wiki that describe CNMCyber events as marketables and other products that the Event cycles are intended to create.

At CNM Wiki, any event wikipage belong to one of two groups:

1. Event group wikipages describe common features of one group of the Events. CNMCyber This Week, CNMCyber Guided Tours, and CNMCyber Welcome wikipages describe series of events. The CNMCyber event wikipage describes common features of all Events. Event group wikipages include deliverable requirements, organizational and technical documentation such as standing operating procedures (SOPs), minutes of the meetings, testing and other reports, etc. Those pages are listed at the "CNMCyber Events" category.
2. Single event wikipages describe particular events. Category names of single events depend on the names of the series they belong to; for instance, "CNMCyber This Week" category, "CNMCyber Guided Tours" category , and "CNMCyber Welcome" category.

Project documents

Location of 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, as well as those communications, memos, meetings, etc. that are related to developments of CNMCyber events depends on predictability of the Events. Project documents for:

1. Predictable events such as CNMCyber This Week, CNMCyber Guided Tours, and CNMCyber Welcome are published on their event group wikipages altogether with their standing operating procedures (SOPs). For the purposes of this very wikipage, predictable events refer to those meetings and conventions that have known agendas, descriptions, locations, speakers, timing, and titles.
2. Unpredictable events are published on single event wikipages. For the purposes of this very wikipage, unpredictable events refer to those meetings and conventions which agendas, descriptions, locations, speakers, timing, and/or titles are not known at the moment when the Org starts organizing them.

Progress on projects to develop particular CNMCyber events is documented using the CNMCyber Event Projects wikipage. It belongs to the "Event Projects" category.

Events

For the purposes of this very wikipage, events refer to meetings or conferences that are planned for special purposes. While organizing events, the Orgs are engaged in the What Orgs do activities.

Authorized events

Those Events that are authorized to practice with are listed on the CNMCyber Event Projects wikipage.

Outreach events

Outreach events, which are CNMCyber events organized to promote the Cyber, the Cloud, CNMCyber Team, technologies, needs, and services to outreach to current and potential clients and participants. Specifically to the Coords, the outreach products include CNMCyber This Week events, which are weekly meetings of the Coords who present (a) what they accomplished last week, (b) what they plan to do next week, and (c) what assistance do they need. The outreach events are normally published on the CNMCyber Meetup group.

What Orgs do

No final instructions exist. Blueprints below represent just suggestions, not strict directions. Based on timing of their Effort cycles, the Orgs' practice can be divided in three sets of processes.

Preparing the Event

To prepare the Event, the Orgs shall:

1. Follow the How to start recommendations.
2. Explore existing CNMCyber events, their documentation at CNM Wiki, other events related to career services that are available on the market.
3. Compare existing CNMCyber events, their documentation at CNM Wiki, as well as other websites related to career services that are available on the market to detect opportunities to improve existing CNMCyber events.
4. Identify the business need that the Event you are about to organize shall satisfy.
5. Create a single event wikipage, while .
6. Report on progress of the initial project discovery using the CNM Website Projects wikipage.
7. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The initial project discovery ends when the business need is identified. New project discoveries belong to the Doing to move forward activities.

Researching the grounds===

To start the initiated project, the Devs shall:

1. Study the website needs and project environments in some depth.
2. Identify those sources, primarily stakeholders and competitors, of information that can be useful for website development.
3. Evaluate what output, a Website idea, a Wiki-based prototype, CMS-based prototype, or Website MVP, is expected from the current efforts, as well as its status of completeness.
4. Update the project and product wikipages, while linking the new data to the identified sources.
5. Report on progress of the project studies using the CNM Website Projects wikipage.
6. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The project studies start after the business need is identified. 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.

Envisioning the solutions===

To plan the researched project, the Devs shall:

1. Identify those target audiences who are supposed to use future deliverables.
2. Create imaginary personas that would represent each of the identified audience.
3. Produce stakeholder requirements for each created persona using CNM Wiki.
4. Conceive what the solutions should look like.
5. Describe the solution or solutions using CNM Wiki.
6. Report on progress of the product description using the CNM Website Projects wikipage.
7. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The product description efforts shall start when business needs are identified and end when a Sprint of the product wikipage development is completed.

Planning the production===

To execute the project plan, the Devs shall:

1. Examine the existing products that are going to be further developed if they are available.
2. Analyze the collected project data while organizing that data on CNM Wiki.
3. Formulate 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.
4. Decide how the imagined solution should be developed.
5. Draft a plan of actions that need to be undertaken in order to execute the development decisions.
6. Publish the project plan on CNM Wiki.
7. Report on progress of the project planning using the CNM Website Projects wikipage.
8. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The project planning efforts shall start no later than completion of product wikipage's Sprint and end when a Sprint of the project wikipage development is completed.

Doing to move forward===

To start a new DREPD cycle, the Devs shall:

1. Act on the plan while doing what is planned such as creating prototypes, producing components, etc.
2. Test the deliverable and, if necessary, its parts.
3. Observe real situations, while detecting what hasn't been expected.
4. Collect data related to the deliverables under development and their production.
5. Analyze the collected project data while organizing that data on CNM Wiki.
6. Re-identify the website need, while discovering new wills. Since new data shall emerge while doing and/or after getting something done, that new discovery shall start a new DREPD cycle.
7. Treat creation of deliverables as primary source of data to revisit the Researching the grounds activities.
8. Revisit the Researching the grounds activities when new data or new sources of data emerges in order to revisit further the Envisioning the solutions and Planning the production activities.
9. Report on progress of the plan executing using the CNM Website Projects wikipage.
10. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The project execution efforts shall start no later than completion of project wikipage's Sprint and end when the CNMCyber website becomes a marketable. The Devs though progress websites to only minimum viable products (MVPs).

1. Create the Event's wikipage

1. Create the event on a Meetup group https://www.meetup.com/techdc/ about 6 days and 23 hours in advance (you also should get the group administrator rights). Later, you can copy meetings and change small details and the date. The event should contain the following information:
   1. title (required);
   2. date and time: Time details;
   3. duration: online events are one hour long;
   4. featured photo: it can be CNM Cyber logo and other logos as well as photos from previous events (if they were offline);
   5. description: it should include meeting details and an agenda, for example: description. You also should add the specific details to be discussed at this particular meeting for each event;
   6. topics: you can pick up to 5 topics. Topics describe what your Meetup event is about in a word or two. They also help show our event to members with matching interests. Select a relevant, but wide range of topics that describe our event. For example: Career Networks, Job Search, Reporting, Recruiting & Hiring, Project Management;
   7. location: the physical location shall have been booked or online room has been created; it is preferable to create a room in CNM Jitsi. There may be problems with CNM Jitsi, so you should have more than 1 alternative video conferencing platform, preferably one internal and one external such as Zoom or Google meet;
   8. allow guests: the number is to be decided, but it's allowed.
2. If special participants are going to be invited to the Event, they need to be identified, contacted, and confirmed;
3. Create the meeting on CNM Jitsi. URL should look like is jitsi.cnmcyber.com/[Name of the project]-[2-digit-year]-[2-digit-month]-[2-digit-day]] such as jitsi.cnmcyber.com/DNSmanagement-23-02-08 and add this to the event on Meetup. There may be problems with CNM Jitsi, so you should have more than 1 alternative video conferencing platform, preferably one internal and one external such as Zoom or Google meet;
4. Create the page of this meeting on wiki. It should include a short description of the meeting subject and brief coordinator's reports and as well as links to predecessor and successor events. The category is yet to be decided.
5. Record of the meeting. You can use this function in CNM Jitsi, OBS Studio, Zoom, or Google meet and have at least 2 alternative programs to record just in case such as Xbox Game Bar or OBS Studio, and you should use 2 programs in parallel, for example, recording in CNM Jitsi + OBS Studio. You may use OBS Studio as your primary recording tool and CNM Jitsi as the secondary recording tool.

To record on OBS Studio:

1. 1. Open your browser, and visit the OBS Studio homepage;
   2. Select the OBS Software instance that the operating system on your computer supports, i.e. Windows, macOS, or Linux from the home page and download will begin automatically;
   3. Open the downloaded file once it has completed and install;
   4. start the meeting as moderator;
   5. Open OBS and click the plus sign in the Sources section;
   6. Select window capture;
   7. create new, and name the window you are about to capture;

To enable the recording function in CNM Jitsi:

1. 1. start the meeting as moderator;
   2. press the three-dot button;
   3. press the "press record" button;
   4. choose the part of the screen;
   5. press the "close access" button if you want to close the meeting, wait until the file is saved and just after that you can close the meeting in CNM Jitsi.

Facilitating the Event

During the Event, the Org will:

1. Be not only a participant but also the host of the event,
   1. connect to the meeting at least 5 minutes before it begins;
   2. switch on the recording of the meeting in CNM Jitsi and in a second another program (read more below Record);
   3. welcome participants;
   4. let participants know that the meeting is being recorded;
   5. familiarize participants with the sample schedule;
   6. introduce participants;
   7. announce the current sections of the meeting;
   8. close the meeting;

Commissioning the records

After the Event, the Org will:

1. Publish the recording on our CNM Cyber YouTube channel and on CNM AVideo. You also should write a description of the video: when you write a description for YouTube, you shouldn't add links to Wiki and to Meetup, but you can add it on AVideo;
2. Share this video of this meeting on the wikipage that was created earlier. The wikipage also shall be composed to include all available data of and about the Event including its minutes, as well as organizing lessons learned;
3. Add useful information to the CNM Social group https://social.cnmcyber.com/s/cnmcyber-event-organizers/ about organizing events;
4. Present your report.

1. Explore existing CNMCyber websites, their documentation at CNM Wiki, other websites related to career services.
2. Compare existing CNMCyber websites, their documentation at CNM Wiki, other websites related to career services to detect opportunities to improve existing CNMCyber websites.
3. Identify the business need that some CNMCyber website may satisfy.
4. Creates a project wikipage, while stating the identified need, its reasoning and backgrounds.
5. Creates a product wikipage, while starting describing the website.
6. Report on progress of the initial project discovery using the CNM Website Projects wikipage.
7. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The initial project discovery ends when the business need is identified. New project discoveries belong to the Doing to move forward activities.

Researching the grounds===

To start the initiated project, the Devs shall:

1. Study the website needs and project environments in some depth.
2. Identify those sources, primarily stakeholders and competitors, of information that can be useful for website development.
3. Evaluate what output, a Website idea, a Wiki-based prototype, CMS-based prototype, or Website MVP, is expected from the current efforts, as well as its status of completeness.
4. Update the project and product wikipages, while linking the new data to the identified sources.
5. Report on progress of the project studies using the CNM Website Projects wikipage.
6. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The project studies start after the business need is identified. 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.

Envisioning the solutions===

To plan the researched project, the Devs shall:

1. Identify those target audiences who are supposed to use future deliverables.
2. Create imaginary personas that would represent each of the identified audience.
3. Produce stakeholder requirements for each created persona using CNM Wiki.
4. Conceive what the solutions should look like.
5. Describe the solution or solutions using CNM Wiki.
6. Report on progress of the product description using the CNM Website Projects wikipage.
7. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The product description efforts shall start when business needs are identified and end when a Sprint of the product wikipage development is completed.

Planning the production===

To execute the project plan, the Devs shall:

1. Examine the existing products that are going to be further developed if they are available.
2. Analyze the collected project data while organizing that data on CNM Wiki.
3. Formulate 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.
4. Decide how the imagined solution should be developed.
5. Draft a plan of actions that need to be undertaken in order to execute the development decisions.
6. Publish the project plan on CNM Wiki.
7. Report on progress of the project planning using the CNM Website Projects wikipage.
8. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The project planning efforts shall start no later than completion of product wikipage's Sprint and end when a Sprint of the project wikipage development is completed.

Doing to move forward===

To start a new DREPD cycle, the Devs shall:

1. Act on the plan while doing what is planned such as creating prototypes, producing components, etc.
2. Test the deliverable and, if necessary, its parts.
3. Observe real situations, while detecting what hasn't been expected.
4. Collect data related to the deliverables under development and their production.
5. Analyze the collected project data while organizing that data on CNM Wiki.
6. Re-identify the website need, while discovering new wills. Since new data shall emerge while doing and/or after getting something done, that new discovery shall start a new DREPD cycle.
7. Treat creation of deliverables as primary source of data to revisit the Researching the grounds activities.
8. Revisit the Researching the grounds activities when new data or new sources of data emerges in order to revisit further the Envisioning the solutions and Planning the production activities.
9. Report on progress of the plan executing using the CNM Website Projects wikipage.
10. Present the progress, plans and possible concerns during CNMCyber This Week meetings.

The project execution efforts shall start no later than completion of project wikipage's Sprint and end when the CNMCyber website becomes a marketable. The Devs though progress websites to only minimum viable products (MVPs).

Hiring

Everyone is welcome to apply. Attracting participants of the Event is not a part of the Org role. Usually, CNMC Event Administrator is responsible for that task.

Announcement

An initiative group is currently looking for a "Meeting Organizer" to join our future team. This is an entry level position with opportunity for growth. The candidate is expected to organize one or more weekly meetings to discuss challenges, especially in recruitment, that the Community faces.

Job Description:

Primarily, organize one or more CNM Cyber roundtables. In addition:

1. Research and recommend new sources for active and passive candidate recruiting;
2. Network and maintain relationships with key talent communities for short and long-term opportunities;
3. Develop a sustainable talent acquisition and hiring strategy to meet growth needs of the Community;
4. Find bottlenecks in the recruiting process and provide suggestions for improving the candidate experience;
5. Develop a broad professional network of top talent;
6. Stay current on market trends and competitors within our industry.

Requirements:

1. Must be able to read, write, speak, understand and comprehend some level of English;
2. High School Diploma or equivalent is not required; Bachelor's Degree or graduate degree may be an obstacle;
3. Excellent communication skills and/or ability to acquire those skills are required;
4. Must be able to work or learn to work as part of a team;
5. Strong problem-solving and analytical skills and/or ability to acquire those skills are required.

What to expect

1. If you succeed to state what valuable you would do for this project, you will get a job offer for 5 hours weekly. In this particular project, the job offer is more like a beginning rather than the destination point. Your skills would be assessed based on your performance, not "interviewing".
2. If you succeed not to state anything concrete (let say, you say some nonsense similar to "I will deliver on this project by scheduling meetings and ensuring they are successful and their outcome can be felt immediately"), you can be offered to organize one meeting just to see that you are able to do something valuable knowing that you are not able to write.
3. When you start working, you can expect detailed feedback. Questions, creative solutions, and taking risks are especially welcome. Under any circumstance, you will not be punished for taking a risk if your endeavor is undertaken within the scope of the project. Your charges will be disputed if you try to charge the financier for your personal stuff such as working on other projects, chatting to your friends on Facebook, etc.
4. If you succeed to organize at least one meeting within a week, your contract will be extended. A bad meeting is better than no meeting at all -- no one is perfect, so is your performance expected to be.
5. If you succeed to organize no meeting within a week, the contract will be paused, you will be asked why and, if no clear output is achieved, the your contract will be ended. This doesn't mean that we cannot work on other projects.

Please note that Gary aka "Igor" is widely available for soliciting additional requirements from him. All currently available requirements are posted at CNM Cyber roundtable -- please visit the link. It is under constant development, but it reflects the current state of development.

Development

History

The role was identified in early July of 2018. The job announcement was published on July 10th. Fourteen initial job offers were sent; two of them were never accepted and eight of contractors either have never started working or started in unacceptable ways.

On August 2nd, 2018, michael succeeded to organize the first meeting. On August 4th, Gary aka "Igor" sent the following message to every of four contractors working on the role:

Today marks three weeks that we have been collaborating on the project. Since we have already had the first meeting, it is successful. In a week, I will be evaluating your contributions to its success. If you don't organize any meeting and/or contributed to the wikipages, I will end our contract, while marking your work as success, giving all-star rating, and positive feedback. Meeting my expectations is not a challenge. You have met those and I appreciate your service. However, we need to keep going forward. I would like to see that you are able to move this project to the next level, which are development/brainstorming meetings every day and fully staffed https://wiki.ksacerts.com/en/WorldOpp_incubator. Thank you so much for everything you have done!

See also

Related concepts

• CNMCyber event.

Related lectures

• CNMC Workforce Essentials.