CNMCyber transcript

Script Development for CNMCyber Events

What is a script

Script is technically wording which is used in CNMCyber Office Hours events. In the best case scenario, it should be typed and moved to the requirements.

The script can also be defined as the record of someone's requirement.

A script is also an intermediate product, it's not a final product. It's a deliverable but is not user deliverable. It's a sub-product. So then when a script is available, a Wiki page can be developed from the requirements in the script.

Purpose and Importance of Scripting

• To have a written record of requirements discussed during the event.
• Support traceability between event discussions and final wiki pages. The script itself leads to requirements. The script isn't the final product, but the requirements that a customer agrees to become the actual product. This can be measured, and in the best situation, it should be a requirements traceability matrix (RTM) record.

For example, when you write down requirements on a page, imagine it's what you're presenting to your boss or customer. You're saying, "This is what you'll get." You list down everything – like having HumHub, Odoo, Jitsi set up in a certain way, using ProxmoxVE, making it highly available with three nodes, having a public IPv4 network, running on Apache and Nginx, using Ceph for storage, and monitoring with PF Sense. You ask, "Is this what you want?" They either sign or confirm via email. This becomes a kind of blueprint.

Components of a script

A script should focus on important information, omitting irrelevant details. A script should omit things like;

• "my name is _ _ _"
• "sorry I need to drink my coffee,"
• "give me a post I will like,"
• "I will answer another call."

It's not important. So script should include what is important, what should be and what can be moved to requirements.

Scripting for CNMCyber Events

Scripts will be developed on wiki project page (currently - discussion page) of the product page. The main page is the product and discussion will be a project. Project (current discussion page), here there will be information how the product was developed and what requirements were involved.

Target Audience and Deliverables

A developer working on the product is the target audience of the script. Script by itself is the intermediate product, the product page is the end product and script is a part of development with a deliverable.

Success Criteria and Desired Outcome

Success for a script is determined by how useful it is. The goal is having Wiki Pages that describe products. For example; we need to have this platform on which our Jitsi will work, which is called talk and we will do this conference one day on the Talk.cnmcyber.com slash something - So right now we are doing this on employableU which is temporary. So the end product is the service but to build this firm we need to have a description of what we are doing, what we need to look for, and what we need to do. So now, in this case the desired out come is a working technology.

The technical sense, quality is confirmation the description of the product matches the product itself right. So we have requirements and we have a product. If there's gaps, it's a quality product. But to know that you have a quality product you need to have a description, if you don't have a description how would you know? Scripting is a good way to build this description.

Steps to create a script

1. Transcribe the audio - This can be done manually by listening and typing or if the event is posted on YouTube Channel you can extract the transcript by clicking on the three dots at the bottom right of the video and select show transcript. A side bar will be displayed with the transcript and time stamps. Highlight the entire transcript then copy and paste to the page where you will create the script from.
2. Clean up the transcript - correct any mistakes in the transcription, eliminate timestamps, and filler words such as "um," "hmm," "oh," "like," "you know," "so", as well as any unnecessary side conversations or interruptions that shouldn't be in the final script. Also remove any repetitions.
3. Structure the information - Break the transcript into logical sections using headers. For example, you may have a section for Introduction, topics that were discussed in the meeting
4. Focus on key points - Summarize the script while paying attention to key questions, decisions, and discussion points that are relevant for the requirements of the product.
5. Review the scrip - Go over the draft script and make any final edits to improve clarity. The goal is to create a traceable record of the event that can used to create product requirements.
6. Save the script - Save the script to the discussion page (project page) of the product being developed.