|
|
| (588 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | [[CNM Website Developer]] (hereinafter, the ''Coord'') is the pre-entry-level position that [[The Economic Group]] has developed and markets as a job opportunity for vocation discoverers, soft skills builders, career developers, employment gap fillers, and those learners who are undergoing initial practical training while being matriculated into the [[CNM Cyber Placement]] stage (hereinafter, the ''Placement''). | + | A [[CNM Website Developer]] (hereinafter, the ''Dev'') is an incumbent of the scholar-tier [[CNMCyber practice]] (hereinafter, the ''Practice'') that [[The Economic Group]] has developed to practically introduce [[CNMCyber patron]]s to [[website project]]s. The ''Devs'' specialize in the development of [[CNMCyber website]]s, including designing and developing website contents, [[information architecture]]s, [[SEO]], software, and WWW settings. |
| | | | |
| − | The ''Placement'' is a part of the [[WorldOpp Pipeline]] program (hereinafter, the ''Program''). [[CNM Cyber]] (hereinafter, the ''Cyber'') is a collection of [[career service]]s that include (a) information technology called [[CNM Cloud]] (hereafter, the ''Cloud''), as well as (b) support for apprenticeships, internships, and jobs that are organized at the ''Cloud'' specifically or the ''Cyber'' generally. | + | The ''Practice'' is part of the [[Website Developer Bootcamp]] (hereinafter, the ''Bootcamp''), which is the second quarter of [[CNMCyber Bootcamps]]. The lessons in this quarter are specifically designed to prepare ''Devs'' for the ''Practice''. |
| | | | |
| | + | The ''Practice'' is offered to those [[KSA Certified Event Organizer]]s who successfully pass [[CNM Website Development Exam]] after taking the ''Bootcamp's'' lessons. By successfully completing of the website development practice, the ''Residents'' become [[KSA Certified Website Developer]]s. |
| | | | |
| − | ==Trivia==
| + | As the ''Dev'', you will have the opportunity to work on real-world [[Website Projects]] and gain hands-on experience. Our program offers comprehensive training that equips you with the skills and knowledge to succeed in the field of [[Website Development]]. Join us today and kick-start your career in [[Website Development]]. |
| | | | |
| − | ===Benefits===
| |
| − | : The ''Cyber'' provides every ''Coord'' with opportunities to:
| |
| − | :# '''Get prepared to get employed'''. The package of (a) [[CNM Cyber Welcome Session]], (b) [[CNM Cyber Orientation]], and (c) [[CNM Cyber Placement]] is designed to provide the learners with theoretical knowledge from scratch and place them in pre-entry-level jobs.
| |
| − | :# '''Start working''' in a pre-entry-level position of the ''Coord'' in order to (a) possess work experience, (b) advance their [[soft skill]]s, as well as (c) get introduced to various professions practically.
| |
| − | :# '''Identify the target profession''' and, if needed, outline the professional preparation at the [[WorldOpp Bootcamp]] and [[WorldOpp Employment]] package.
| |
| | | | |
| − | ===Competencies=== | + | ==Career objectives in [[ Website Development ]]== |
| − | : No specific [[knowledge, skills, and abilities]] are required to begin. Vice versa, the ''Coord's'' position is created to build or refresh so-called [[soft skill]]s. The ''Coords'' work with documents, technology, and other people, while entering the industry, building their general expertise, and observing what various professions look like.
| |
| | | | |
| − | : The [[#Team|Team]] provides all of the interested candidates with free-of-charge training. Once again, no prior training and no experience are needed in order to get started. The ''Coords'' are encouraged to start from scratch and go where ever they dream.
| + | If you're interested in pursuing a career in [[Website Development]], there are many challenges to overcome and credentials to earn. However, with the right knowledge, you can pave the way to a successful career in this exciting field. |
| | + | |
| | + | ===Credentials=== |
| | + | : As a result of the ''Practice'', the ''Devs'' shall obtain the following [[professional credential]]s: |
| | + | :* [[Work experience]], which the ''Dev'' may include in his or her [[resume]]. |
| | + | :* [[Professional recommendation]], which the ''Dev's'' formal mentor shall generate. |
| | + | :* [[KSA Certified Website Developer]] credential. |
| | | | |
| − | ===History=== | + | ===KSAs=== |
| − | : ''Main wikipage: [[History of CNM Cyber Coordinators]]''
| + | At our program ,we focus on helping you acquire the [[knowledge, skills, and abilities]] ([[knowledge, skills, and abilities|KSA]]) you need to succeed in [[ Website Development ]]. |
| | | | |
| − | : History of the ''Coord's'' position encompasses about nine years that witnessed tech advancements, Bskol and iDosvid spins-off, concept proving and re-launch. | + | ===Further paths=== |
| | + | : Upon graduation from the ''Practice'', the ''Devs'' are recommended to choose one or more of the following options: |
| | + | # Continue with other [[CNMCyber practice]], while becoming a [[CNM Event Organizer]]. |
| | + | # Decide to concentrate on specific website development professions, possibly, mentioned in the [[#Occupations|Occupations]] section. |
| | + | # Work on own projects. |
| | | | |
| − | ===Position=== | + | ===Occupation=== |
| − | : The ''Coord'' is marketed as a pre-entry-level position. [[Entry-level job]]s usually are offered to those who got trained in a particular profession, but hasn't had any experience yet. The ''Coord'' position is designed for those who obtained neither formal training nor expertise. | + | : A website developer can be defined as anyone who develops websites; nevertheless, such a position rarely exists in the real workplace. Some companies call web developers "website developers". In the meanwhile "classic" web development targets software, while website development doesn't imply software only. |
| | | | |
| − | : 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''. | + | : The ''Dev's Practice'' touches many occupations. They may include one or more of the following: |
| | + | :* '''Architecture and design''' such as Human Factors Engineers and Ergonomists, Information Architects, as well as Web and Digital Interface Designers as long as the ''Devs'' design website contents, interfaces, and structures, this could be the right path for you. |
| | + | :* '''Content creation''' such as Producers and Directors, Proofreaders and Copy Markers, as well as Writers and Authors as long as the ''Devs'' create website contents such as graphics, multimedia, and texts, this could be the right path for you. |
| | + | :* '''Technology development''' such as Architectural and Engineering Managers, Software Developers, as well as Web Developers as long as the ''Devs'' work with the technologies behind the website, this could be the right path for you. |
| | + | :* '''Web-search marketing''' as Search Marketing Strategists as long as the ''Devs'' work on [[search engine optimization]] ([[search engine optimization|SEO]]), this could b the right path for you. |
| | | | |
| − | : However, the ''Coord's'' position is a point of entrance, not a destination. Based on the ''Coords<nowiki>'</nowiki>'' experience, they [[#Coords' placement|may be placed]] in professional jobs such as [[CNM Cyber Project Manager]], [[CNM Cyber Recruiter]], [[CNM Cyber Security Analyst]], [[CNM System Administrator]], [[CNM Systems Engineer]], [[CNM Web Developer]], as well as positions available through ''Cyber'' partners. | + | : Upon their graduation from the ''Practice'', the ''Devs'' may choose to concentrate on one or more of the real professions listed above. |
| | | | |
| − | ===Target audiences===
| + | No matter which path you choose, our program can help you acquire the [[KSAs]] you need to succeed. Join us today and start your journey towards a rewarding career in [[Website Development]]. |
| − | : The [[#Team|Team]] believes that, besides the ''Placement'' learners, a few audiences can get benefited from service as the ''Coord''. They are:
| |
| − | :# '''Vocation discoverers''' such as middle- and high-school students, as well as someones else who consider what profession they would like to pursue. While serving as ''Coords'', they will be exposed to a variety of professions and can pick up their own one.
| |
| − | :# '''Skills builders'''. The ''Coord's'' work by itself delivers valuable practical experience and build-up of [[soft skill]]s to the ''Coords''.
| |
| − | :# '''Career developers'''. Over its years, the ''Cyber'' witnessed many successes of people who transitioned from one industry and/or profession to other ones. Normally, one employer utilizes a limited scope of processes and technologies; consequently, scopes of competencies of its employees are limited as well. Someones who are currently employed, but would like to obtain wider skill-sets, may dedicate few hours a week, month, or even a year to explore something new in their industries and/or professions or outside of those.
| |
| − | :# '''Employment gap fillers'''. Those who need to drop out from the formal workforce, for instance, due to medical or family issues, may utilize the ''Coord'' work to fill in employment gaps.
| |
| | | | |
| − | ==What Coords produce== | + | ==Website Development Position and Practice Choices== |
| − | To facilitate development and/or management of [[#Cyber products|Cyber products]], the ''Coords'' produce four categories of their first-level results: (1) [[#Meetings|Meetings]], (2) [[#Documents|Documents]], (c) [[#Records|Records]], and (d) [[#Communications|Communications]].
| + | As a''Dev'' your main responsibility is to undertake [[website project]]s to develop [[CNMCyber website]]s. To learn about benefits, competencies, history, supervision, and target audiences, please consult the '''[[CNMCyber practice]]''' wikipage. |
| | | | |
| − | ===Communications=== | + | ===Choice of practice=== |
| − | : 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''. | + | : By default, the ''Devs'' choose [[#Projects|Projects]] that suit them best. The ''Devs'' can choose between: |
| | + | :* [[#Authorized projects|Authorized projects]] that [[CNMCyber Customer]] authorized for funding. Any ''Dev'' is welcome to pick any project that he or she would like to practice with. |
| | + | :* Their own projects for which they can request [[CNMCyber Customer]]'s authorization. |
| | | | |
| − | : The ''Coords'' run their communications to make development of [[#Cyber products|Cyber products]] possible. These communications include: | + | : In addition, [[CNMCyber Project Manager]]s may ask a ''Dev'' to take an urgent or specific project when they understand the ''Dev's'' professional capacity. Particularly, that means that the ''Devs'' have to choose their first project at least. |
| − | :* '''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|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.
| + | ===Goals and objectives=== |
| − | | + | : Each particular ''Dev'' establishes their own goals and objectives based on their [[#Career objectives|Career objectives]] and [[#What Devs produce|What Devs produce]] requirements. |
| − | ===Documents=== | + | Whether you are a seasoned professional or just starting out, our program can help you achieve your goals and develop the skills you need to succeed in [[Website Development]]. This means that the ''Devs'' have to choose their first project at least. |
| − | : 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 [[#Cyber products|Cyber 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 [[contract]]s.
| |
| − | :* '''Outreach materials''', which are marketing drafts intended to outreach to current and potential clients and participants such as [[Friends Of CNM newsletter]]s.
| |
| − | :* '''Product documents''', which are descriptions of former, existing, and future products published at [[CNM Wiki]], as well as deliverable requirements, emails and other messages between product owners and developers, organizational and technical documentation such as [[standing operating procedure]]s ([[SOP]]s), minutes of the meetings, testing and other reports, etc.
| |
| − | :* '''[[Project document]]s''', which are project requirements, progress reports, emails and other messages between project owners and developers, memos with the results of project approvals, developments, meetings, and research.
| |
| − | :* '''[[Webpage text]]s'''
| |
| − | | |
| − | : 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 [[#Cyber products|Cyber 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 [[#Cyber products|Cyber 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 [[CNM Cyber Project Manager]] organized to discuss potential entering into a [[contract]] and/or to make that decision.
| |
| − | :* '''Outreach events''', which are [[CNM Cyber event]]s organized to promote the ''Cyber'', the ''Cloud'', its [[#Team|Team]], technologies, needs, and services to outreach to current and potential clients and participants. Specifically to the ''Coords'', the outreach products include [[Week at CNM Cyber]] 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 at the [[CNM Cyber Meetup]] group.
| |
| − | :* '''Product meetings''', which are meetings organized (a) to discuss deliverable features, (b) to make deliverable decisions, and/or (c) to communicate those decisions.
| |
| − | :* '''Project meetings''', which are meetings organized (a) to discuss project features, (b) to make project decisions, and/or (c) to communicate those decisions.
| |
| − | | |
| − | : Within the [[#Project results|Project results]], the outreach events represent [[project output]]s. The other meetings should be considered as [[project scrap]]; those meetings are used to develop [[#Documents|Documents]].
| |
| − | | |
| − | : Moreover, meetings tend to address a number of purposes. For instance, meetings of the [[CNM Technology Board]] may touch both product and project features and decisions. When they are open to the general public, they also serve the outreach purpose.
| |
| − | | |
| − | ===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 [[document]]s.
| |
| − | | |
| − | : To support development of [[#Cyber products|Cyber products]], the ''Coords'' collect records, place them in designated spaces, and, if applicable, manage their storage. Special [[standing operating procedure]]s ([[standing operating procedure|SOP]]s) shall designate spaces for that purpose. Those records may include:
| |
| − | :* '''Archived files''' such as videos, audios, textual files, as well as coded and programmed scripts.
| |
| − | :* '''Databases''' of contacts, competencies of contractors, characteristics of tested software, etc.
| |
| − | :* '''Enterprise records''' such as [[contract]]s, which are legally-binding agreements, applications and reports that are officially submitted to governmental bodies and partners, identification and other personal documents of ''Cyber's'' employees that the law requires to keep in the enterprise system, accounting records, etc. At the ''Cyber'', enterprise records are stored at [[CNM Venture]].
| |
| − | :* '''Product records''' such as approved requirements for the project deliverable are posted at [[CNM Wiki]]. To be product records, they need to be protected from unauthorized edits and belong to the [[:Category: Product records|Product records]] category.
| |
| − | :* '''Project records''' are kept at several spaces depending on their nature. Project reports are posted at the [[CNM Cloud Usable]] wikipage. Legally-binding documents are stored at [[CNM Venture]]. Accepted deliverables are stored at [[CNM Repo]].
| |
| − | :* '''Publications''' such as minutes of meetings and others textual records that reflect past events, content of [[CNM Repo]], [[CNM Page|Page]], [[CNM Social|Social]], and [[CNM Wiki|Wiki]], as well as those postings on [[YouTube]], [[CNM Cyber Meetup]], and other [[social media]] that the ''Coords'' may make. There is no single place for publications' storage at the ''Cyber''; they are posted at different media. [[CNM Wiki]] can be used for development of publications; appearance of [[CNM app]]s at the [[WWW]] can also be considered as publications.
| |
| − | :* '''Technology records''' such as access credentials and detailed descriptions of software used in the ''Cloud''. At the ''Cyber'', technology records are stored at [[CNM Repo]].
| |
| − | | |
| − | : Within the [[#Project results|Project results]], the records represent [[project output]]s by their definition.
| |
| − | | |
| − | ==Work in general==
| |
| − | The ''Coords'' work is to facilitate someone else's performance on [[#Projects vs operations|Projects vs operations]] related to [[#Cyber products|Cyber products]]. 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.
| |
| − | | |
| − | ===Choice of work===
| |
| − | : By default, the ''Coords'' choose [[#Endeavors|Endeavors]] that suit them best. [[CNM Cyber 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.
| |
| − | | |
| − | : The work of the ''Coords'' is paid when they work on those endeavors that funding is authorized on the '''[[CNM Cloud Usable]]''' wikipage. That page contains links to:
| |
| − | :* Endeavors that the ''Coords'' can work on. Those pages are called "endeavor pages" and are combined in the [[:Category:CNM Cyber 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, [[CNM WordPress]].
| |
| − | | |
| − | : 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.
| |
| − | | |
| − | ===Hours of work===
| |
| − | : The ''Coords'' choose their schedule. Rarely, they get more than 20 hours a week to leave enough time for looking for an [[entry-level job]] or another regular employment. The ''Coords'' are encouraged to serve as [[#Contractors|Contractors]] outside of their ''Coord's'' work; there are no limits on hours of contracting.
| |
| | | | |
| | ===How to start=== | | ===How to start=== |
| − | : Are you interested in getting started as the ''Coord''? Please follow a step-by-step instruction as follows: | + | : Are you interested in getting started as the ''Dev''? Please follow the step-by-step instructions: |
| − | :# '''Read''' this wikipage. If you cannot read, you cannot work. This wikipage contains everything you need; however, its content is neither intuitive nor user-friendly yet. | + | :# Until [[Website Developer Bootcamp]] is fully developed, briefly '''review''' the following wikipages:<ol type="a"><li>This very wikipage, it describes your website development ''Practice'' specifically,</li><li>[[CNMCyber practice]], it describes your ''Practice'' generally,</li><li>[[Website project]], this describes those projects that could be undertaken to develop websites, not specific to your ''Practice'', but your ''Practice'' can correlate to them,</li><li>[[CNMCyber website]], it describes the websites you are about to develop, and</li><li>[[CNM Website Projects]], it describes those projects that are authorized to practice with.</li></ol>Those wikipage contents are neither intuitive nor user-friendly yet; however, if you cannot read them, you cannot work. |
| − | :# '''Ask''' questions. Questions are a huge part of your work; if you cannot ask, you cannot work. If you prefer videoconferences, attend any [[Week at CNM Cyber]] event. You will have opportunities to ask questions and get responses in real time.
| + | :# '''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. |
| − | :# '''Study''' this wikipage to be ready to discuss two topics: (a) what paragraph is intentionally left unclear and (b) what section can be taken out without big harm. You will be offered to discuss those topics during your job interview. Why? If you don't know your job, you cannot work.
| + | :# '''Study''' this very and [[CNMCyber practice]] wikipages in details to be ready to discuss two topics: a). what paragraph is left unclear and b) what section can be taken out without causing significant damage. You will be offered to discuss those topics during your job interview. Why? If you don't know your job, you cannot work. |
| − | :# '''Understand''' why the ''Cyber'' project is undertaken and what value is expected from the ''Coord''. That's simple. If you cannot deliver what the [[#Customer|Customer]] pays for, you cannot work. Everything that the [[#Customer|Customer]] pays for is stated on this very wikipage. | + | :# '''Be''' prepared to learn while practicing. For instance, [[CNM Wiki]] is one of the ''Dev's'' primary tools. The [[lectio]]s of [[CNMCyber]] that cover usage of that wiki include [[What CNM Wiki Is]], [[Collaboration on Documents]], [[Functions of Wiki]], and [[CNM Wiki at Cyber]]. However, they cannot cover all that the ''Devs'' need. At the same time, the [[World Wide Web]] ([[World Wide Web|WWW]]) contains additional resources for [[MediaWiki]], which is the software behind [[CNM Wiki]]. The ''Devs'' face similar challenges while learning about [[DNS]], [[website IA]], [[WordPress]], as well as other tools and knowledge frameworks that the [[CNMCyber Team]] utilizes in website development. |
| − | :# '''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 at [[CNM Tube]] and [[YouTube]]. Some of course wiki-materials are linked to [[CNM Cyber Welcome Session]], [[CNM Cyber Orientation]], and [[CNM Cyber Placement]] wikipages | + | :# If you are willing to be paid, '''understand''' why the ''Cyber'' project is undertaken and what value is expected from the ''Dev''. That's simple. If you cannot deliver what [[CNMCyber Customer]] pays for, you cannot work. Everything that [[CNMCyber Customer]] pays for is stated on this very wikipage. |
| − | :# '''Pick up''' your first endeavor at the [[CNM Cloud 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''.
| + | :# '''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. |
| − | :# '''Contact''' the [[#Customer|Customer]] while stating (a) the effort 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.
| + | :# At the [[CNM Website Projects]] wikipage, '''pick up''' the project you would like to practice with. You may have no idea what that particular project is about. First of all, no project is fully clear and, secondly, to learn about one project is always simpler than to learn about many. When you diligently study this very wikipage and understand what your objectives are, you should know how to go about that project. If you cannot pick your project, you cannot start working as the ''Dev''. |
| − | | + | :# '''Present''' your pick during a [[CNMCyber This Week]] event, while stating (a) the project 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. |
| − | : By the way, you can be paid to ask questions about this wikipage when you identify the endeavor behind that page. | + | :# '''Wait''' for [[CNMCyber Customer]]'s approval or feedback to start your ''Practice'' this week or modify your proposal. |
| − | | |
| − | ===Supervision===
| |
| − | : The ''Coords'' work with no supervision. They choose their endeavors, get or don't get the [[#Customer|Customer]]'s authorization, collaborate with the [[#Administrators|Administrators]], [[#What Coords produce|produce what the ''Coords'' produce]], and submit the outputs of their 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]].
| |
| − | | |
| − | 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:CNM Cyber endeavors|"CNM Cyber endeavors" category]].
| |
| − | | |
| − | ===Endeavor documents===
| |
| − | : At [[CNM Wiki]], ''Cyber'' endeavors are documented using two types of wikipages:
| |
| − | :# The progress on particular endeavors is reported at the [[CNM Cloud Usable]] wikipage.
| |
| − | :# Endeavor pages document everything, but progress reports. Those pages are listed at the [[:Category:CNM Cyber endeavors|"CNM Cyber endeavors" category]] and include [[project document]]s such as [[project charter]], [[asset register]], [[competency register]], [[stakeholder register]], [[requirements traceability matrix]], [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]].
| |
| − | | |
| − | ===Projects vs operations===
| |
| − | : The ''Coords'' work and/or facilitate someone else's work on endeavors, which are either:
| |
| − | :* '''Product development projects''' are development endeavors; they are undertaken to create new products or new features of existing products, which is addressed in the [[#Projects|Projects]] section of this wikipage. Projects are temporary endeavors; they close when the [[#Team|Team]] receive all of the required deliverables and [[#Contractors|Contractors]] receive their compensation. While working on projects, the ''Coords'' are engaged in the [[#Formalizing the project|Formalizing the project]], [[#Specifying the deliverables|Specifying the deliverables]], [[#Planning the project|Planning the project]], [[#Creating the deliverables|Creating the deliverables]], and [[#Commissioning the product|Commissioning the product]] activities.
| |
| − | :* '''Product management operations''' are operational endeavors; they are undertaken to manage existing [[#Cyber products|Cyber products]], including their service, maintenance, audits and revisions, as well as end of life. [[Ongoing operations]] 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.
| |
| − | | |
| − | : 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.
| |
| − | | |
| − | ===Sets of processes===
| |
| − | : Any endeavor can be viewed as sets of [[process]]es. On that very wikipage, those processes are grouped in nine sections of [[#What Coords do|What Coords do]].
| |
| − | | |
| − | : 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.
| |
| − | | |
| − | ===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<nowiki>'</nowiki>'' endeavors are not undertaken systematically.
| |
| − | | |
| − | ==What Coords do==
| |
| − | The ''Coords<nowiki>'</nowiki>'' work can be divided in nine [[#Sets of processes|Sets of processes]]. Every [[#Endeavors|Endeavor]] shall start with [[#Formalizing the project|Formalizing the project]], go through at least [[#Studying the backgrounds|Studying the backgrounds]] and [[#Creating the deliverables|Creating the deliverables]], as well as end from the [[#Managing the product|Managing the product]] activities.
| |
| − | | |
| − | ===Formalizing the project===
| |
| − | : For the purposes of this very wikipage, project formalization refers to the set of efforts that is undertaken to the extent necessary to start researching the backgrounds for envisioning of [[#Project deliverables|Project deliverables]] and their production. This formalization aims to setup the stage for [[#Studying the backgrounds|Studying the backgrounds]] activities.
| |
| − | | |
| − | : 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 [[#Customer|Customer]]'s [[business requirement]]s or those product and/or project requirements of the [[#Customer|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 [[CNM Cyber]], they may be stated in one or more of the following:
| |
| − | :* [[Business case]]. A description of the [[#Customer|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]]).
| |
| − | | |
| − | : On a slang, non-negotiable requirements are called "hard requirements". The ''charter'' contains all of the hard requirements that come from the [[#Customer|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.
| |
| − | | |
| − | : To coordinate the project formalization, the responsible ''Coord'':
| |
| − | :# '''Collects''' data related to the [[business requirement]]s from the [[#Customer|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 the [[#Customer|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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] 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 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.
| |
| − | | |
| − | : Endeavor studies shall produce data needed for (a) envisioning of the product, (b) planning its production, and (c) managing the produced product. At [[CNM Cyber]], 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 the [[#Team|Team]].
| |
| − | :* Product user group at [[CNM Social]], 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|"CNM Cyber 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 CNM Cyber/Cloud/Opplet/Farms" format. They belong to the [[:Category:CNM Cyber endeavors|"CNM Cyber 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]], [[#Team|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.
| |
| − | | |
| − | : To coordinate the project studies, the responsible ''Coord'':
| |
| − | :# '''Identifies''' those available resources that should or can be used in project activities. Human resources include [[#Team|Team]]. Other resources include those presented in the initial [[WorldOpp Pipeline]] courses, on [[CNM Wiki]], existing tools, materials, prototypes, and finished products available at [[CNM Cyber]], 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 [[CNM Social]] 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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] 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'':
| |
| − | :# '''Collects''' data related to [[stakeholder requirement]]s for the project deliverables and [[product specification]]s using the [[asset register]], [[competency register]], and [[stakeholder register]]. This collection includes communications with stakeholders and review of documents and other assets that are registered.
| |
| − | :# '''Examines''' available prototypes, unfinished and finished products against the collected data.
| |
| − | :# '''Analyses''' the collected product data while organizing that data on [[CNM Wiki]].
| |
| − | :# '''Clarifies''' the collected data based on the examined prototypes and finished products.
| |
| − | :# '''Identifies''' those target audiences who are supposed to use future deliverables.
| |
| − | :# '''Creates''' imaginary personas that would represent each of the identified audience.
| |
| − | :# '''Produces''' [[stakeholder requirement]]s for each created persona using [[CNM Wiki]].
| |
| − | :# '''Composes''' [[product specification]]s based on the produced [[stakeholder requirement]]s using [[CNM Wiki]].
| |
| − | :# '''Traces''' in a [[requirements traceability matrix]] the formalized [[stakeholder requirement]]s from their sources to perspective project deliverables.
| |
| − | :# '''Makes''' sure that (a) the [[product specification]] supports the [[stakeholder requirement]]s and (b) all the deliverable data is published on [[CNM Wiki]].
| |
| − | :# '''Checks''' [[product specification]]s for completeness. This completeness shall be characterized by the presence of conditions for (a) functionality, (b) applicability, and (c) manageability of the deliverables. Conditions for functionality should include measures for product's performance. Conditions for applicability should include measures for product's deployment, testing, diagnostics, accessibility, serviceability, protection, and capacity to recover after disasters; these measures must be documented in product's [[standing operational procedure]] ([[standing operational procedure|SOP]]). Conditions for manageability should include measures for product's monitoring, periodic audits and revisions, as well as timely software updates for the [[#COTS software|COTS software]] products.
| |
| − | :# '''Updates''' the [[stakeholder requirement]]s and [[product specification]]s when ever new data from existing and/or new sources emerge.
| |
| − | :# '''Requests''' assistance of the [[#Administrators|Administrators]] when additional resources are needed.
| |
| − | :# '''Reports''' on progress of the product specification using the [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] meetings.
| |
| − | | |
| − | :The product specification opens when the [[#Customer|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'':
| |
| − | :# '''Collects''' data related to [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]] using the [[asset register]], [[competency register]], and [[stakeholder register]]. This collection includes communications with stakeholders and review of documents and other assets that are registered.
| |
| − | :# '''Examines''' the existing products that are going to be further developed if they are available.
| |
| − | :# '''Analyses''' the collected project data while organizing that data on [[CNM Wiki]].
| |
| − | :# '''Formulates''' the difference between what actually is and what is needed to be. The existing products are what actually is, while the specified deliverable is what is needed to be. The project activities shall address this identified difference; they represent what needs to be done.
| |
| − | :# '''Drafts''' a [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]], based on the resources recorded in the registers.
| |
| − | :# '''Makes''' sure that the [[acceptance criteria]] supports the [[project scope baseline]] and [[project schedule baseline]].
| |
| − | :# '''Submits''' the drafted [[project scope baseline]], [[project schedule baseline]], [[project cost baseline]], and [[acceptance criteria]] for the [[#Customer|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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] meetings.
| |
| − | | |
| − | : Similarly to [[#Specifying the deliverables|Specifying the deliverables]], the project planning opens when the [[#Customer|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 rules 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<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]].
| |
| − | | |
| − | : 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'':
| |
| − | :# '''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 the [[#Customer|Customer]] for making the decision either to bring external contractors on the board or not to bring. The positive decision assumes the [[#Customer|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 [[CNM Cyber 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, the [[#Customer|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''' the [[#Customer|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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] meetings.
| |
| − | | |
| − | : The hiring of contractors opens when the 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|Contractors]] to deliver rightly right project deliverables or other requested services. To coordinate collaboration with contractors, the responsible ''Coord'':
| |
| − | | |
| − | :# '''Serves''' as an liaison between the [[#Customer|Customer]] and contractors, reporting problems that need to be resolved.
| |
| − | :# '''Organizes''' videoconferences or other meetings of parties interested in the project, especially those necessary to resolve problems arising during the project.
| |
| − | :# '''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 [[#Customer|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 [[Week at CNM Cyber]] 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 specification]]s that have been approved for this deliverable. "Rightly" means that the aggregate of creation activities match the agreed [[acceptance criteria]].
| |
| − | | |
| − | : At the ''Cyber'', [[#Contractors|Contractors]] create [[#Project deliverables|Project deliverables]]. To coordinate the deliverable creation, the responsible ''Coord'':
| |
| − | :# '''Initiates''' hiring of development contractors.
| |
| − | :# '''Plays''' roles of the [[product owner]] and/or [[project owner]] in the absence of other members of the [[#Team|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 Repo]] for work on the deliverable in addition to the project wikipage on [[CNM Wiki]].
| |
| − | :# '''Invites''' the hired contractor to the project space.
| |
| − | :# '''Reports''' to the [[#Customer|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 the [[#Customer|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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] meetings.
| |
| − | | |
| − | : The deliverable creation opens when the [[#Customer|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'':
| |
| − | :# '''Clarifies''' with [[CNM Cyber Project Manager]]s which members of the [[#Team|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 Repo]], (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 Repo]], (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 Repo]]. 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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] 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===
| + | register, wiki |
| − | : 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.
| |
| − | :# '''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.
| |
| − | :# '''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 the [[#Customer|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 [[CNM Cloud Usable]] wikipage.
| |
| − | :# '''Presents''' the progress, plans and possible concerns during [[Week at CNM Cyber]] meetings.
| |
| | | | |
| − | : Product management opens when the product is put into service and ends when the product gets retired. | + | ===Tools=== |
| | + | :* [[Inplz Page]]; every learner shall have their [[Educaship WordPress]] instance to play with. At the same time, we will need to clarify the [[website builder]] to include into [[Educaship WordPress]]. We are also looking at [[WordPress Gutenberg]]. |
| | + | :* [[CNM Lab]] is a file repository within [[Opplet]]. |
| | + | :* [[CNM Corp]] includes a tool that the ''Devs'' shall use in order to report their time spent on the ''Practice''. |
| | + | :* [[CNM Wiki]] is the primary tool for website projects generally and development of website ideas, contents, and wiki-based prototypes specifically. |
| | + | :* One more [[COTS]] package shall be added for cnmcyber.com landing. Our production instance of [[Educaship WordPress]] would be [[CNM Page]], but we need to use something simpler for the landing at cnmcyber.com. We look at [[Ghost]], which is written with [[NodeJS]], and, possibly, [[Grav]], which is really lightweight. |
| | | | |
| − | ==Cyber products== | + | ===What Devs produce=== |
| − | For the purposes of this very wikipage, ''Cyber products'' refer to the products that are components of the ''Cyber''. They are belong to one of sub-categories of the [[:Category:CNM Cyber products|"CNM Cyber products" category]].
| + | : Most importantly, the ''Devs'' are expected to achieve their [[#Career objectives|Career objectives]] and acquire other personal benefits as their result of the ''Practice''. As a part of [[CNMCyber Team]], the ''Devs'' are expected to produce measurable outputs in two categories, website deliverables and work documents: |
| | + | :# '''[[#Website deliverables|Website deliverables]]''', which are those [[CNMCyber website]]s, their components, and other [[CNMCyber product]]s that the ''Devs'' are able to produce. [[CNMCyber Coordinator]]s will further utilize to develop the very [[CNMCyber website]]s that the particular ''Dev'' practices with. |
| | + | :# '''[[#Work documents|Work documents]]''', which are those documents that support website developments. Particularly, they include those requirements that would allow hiring [[Careerprise contractor]]s to develop those [[CNMCyber website]]s that the ''Devs'' don't produce directly, on their own. |
| | | | |
| − | ===Categories of products===
| + | : In other words, there are no expectations of the ''Dev's'' achievements of their own [[#Career objectives|Career objectives]]. [[CNMCyber Team]] expects the ''Devs'' to deliver either (a) website components or (b) the documents that would allow those components to produce. The ''Devs'' stop practicing with [[CNMCyber website]]s and work documents after their delivery. [[CNMCyber Coordinator]]s further take over their development. |
| − | : At [[CNM Wiki]], wikipages of ''Cyber'' products belong to several categories. | |
| − | :{|class="wikitable" width=100%
| |
| − | !Category!!This wikipage section
| |
| − | |-
| |
| − | |[[:Category:CNM COTS products|CNM COTS products (category)]]||[[#COTS software|COTS software (wikipage section)]]
| |
| − | |-
| |
| − | |[[:Category:CNM Cloud products|CNM Cloud products (category)]]||[[#Software systems|Software systems (wikipage section)]]
| |
| − | |-
| |
| − | |[[:Category:Careerprise marketables|Careerprise marketables (category)]]||[[#Marketables|Marketables (wikipage section)]]
| |
| − | |-
| |
| − | |[[:Category:CNM customer products|CNM customer products (category)]]||[[#Customer-oriented|Customer-oriented (wikipage section)]]
| |
| − | |-
| |
| − | |[[:Category:CNM corporate products|CNM corporate products (category)]]||[[#Corporate-oriented|Corporate-oriented (wikipage section)]]
| |
| − | |}
| |
| | | | |
| − | : 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. | + | : In addition, the ''Devs'' may be offered to develop [[CNMCyber product]]s other than [[CNMCyber website]]s. For instance, development of this very wikipage is also a project that the ''Dev'' may take on. However, the main focus is on producing deliverables and work documents for [[CNMCyber websites]]. |
| | | | |
| − | : Moreover, a few intermediate products belong to all of the categories and can be considered as [[#Universal|Universal]].
| + | ==Work documents== |
| | + | Generally speaking, a [[document]] is a separate piece that (a) presents data, (b) is composed of texts and/or images, and (c) can further be edited or revised. A document that can no longer be revised, for instance, a transcript of a meeting that has already ended or a [[statement of work]] that a contractor has already agreed on, becomes a [[record]]. |
| | | | |
| − | ===Corporate-oriented===
| + | For the purposes of this wikipage, ''work documents'' shall refer to those documents which target the general public regardless of whether those documents are available to the public or not. |
| − | : For the purposes of this very wikipage, ''corporate-oriented products'' refer to those ''Cyber'' products that serve the enterprise rather than its customers directly. Basically, the talk is about ''Cyber'' administration that covers personnel, legal, financial and organizational issues. Those products are listed in the [[:Category:CNM corporate products|"CNM corporate products" category]] and may include:
| |
| − | :* '''Administrative procedures''' for personnel, financial, accounting and legal operations of the organizational structure behind the ''Cloud''.
| |
| − | :* '''Corporate events''', in which real people participate physically or remotely, such as interviews of candidates for contractors, meetings of professionals and conferences for potential participants. A separate section of this wikipage, [[#Meetings|Meetings]], is dedicated to them.
| |
| − | :* '''Partnerships''', which are contractual agreements to mutually develop and market offers. Historically, the [[#Team|Team]] partnered with two Microsoft stores, in Pentagon City Mall and Tysons Corner Center, several employers, training providers, governmental, and non-profit organizations.
| |
| − | :* '''Positions''', which are documented workplaces of associates included in the organizational structure. This very wikipage is the development of one of ''Cyber'' positions. Moreover, the ''Coords'' are welcomed to own their role, which assumes both (a) developing and updating general instructions, policies, and/or recommendations for the ''Coords'' and (b) contributing to and grooming of the backlog of the ''Coord's'' tasks at the [[CNM Cloud Usable]] and related wikipages.
| |
| − | :* '''Relationships''' with potential and existing clients such as exhibitors, contractors and partners. Stakeholders are involved in communications through (a) hiring contractors to turn those descriptions that the [[#Customer|Customer]] approved into the [[#Cyber products|Cyber products]], (b) hiring employees for developed positions, (c) participation of potential ''Cyber'' participants in events organized by the project.
| |
| − | :* '''Structures''' such as an [[organizational structure]] to organize the work of [[#Team|Team]]; their rights and duties are determined by positions.
| |
| | | | |
| − | ===Customer-oriented===
| + | The work documents are or might be utilized by one or more of the following audiences: |
| − | : For the purposes of this very wikipage, ''customer-oriented products'' refer to those ''Cyber'' products that are designed to serve the customers, but not marketed separately. At the ''Cyber'', any [[#Marketables|Marketable]] is a package of "customer-oriented products". Those products are listed in the [[:Category:CNM customer products|"CNM customer products" category]] and may include:
| + | # A particular ''Dev'' who practices with a particular [[CNMCyber website]] shall use the work documents for the development process and reports. |
| − | :* '''Content''', such as texts, illustrations and multimedia materials that can be used in [[CNM app]]s.
| + | # ''Dev's'' mentors shall use the work documents to assess the ''Dev's'' progress and his or her readiness to move further. |
| − | :* '''Customer support''' for end-users, potential participants and partners of the ''Cyber''.
| + | # The other ''Devs'', who will work on other websites in the future, may further utilize it in their ''Practice'' as prototypes and training materials. |
| − | :* '''[[End-user application]]s''' known as [[CNM app]]s that can be used by current and potential students, apprentices and employees of the ''Cyber''.
| + | # [[CNMCyber Coordinator]]s shall use some work documents to hire [[Careerprise contractor]]s in order to develop what the ''Devs'' are not able to develop on their own. |
| − | :* '''Information resources''' for attracting potential partners and clients of the ''Cyber'', such as websites, social media materials, and mailing lists, as well as standard messages, invitations and advertisements.
| |
| | | | |
| − | : Obviously, there are some interconnections between products areas. For instance, any [[CNM app]] needs its content and so on. At the ''Cyber'', [[#Software products|Software products]] are not considered as ''customer-oriented products'' since the ''Cyber'' doesn't offer software on the market.
| + | In addition, the ''Devs'' may practice with those public documents such as website texts that belong to the [[#Public contents|Public contents]]. As [[work product]]s of the ''Devs'', documents shall be published at [[CNM Wiki]]. |
| | | | |
| − | ===Personnel development=== | + | ===Product wikipages=== |
| − | :In terms of the development of human resources, the results of the work of the ''Coord'' can be: | + | : For the purposes of this very wikipage, ''product wikipages'' refer to descriptions of [[CNMCyber website]]s, as well as deliverable requirements, organizational and technical documentation such as [[standing operating procedure]]s ([[SOP]]s), minutes of the meetings, testing and other reports, etc. Those pages are listed at the [[:Category:CNMCyber Websites|"CNMCyber Websites" category]] |
| − | :# Sourcing and orientation 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]], [[TikTok]], 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. That includes facilitating of training and participating in mentor-[[protégé]] arrangements.
| |
| | | | |
| − | ===Software systems=== | + | ===Project wikipages=== |
| − | : For the purposes of this very wikipage, ''software systems'' refer to those ''Cyber products'' that are assembled of two or more specially-written and/or [[commercial off-the-shelf]] ([[commercial off-the-shelf|COTS]]) software packages. At [[CNM Wiki]], they are listed in the [[:Category:CNM Cloud products|"CNM Cloud products" category]] and may include the following [[information technology]]: | + | : At [[CNM Wiki]], [[#Projects|Projects]] are documented using two types of wikipages: |
| − | :* [[CNM Farms]], including tools for their [[high availability]] and recovery.
| + | :# The progress on particular projects is reported on the [[CNM Website Projects]] wikipage. |
| − | :* [[Opplet]] that serves both end-user applications called [[CNM app]]s and end-users directly.
| + | :# Project pages document everything, but progress reports. Those pages are listed at the [[:Category:CNM Website Projects|"CNM Website Projects" 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]], as well as those communications, memos, meetings, etc. that are related to developments of [[CNMCyber website]]s. |
| − | :* [[CNM app]]s as software. Some application developments concern only their software, some - only the content used in the provision of services, some developments combine both.
| |
| | | | |
| − | ===Universal=== | + | ==Website deliverables== |
| − | : For the purposes of this very wikipage, ''universal products'' refer to those ''Cyber'' products that belong to all of the product categories. They include:
| + | For the purposes of this wikipage, ''website deliverables'' refer to those [[work product]]s that the ''Devs'' deliver to [[CNMCyber Team]] for further use as cores of [[CNMCyber website]]s, their components, or new features of existing websites. |
| − | :* '''Labor resources'''. All products require someone's work on them. Thus, sourcing, selecting, onboarding, and development of labor resources belong to every of the categories. On this very wikipage, the [[#Personnel development|Personnel development]] section reflects those products. All in all, development of human resources generally and the ''Coords'' particularly is the primary of [[#Cyber objectives|Cyber objectives]].
| |
| − | :* '''Testing''' of [[project input]]s and [[deliverable]]s under development. At the ''Cyber'', those projects that are undertaken in order to obtain testing results only are rare. The ''Coords'' execute the overwhelming majority of testing while obtaining other deliverables or simply utilizing existing ''Cyber'' products such as this very wikipage.
| |
| − | :* '''[[#What Coords produce|What the Coords produce]]''' such as [[#Meetings|Meetings]], [[#Documents|Documents]], [[#Records|Records]], and [[#Communications|Communications]] to facilitate development and management of ''Cyber'' products. ''Cyber'' products are outcomes rather than outputs of the ''Coords<nowiki>'</nowiki> work.
| |
| | | | |
| − | ==Marketables==
| + | The ''Devs'' shall aim to create one or more of the following website deliverables: (a) [[#Public contents|Public contents]], (b) [[#SEO efforts|SEO efforts]], (c) [[#Website designs|Website designs]], (d) [[#WWW settings|WWW settings]], and, finally, (e) [[#System-based websites|System-based websites]]. |
| − | For the purposes of this very wikipage, [[marketable]]s refer to those products that [[The Economic Group]] offers to the general public and positions on the market. All of ''Cyber'' marketables are largely undeveloped yet; that is why the ''Coords'' are urgently needed.
| |
| | | | |
| − | At the ''Cyber'', its marketables are called "Careerprise marketables", assembled from [[#Customer-oriented|Customer-oriented]] products, and listed in the [[:Category:Careerprise marketables|"Careerprise marketables" category]].
| + | ===Public contents=== |
| | + | : For the purposes of this wikipage, ''public contents'' refer to those audiovisuals, graphics, and texts that the website visitors shall be able to read, see, and/or hear. As [[work product]]s of the ''Devs'', texts shall be published at [[CNM Wiki]], while audiovisuals and graphics shall be stored at [[CNM Lab]]. |
| | | | |
| − | ===Career services=== | + | ===SEO efforts=== |
| − | : Those [[career service]]s that [[The Economic Group]] offers to the general public and positions on the market include: | + | : For the purposes of this wikipage, ''SEO efforts'' refer to those action plans that shall improve website's [[search engine optimization]] ([[search engine optimization|SEO]]). As [[work product]]s of the ''Devs'', action plans shall be published at [[CNM Wiki]]. |
| − | :* '''[[Careerprise support]]'''. A buffet-style range of career services delivered by specialists and experts such as resume writing, public relations management, job search assistance, [[talent representation]], [[mentorship]] or support of [[mentor]]s, as well as vocational guidance and training.
| |
| − | :* '''[[CITPMA|Certified IT Project Management Associate]]''' ([[CITPMA]]) certification is designed to assess competencies in basic [[information technology]], [[project management]], and [[soft skill]]s. The ''Coords'' are certified upon successful graduation automatically.
| |
| − | :* '''[[CNM Cyber]]''' (as web-based resources). The ''Cyber'' is a web platform for those who are on the job market, going to be there, or wish to be there. Its end-user computer-led resources encompass [[CNM app]]s, [[Kryvi app]]s, and [[Inplz app]]s. The general public can find here career-oriented courses, hands-on training facilities, information banks, as well as access to human-led [[Careerprise support]], [[#Introductory jobs|Introductory jobs]], [[#Professional networks|Professional networks]], and [[#Public events|Public events]]. As a workspace, the ''Cyber'' is capable to accommodate internships for partners' interns, practical experience for the ''Coords'', and apprenticeships for graduates from the ''Coord'' position.
| |
| − | :* '''[[iDosvid]]'''. The version of the ''Cyber'' that is oriented on middle- and high-school students.
| |
| − | :* '''[[WorldOpp Pipeline]]'''. The aggregate of all career services of [[The Economic Group]].
| |
| | | | |
| − | ===Introductory jobs=== | + | ===System-based websites=== |
| − | : ''Introductory jobs'' is the signature offer of [[The Economic Group]] on the workforce market. This component makes its [[#Career services|Career services]] unique; this is also the "heart" of [[WorldOpp Pipeline]]. ''Introductory'' means that those jobs come with complete preparation for them. Anyone can possibly start from scratch and land the pre-entry-level position, the ''Coord'', in order to gain work experience, get introduced to various professions, and pick up the one to pursue further. | + | : For the purposes of this wikipage, ''system-based websites'' refer to those [[website]]s that are powered by one or more [[content management system]]s ([[content management system|CMS]]s). The websites may represent [[prototype]]s, [[minimal viable product]]s ([[minimal viable product|MVP]]s), or parts of [[Careerprise Funnel]]. As [[work product]]s of the ''Devs'', websites shall be hosted at [[Opplet]]. |
| | | | |
| − | : On its platform, the ''Cyber'' offers a few professional positions to [[CITPMA|Certified IT Project Management Associate]]s ([[CITPMA]]s) and/or the ''Coord'' graduates. These positions are: | + | ===Website designs=== |
| − | :* '''[[CNM Cyber Project Manager]]s''' are responsible for resolving administrative, personnel, financial, legal and organizational issues. In particular, the executive officer assigns projects to the Coordinators, places advertisements for hiring contractors, gives the coordinators recruiter access and pays the project budgets. The executive director can be called a "super-coordinator". If the ''Coords'' work on one endeavor, which they choose on their own, the executive is responsible for the entire group of developments and operations, including finance, personnel, administration of the ''Coords'', and so on. At the moment, the [[#Customer|Customer]] plays the role of ''Cyber'' executive, but he does it temporarily, until such a person or people are found.
| + | : For the purposes of this wikipage, ''website designs'' refer to those depictions that represent current or future website's appearance, including single [[webpage]]s and [[website IA]]s overall. As [[work product]]s of the ''Devs'', final depictions shall be stored at [[CNM Lab]]; their thumbs and sketches may emerge at [[CNM Wiki]]. |
| − | :* '''[[CNM Cyber Recruiter]]s''' ensure that the recruiting process is in place, there are candidates for Coords and, with the approval of the [[#Customer|Customer]], for other full-time positions in the recruiting "pipeline", and also advise on those developments that relate to recruiting. In their projects, the ''Coords'' also play the role of recruiters and take over the hiring of contractors. Unlike recruiters, the ''Coords'' discuss requirements and other [[project document]]s with candidates. The ''Coords'' turn to recruiters in cases where their own competencies or resources are not enough to attract contractors.
| |
| − | :* '''[[CNM Cyber Security Analyst]]s''' monitor, analyze, and revise security of the ''Cyber'' and adequacy of its security policies.
| |
| − | :* '''[[CNM System Administrator]]s''' ensure the stability of the ''Cloud's'' operations and advise on technological developments.
| |
| − | :* '''[[CNM Systems Engineer]]s''' design new [[#Software systems|Software systems]] and revise the existing ones.
| |
| − | :* '''[[CNM Web Developer]]s''' develop [[website]]s of the ''Cyber''.
| |
| | | | |
| − | : Those jobs come with vocational guidance, training, support of [[mentor]]s, and other [[Careerprise service]]s, as well as the ''Cyber'' workspace. The workspace comes with administrative procedures for hiring and retaining of its workforce, end-user applications for person's work, as well as personnel meetings, marketing campaigns to attract candidates, and so on.
| + | ===WWW settings=== |
| − | | + | : For the purposes of this wikipage, ''WWW settings'' refer to those scripts of [[DNS record]], lines of [[web server]] files, and hosting details that are necessary for the website to be accessible on the [[World Wide Web]] ([[World Wide Web|WWW]]). As [[work product]]s of the ''Devs'', scripts, lines, and details shall be published at [[CNM Wiki]]. |
| − | : More positions are available through ''Cyber'' partners. [[The Economic Group]] is constantly looking for new opportunities for ''Cyber'' customers.
| |
| − | | |
| − | ===Partnerships===
| |
| − | : The [[#Team|Team]] produces itself just three [[marketable]]s, which are (a) [[CITPMA|Certified IT Project Management Associate]] ([[CITPMA]]) certification, (b) [[CNM Cyber]] (as web-based resources), and (c) the first three stages of [[WorldOpp Pipeline]]. However, it markets not only services that it produces.
| |
| − | | |
| − | : All the other services are produced by ''Cyber'' partners. To source, select, contract, onboard, and retain partners, the [[#Team|Team]] must offer partnerships on the market. There are three basic patterns of partnerships:
| |
| − | :# ''Cyber'' partners offer the [[Category:Careerprise marketables|''Cyber'' marketables]] to their customers.
| |
| − | :# The [[#Team|Team]] offers partner's marketables to its customers.
| |
| − | :# ''Cyber'' partners and the [[#Team|Team]] together develop new marketables.
| |
| − | | |
| − | : The [[#Team|Team]] assembles partners' marketables and, altogether with its own ones, positions and promotes them on the market.
| |
| − | | |
| − | ===Professional networks=== | |
| − | : Human connections is the key to many jobs; that is why the [[#Team|Team]] is building its professional networks including: | |
| − | :* '''[[CNM industry councils]]'''. Groups of professionals who work in the industries related to the ''Cyber''.
| |
| − | :* '''[[CNM professional committees]]'''. Groups of professionals who work in the positions related to the ''Cyber''.
| |
| − | :* '''[[CNM User Group]]'''. The group of [[end-user]]s of the ''Cyber'' to discuss its challenges and possible solutions.
| |
| − | :* '''[[Society of Sysadmins]]'''. The group of [[system administrator]]s that is supported by the ''Cyber''.
| |
| − | | |
| − | ===Public events===
| |
| − | : The [[#Team|Team]] organizes [[CNM Cyber event]]s in order to position the ''Cyber'' on the market and to:
| |
| − | :# Attract prospective contractors, customers, and partners. Those outreach events are marketing efforts to reach out to current and potential customers on the labor market and business services market in order to gain their attention, build their interest, arise their desire to utilize ''Cyber'' opportunities and not the products of the competitors, as well as to motivate them to act in that direction.
| |
| − | :# Generate revenues. Some events come in the [[freemium]] mode; basic events are free-of-charge; however, some extras might be paid.
| |
| − | | |
| − | : Those events are combined in series such as:
| |
| − | :* '''[[Week at CNM Cyber]]'''. The series of free-of-charge events that the ''Coords'' organize to exchange ideas, to present new developments and plans, as well as to market their work.
| |
| − | :* '''[[CNM Cyber Guided Tours]]'''. The series of freemium-mode events that are organized to present technologies of the ''Cyber''. The basic attendance is free-of-charge; hands-on access to the technologies and/or one-on-one consultations are paid.
| |
| − | | |
| − | : More public meetings, in which real people participate physically or remotely, may be organized by the [[#Professional networks|Professional networks]].
| |
| − | | |
| − | ==Market presence==
| |
| − | For the purposes of this very wikipage, [[market presence]] refers to the [[#Team|Team]]'s efforts to present its [[#Marketables|Marketables]] on the markets, so their current and potential customers can find and take advantage of them. While accomplishing that goal, the ''Coords'' may work on a variety of marketing products generally or marketing communications specifically. | |
| − | | |
| − | ===Communications to build===
| |
| − | : The [[#Team|Team]] shall create a variety of communications in order to reach out to prospective ''Coords'', contractors, partners, supporters, as well as paying customers. [[Customer relationship management]] (or [[Customer relationship management|CRM]]) is an important part of these efforts. While documenting their efforts in [[customer relationship management system]]s (or [[Customer relationship management system|CRMS]]), the ''Coords'' may coordinate endeavors to produce marketing communications as follows:
| |
| − | :* '''[[Customer support]]''' is a contact person or people who assist customers in installing, upgrading, maintaining, using, and/or disposing a product correctly and cost effectively. In the case of the ''Cyber'', its ''customer support'' shall yet be designed.
| |
| − | :* '''[[Help desk]]''' is a contact person or people who provide the customers with technical assistance and troubleshooting. In the case of the ''Cyber'', its ''help desk'' shall yet be designed.
| |
| − | :* '''[[Marketing outlet]]s''', in the case of the ''Cyber'', are efforts to establish points of [[#Team|Team]]'s direct contact with prospective contractors, customers, partners, and supporters. ''Cyber's'' booth at a job fair or table at the [[marketplace]]s would be an example of physical point of contact. ''Marketplaces'' refer to virtual and physical locations where sellers and buyers regularly gather to buy and sell products. Virtual points of contact may include (a) corporate profiles at web-based marketplaces, including [[freelance marketplace]]s such as [[Fiverr]] and [[Upwork]], (b) corporate channels at [[videosharing platform]]s such as [[TikTok]] and [[YouTube]], (c) corporate pages or groups at [[social networking platform]]s such as [[Facebook]], [[LinkedIn]], [[Meetup]], and [[Twitter]], and (d) other direct marketing opportunities given by third parties. For example, some [[job-search website]]s feature free announcements; the [[#Team|Team]], particularly, used [[robota.ua]] and [[work.ua]] to look for potential ''Coords'' in Ukraine. As another example, the [[#Team|Team]] once considered publishing its courses at [[learning platform]]s such as [[Udemy]].
| |
| − | :* '''[[Public relations]]''' ([[Public relations|PR]]), in the case of the ''Cyber'', is efforts to transfer marketing messages from the [[#Team|Team]] to mass media and/or the general public directly. While [[publicity]] is controlled by external media, the [[#Team|Team]] controls ''PR''.
| |
| − | :* '''[[Stakeholder communications]]''', in the case of the ''Cyber'', are efforts to transfer marketing messages such as [[newsletters]] from the [[#Team|Team]] to those who are listed in the [[stakeholder register]] directly.
| |
| − | :* '''[[UX design]]''' is efforts to enhance user satisfaction with marketables by improving their accessibility, credibility, desirability, findability, usability, usefulness, and value. Any product implies some unspoken and unwritten messages; ''Cyber'' products are not exceptions. Good marketing of bad products just increase user dissatisfaction. That is why the ''Coords'' are encouraged to take into consideration [[user experience design]] while working on ''Cyber'' products.
| |
| − | :* '''[[#Websites|Websites]]''', in the case of the ''Cyber'', are composed of [[lead-generation websection|lead-generation]], [[prospect-education websection|prospect-education]], and [[deal-closing websection]]s. A special section of this very wikipage, [[#Websites|Websites]], is dedicated to them.
| |
| − | | |
| − | ===Communications to buy===
| |
| − | : The [[#Team|Team]] may purchase a variety of communications in order to reach out to prospective ''Coords'', contractors, partners, as well as paying customers. The ''Coords'' may coordinate endeavors to buy marketing communications as follows:
| |
| − | :* '''[[Advertising]]''', in the case of the ''Cyber'', is buying media's delivery of marketing messages to potential contractors, customers, partners, and supporters. The world's oldest forms of advertising are, probably, vocal announcements and distribution of samples, especially, in public spaces. Published advertising is either posting messages on something like walls or billboards that people can physically see or distributing something like leaflets hand-to-hand. Radio and television are considered as traditional electronic media; while mobile and web are new ones. The [[#Team|Team]], for examples, may purchase advertising to support its activities at [[marketplace]]s and [[social media]]. Often, but not necessarily, ''advertising'' also entails creation of marketing messages. If so, their ownership depends on agreements.
| |
| − | :* '''[[Personal selling]]''' (outsourced), in the case of the ''Cyber'', is hiring agents, brokers, and/or sales representatives to promote one or more ''Cyber'' products to their potential customers on a one-to-one basis. Obviously, ''personal selling'' is the most expensive form of marketing communications. That is why the [[#Team|Team]] tends to hire those on a [[contingency model]] rather than [[retained model|to retain]] them (see the [[#Payment models|"Payment models"]] section of this very wikipage).
| |
| − | | |
| − | : Communications for sale tend to be less trusted than unpaid ones. Furthermore, ''advertising'' is usually less trustworthy than ''personal selling'', however, trustworthiness of ''personal selling'' heavily depends on seller's features and capacities.
| |
| − | | |
| − | ===Communications to earn===
| |
| − | : The [[#Team|Team]] may attempt to earn a variety of communications in order to reach out to prospective ''Coords'', contractors, partners, as well as paying customers. The ''Coords'' may coordinate endeavors to earn marketing communications as follows:
| |
| − | :* '''[[Publicity]]''', in the case of the ''Cyber'', is efforts to support mass and other media to cover the ''Cyber'' and/or its products on a non-monetary basis. After those efforts, the [[#Team|Team]] no longer controls its content. For instance, a television report may theoretically promote the ''Cyber'' without paying for that; however, the [[#Team|Team]] cannot dictate the TV producer what this report should look like. [[Social media]]
| |
| − | :* '''[[Word of mouth]]''' is the transfer of messages from person to person using oral communication. When they say, "a good product sells itself", they probably mean that good products shall generate words of mouth in sufficient amounts. This form of communications is the most effective when the listener trusts the messenger, for instance, a relative or friend. Obviously, the [[#Team|Team]] cannot produce those messages directly; they can be caused by other types of communications, [[#Public events|Public events]], and, especially, ''Cyber'' products when their users like them. At the same time, the ''Coords'' are encouraged to take into consideration possibilities of ''word of mouth'' generation while working on marketing products.
| |
| − | | |
| − | : Earned-media messages tend to be more trusted than, let say, paid-media ones. However, earned-media messages are pretty much always distorted since they pass one or more intermediaries.
| |
| − | | |
| − | ==The funnel==
| |
| − | On one hand, marketing products are not equal. On another hand, ''Cyber'' consumers shall go through several stages from "barely aware" to, in the best case, "highly loyal". The [[marketing funnel]] concept is deployed to map out the journey consumers undertake while making purchases, re-purchases, and/or advocating actions from the marketer's perspective. This concept utilizes a funnel as an analogy because the number of "barely aware" consumers is much larger than "highly loyal" ones.
| |
| − | | |
| − | A [[purchase funnel]] is the ''marketing funnel'' that is viewed from the buyer's perspective. A [[sales funnel]] represents the portion of the ''marketing funnel'' that describes a sales stages. It has three clearly-distinctive conversion points: (a) a visitor to a lead, (b) the lead to an educated prospect, and (c) the educated prospect to a customer.
| |
| − | | |
| − | The funnels need to be taken into consideration in building [[#Marketables|Marketables]] such as [[#Website developments|Website developments]] and their marketing campaigns. The ''Coords'' are encouraged to be aware of the various levels of the funnel and marketing products that are utilized at those levels.
| |
| − | | |
| − | ===Top of the funnel===
| |
| − | : The top of the funnel, which is also known as [[ToFu]], refers to lead generation, which aims to convert an unaware to a lead. That ''unaware'' is someone who is unaware of a product; that ''lead'' is someone who is interested in that product enough to act in order to learn about it. Two levels can be distinguished at ''ToFU'':
| |
| − | :# '''Attract attention''' of potential consumers or, in other words, move an unaware to a visitor. At this level, potential consumers haven't got to ''Cyber'' websites yet, but those consumers shall get either (a) their domain names through marketing products like [[advertising]], [[marketing outlet]]s, [[public relations]] ([[public relations|PR]]), [[publicity]], and [[word of mouth]] or links to the websites via [[search engine optimization]] ([[SEO]]) or other online resources.
| |
| − | :# '''Build awareness''' and prompt consumers' discovery or, in other words, move a visitor to a lead. At this level, potential consumers have got to ''Cyber'' websites, probably, to their [[lead-generation websection]]s.
| |
| − | | |
| − | : In the case of the ''Cyber'', ''lead-generation websections'' are expected to attract consumers' attention in order to generate traffic to ''Cyber's'' [[prospect-education websection]]s. Every ''Cyber'' website has some ''lead-generation websections''. At the ''Cyber'', [[Bskol.com]], [[FriendsOfCNM.com]], [[HOTCOE.com]], [[Inplz.com]], and [[Kryvi.com]] websites are fully dedicated to lead generation.
| |
| − | | |
| − | ===Middle of the funnel===
| |
| − | : The middle of the funnel, which is also known as [[MoFu]], refers to prospect education, which aims to convert a lead to a prospect. That ''prospect'' is someone who has started product's purchase process. Two levels can be distinguished at ''MoFU'':<ol start="3"><li>'''Present deals''' to potential consumers to prompt their consideration or, in other words, move a lead to an educated lead.</li><li>'''Address doubts''' to eliminate potential consumers' objections to their purchase or, in other words, move an educated lead to a prospect.</li></ol>
| |
| − | | |
| − | : At those levels, potential consumers have got to [[prospect-education websection]]s of ''Cyber'' websites. Other marketing products that can be helpful at ''MoFU'' include [[personal selling]] and educational resources of the ''Cyber'' such as [[CNM Cyber Welcome Session]].
| |
| − | | |
| − | : In the case of the ''Cyber'', ''prospect-education websections'' are expected to prompt consumers' purchase consideration in order to generate traffic to ''Cyber's'' [[deal-closing websection]]s. At the ''Cyber'', [[CITPMA.com]], [[CNMCyber.com]], and [[iDosvid.com]] websites feature ''prospect-education websections''. They also feature lead generation; in addition, [[CNMCyber.com]] provides its customers with services at the [[#Bottom of the funnel|Bottom of the funnel]].
| |
| − | | |
| − | ===Bottom of the funnel===
| |
| − | : The bottom of the funnel, which is also known as [[BoFu]], refers to customer acquisition, adoption, and engagement which aim to convert a prospect to a customer. That ''customer'' is someone who has purchased at least once at least one ''Cyber'' product and, preferably, is loyal to it and advocating in its behalf. Three levels can be distinguished at ''BoFU'':<ol start="5"><li>'''Close deals''' to finalize purchases; [[deal-closing websection]]s and [[personal selling]] may be especially helpful in deal closing. In the case of the ''Cyber'', ''deal-closing websections'' are those [[websection box]]es of [[CNMCyber.com]] that are expected to prompt prospects' purchase.</li><li>'''Support acquisitions''' of customers to build loyalty; [[customer support]], [[help desk]], and [[UX design]] may be especially helpful in retention.</li><li>'''Engage customers''' to build their advocacy; [[stakeholder communications]] may be especially helpful in engaging.</li></ol>
| |
| | | | |
| | ==Projects== | | ==Projects== |
| − | Generally speaking, a [[project]] is a development [[#Endeavors|Endeavor]] or a set of [[enterprise effort]]s undertaken to produce a unique [[deliverable]], functional features of which are identified or can be identified before the ''efforts'' start. Those deliverables are those new and modified products that are produced during those developments. Indeed, the aim of ''Cyber's'' developments is to produce new or modify existing [[#Cyber products|Cyber products]]. At the ''Cyber'', former and current projects are listed in the [[:Category:CNM Cyber endeavors|"CNM Cyber endeavors" category]]. | + | Generally, a [[project]] is a temporary endeavor undertaken to create a unique [[work product]]. They aim to solve a problem and the resulting output. The ''work product'' that is created to deliver to its customer is called a [[deliverable]]. |
| − | | |
| − | ===Cycles of cycles===
| |
| − | : To coordinate endeavors, the ''Coords'' shall accomplish cycles of efforts that consists of several steps. Similar procedures are normally needed to produce [[project scrap]]s and by-products. That means that the ''Coords'' are expected to follow the same cycle to create [[#What Coords produce|What Coords produce]].
| |
| − | | |
| − | : Furthermore, the most of projects may be viewed as sets of smaller developments. Among the ''Coords<nowiki>'</nowiki>'' outputs, [[#Meetings|Meetings]], [[#Documents|Documents]], and [[#Communications|Communications]] usually belong to [[project scrap]]s. Indeed, [[#Project results|Project results]] and results of the ''Coords<nowiki>'</nowiki>'' work are different phenomena.
| |
| − | | |
| − | : Project deliverables normally utilize outputs from other projects as its scrap. A [[CNM app]] development, for example, requires documents that describe its requirements, and drawing up those requirements requires meeting events. If we consider the ''Coords<nowiki>'</nowiki>'' work as micro-projects, we can say that outputs of micro-projects tend to become scraps for small projects and, furthermore, outputs of small projects tend to become scraps for macro-projects.
| |
| − | | |
| − | ===Deliverables vs by-products===
| |
| − | : Those [[project output]]s that are not [[#Project deliverables|Project deliverables]] may be called project by-products. Their range is huge; there are some imaginary scenarios:
| |
| − | :* A contractor submitted more products than the contract had required. If they are further deployed, those additional products would be by-products of this project.
| |
| − | :* Contractor's performance demonstrated advanced competencies in something unrelated to the project. The updated records are by-products of this project.
| |
| − | :* While organizing a meeting, the ''Coord'' encountered the problem of the policy's incompleteness. The project customer agreed to fund the policy's updates. The updated policy is a by-product of the project
| |
| − | | |
| − | ===Durations===
| |
| − | : The ''Coords'' work on one project, usually up to three and, in exceptional cases, up to five weeks.
| |
| − | :# In the first week, they shall get familiarized with the project. At the end of the familiarization, the ''Coord'' should be able to explain what is described on the relevant wikipages and be ready to discuss its [[Sprint Zero]] with the [[#Customer|Customer]].
| |
| − | :# From the second week to the penultimate week, they facilitate the project work in accordance with the [[#What Coords do|What Coords do]] section.
| |
| − | :# In the final week, they close the project or project part, documenting their work and the data that was uncovered during that work.
| |
| − | : Projects can overlap. For example, the last week of work on one project may be the first week of work on another project. For senior ''Coords'', there are no restrictions.
| |
| − | | |
| − | ===Patterns===
| |
| − | : Although no single straightforward pattern of project advancement exists, some patterns can be found in various developments. As an example, letters in the [[DREPD]] pattern represent five phrases:
| |
| − | :# '''D''' for "discover the need".
| |
| − | :# '''R''' for "research the background".
| |
| − | :# '''E''' for "envision the deliverable".
| |
| − | :# '''P''' for "plan the production".
| |
| − | :# '''D''' for "do what is planned and discover what hasn't been expected". This discovery is supposed to start a new cycle; new data shall emerge while doing and/or after getting something done.
| |
| − | | |
| − | : This pattern can be found in the whole development, in every group of processes, every process and every part of processes where ever anything new is or is going to be developed.
| |
| − | | |
| − | ===Project deliverables===
| |
| − | : Projects are undertaken to create project deliverables. Project customers initiate projects in order to get something in return. Normally, customers fund projects because of its expected deliverables. Any project is expected to deliver some outputs. In other words, project deliverables are those products for which development the project exists.
| |
| − | | |
| − | : For instance, when a contractor is hired to produce a particular thing, that very thing should be the deliverable of that project. Literally, the contractor is expected to ''deliver'' the deliverable to complete the project.
| |
| − | | |
| − | : At the ''Cyber'', former, current, and expected deliverables are listed in the [[:Category:CNM Cyber products|"CNM Cyber products" category]]. Project deliverables exist in various [[#Product states|Product states]] and belong to various [[#Product areas|Product areas]]. In addition, one project rarely produces one single deliverable. For instance, the [[HAProxy for CNM Farms]] project is expected to deliver high-availability capabilities for [[CNM Campus Farm]] and [[Campus Farm Lab]], as well as related presentations on various media resources, updates to the [[CNM Cyber Orientation]] course, and a bundle of exercises for the learners.
| |
| − | | |
| − | : Finally, project deliverables and ''Coords<nowiki>'</nowiki>'' deliverables are not the same things. Any development can be represented as [[#Cycles of cycles|Cycles of cycles]]. Just few ''Coords<nowiki>'</nowiki>'' deliverables, for instance, records, become a part of project deliverables. Normally, [[#What Coords produce|the ''Coords'' deliver]] to the project something like [[#Meetings|Meetings]], [[#Documents|Documents]], [[#Records|Records]], and [[#Communications|Communications]] to be consumed in the project activities as [[project scrap]]s.
| |
| − | | |
| − | ===Project results===
| |
| − | : [[Project result]]s or results of the projects may be classified in four levels:
| |
| − | :# '''[[Project scrap]]s''', which are intermediate products that either become parts of the [[#Cyber products|Cyber products]] or have been decommissioned before the end of the project. Nevertheless, the outputs cannot be produced without those scraps. As they say, sausage making is messy, but no sausage can be produced without that mess.
| |
| − | :# '''[[Project output]]s''' are the things that are produced during the project and kept after its end. Besides the [[#Project deliverables|Project deliverables]], the outputs may include other-than-the-project [[#Records|Records]] such as publications and [[#Documents|Documents]] such as blueprints that have been developed and commissioned in order to produce the [[#Project deliverables|Project deliverables]].
| |
| − | :# '''[[Project outcome]]s'''. On the ''Coord's'' side, the outcomes are those [[KSA]]s that the ''Coord'' has obtained during the project coordination. On the other stakeholders' side, the outcomes are something for which the [[#Project deliverables|Project deliverables]] have been produced.
| |
| − | :# '''[[Project impact]]s''', which are consequences of the project, its outputs and outcomes on a society. Beyond the ''Coord's'' work, some projects, for instance, may initiate further meetings, documents, actions, and changes.
| |
| − | | |
| − | ===Status reports===
| |
| − | : While working on the deliverable, the ''Coords'' are expected to report their project status. In [[CNM Agile]] framework, these statuses are reported at the product line wikipage, [[CNM Cloud Usable]], using the following readiness levels for each [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]]:
| |
| − | :* '''[[Not started status|Not started]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] hasn't started yet.
| |
| − | :* '''[[In progress status|In progress]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been started, but the state/device has not yet been submitted for the approval.
| |
| − | :* '''[[Cancel status|Cancel]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been cancelled.
| |
| − | :* '''[[Submitted status|Submitted]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been submitted for the approval.
| |
| − | :* '''[[Done status|Done]]'''. Project work on the corresponding [[#Product states|Product state]] and [[#Devices of certainty|Device of certainty]] has been approved. With exceptions of the [[state of certainty]], the [[#Customer|Customer]] approves the status. With regard to the [[state of certainty]], its approval also requires the developer's consent.
| |
| − | | |
| − | ==Websites==
| |
| − | Generally speaking, a [[website]] is a collections of webpages published on the [[World Wide Web]] ([[World Wide Web|WWW]]), as well as service capacities and resources attached to those pages. ''Cyber'' websites serve marketing purposes; they are important at every level of [[#The funnels|The funnels]], including attracting, educating, closing, retaining, as well as engaging. As work products, ''Cyber'' websites are also vital in ''Cyber'' learner training.
| |
| − | | |
| − | ===Featured===
| |
| − | : At the ''Cyber'', featured websites are those that the [[#Team|Team]] specifically promotes through its [[#Market presence|Market presence]]. Particularly, those websites are promoted at [[marketing outlet]]s, [[public relations]] ([[public relations|PR]]), [[advertising]], and [[personal selling]]. Three featured websites of the ''Cyber'' are:
| |
| − | :* '''[[CITPMA.com]]''', official [[website]] of [[CITPMA]].
| |
| − | :* '''[[CNMCyber.com]]''', official [[website]] of the ''Cyber''.
| |
| − | :* '''[[iDosvid.com]]''', official [[website]] of [[iDosvid]].
| |
| − | | |
| − | ===Traffic-generating===
| |
| − | : At the ''Cyber'', traffic-generating websites are those that the [[#Team|Team]] doesn't promote, but support in order to generate traffic to the [[#Featured|Featured]] websites. Five traffic-generating websites of the ''Cyber'' are:
| |
| − | :* '''[[Bskol.com]]''', where ''[[Bskol]]'' is a brand name of a ''Cyber'' spin-off.
| |
| − | :* '''[[FriendsOfCNM.com]]''', where ''Friends of CNM'' is a former name of the ''Cyber''.
| |
| − | :* '''[[HOTCOE.com]]''', where ''hotcoe'' is a former name of the ''iDosvid''.
| |
| − | :* '''[[Inplz.com]]''', which is a home page of [[Inplz app]]s.
| |
| − | :* '''[[Kryvi.com]]''', which is a home page of [[Kryvi app]]s.
| |
| − | | |
| − | ==Website developments==
| |
| − | For the purposes of this very wikipage, [[website project]]s, ''website developments'', or, simply, ''web devs'' are those [[project]]s that are undertaken to develop ''Cyber'' websites and their components. Website development normally consists of several interrelated projects. New ''Coords'' are expected to take one of them as their first-week-on-the-job assignment at least.
| |
| − | | |
| − | ===Content projects===
| |
| − | : For the purposes of this very wikipage, ''content projects'' refer to the [[website project]]s that are undertaken to develop general public contents of ''Cyber'' websites. General public contents are those audio-visuals, images, multimedia, and texts that the visitors of ''Cyber'' websites shall be able to see or hear when they access the ''Cyber'' webpages.
| |
| − | :# '''Non-textual contents''' such as audiovisuals, images, and multimedia. [[#Contractors|Contractors]] shall be hired to development audio-visuals, images, and/or multimedia. To accomplish so, separate projects shall be formalized. The completed audio-visual, image, and multimedia files shall be stored at [[CNM Repo]]. The other website developments do not necessarily depend on general public contents. Until they or their drafts are developed, [[placeholder]]s shall substitute the future content in other developments.
| |
| − | :# '''Texts'''. ''Cyber'' webpages are literally [[HTML]]-based documents, which means that the webpages are textual documents marked up with [[HTML]] tags in order to embed non-textual contents and make all viewable on the [[World Wide Web]] ([[World Wide Web|WWW]]). Since [[#Documents|Documents]] are regular outputs of ''Coords'' work, the ''Coords'' are encouraged to develop textual contents using [[CNM Wiki]]. The other website developments do not necessarily depend on general public contents. Until they or their drafts are developed, [[lorem ipsum]] shall substitute the future content in other developments.
| |
| − | | |
| − | : Development of ''Cyber'' websites' content, most likely, consumes the most of website development time. Since the websites shall reflect the actual situation, the website content shall be periodically updated even when the website is already up and running.
| |
| − | | |
| − | : The other, not for the general public, contents include key words for [[search engine optimization]] ([[search engine optimization|SEO]]) and other technical texts.
| |
| − | | |
| − | ===Design projects===
| |
| − | : For the purposes of this very wikipage, ''design projects'' refer to the [[website project]]s that are undertaken to develop graphical appearance for ''Cyber'' websites. Creation of certain images or audiovisuals that are used in website contents is a part of the [[#Content projects|Content projects]].
| |
| − | | |
| − | : [[Web design]] is essential for every [[website]] generally and ''Cyber'' website particularly. By its definition, development of ''web design'' is creative; design-developing [[#Contractors|Contractors]] shall be hired on a per-hour basis. At the ''Cyber'', web design projects can be undertaken to develop a single [[webpage section]], especially a main one.
| |
| − | | |
| − | : At the ''Cyber'', designs are divided in [[graphic design]]s and [[UX design]]s. Graphic designers shall normally be hired to achieve webpage esthetics; UX designers shall work on great [[user experience]] with the page. The work outputs of one designer shall be given to another designer until both agree that the [[webpage section]] they work on is both graphically and [[UX]] acceptable.
| |
| − | | |
| − | : Deliverables of ''design projects'' are pixel-sharp [[product depiction]]s of one or more [[webpage section]]s. After the [[#Customer|Customer]]'s approval, they shall be used as inputs to the [[#Website as one product|Website as one product]] developments. In order to store the deliverable files at [[CNM Repo]], the [[#Contractors|Contractors]] who work on the designs need to have proper access.
| |
| − | | |
| − | ===SEO projects===
| |
| − | : For the purposes of this very wikipage, ''SEO projects'' refer to the [[website project]]s that are undertaken to develop and manage [[search engine optimization]] ([[SEO]]) for ''Cyber'' websites. ''Cyber's'' SEO efforts aim to generate traffic of those people who look for apprenticeship, entry-level job, internship, hands-on training, high-school student job, professional orientation, sysadmin job, and other ''Cyber'' services to the ''Cyber'' websites.
| |
| − | | |
| − | : ''SEO'' efforts belong to competitive marketing; various actors on the market try to emerge in search engine results as high as possible. Since [[Google]] search engine is dominant; ''SEO'' can be viewed as competition over Google ratings. ''SEO'' can also be considered as a part of [[information architecture]].
| |
| − | | |
| − | : Results of ''SEO projects'' are published at [[CNM Wiki]]; [[CNM System Administrator]]s use those results to update the actual website protocols.
| |
| − | | |
| − | ===Software projects===
| |
| − | : For the purposes of this very wikipage, ''software projects'' refer to the [[website project]]s that are undertaken to develop software that powers ''Cyber'' websites.
| |
| − | :# '''CMS-based'''. Primarily, this software represents a [[content management system]] (or [[content management system|CMS]]). ''Cyber'' websites normally use [[CNM WordPress]] under their hood. In the past, the [[#Team|Team]] have also used other [[content management system]]s such as [[Drupal]] and [[Joomla]]. If the need emerges, some considerations can also be given to [[Ghost]], [[Grav]], and [[Jekyll]].
| |
| − | :# '''Plain code'''. The authorization and landing pages of [[#Featured|Featured]] websites can also be coded with [[HTML5]], [[CSS]], and [[JavaScript]] without any ''CMS''.
| |
| − | | |
| − | : Results of ''software projects'' shall be stored at [[CNM Repo]]; [[CNM System Administrator]]s use those results to install and run the actual software.
| |
| − | | |
| − | ===Website-core projects===
| |
| − | : For the purposes of this very wikipage, ''website-core projects'' refer to the [[website project]]s that are undertaken to make a ''Cyber'' website one product. [[#Content projects|Content]], [[#Design projects|Design]], [[#SEO projects|SEO]], [[#Software projects|Software]], and [[#WWW projects|WWW projects]] shall deliver various parts of websites. [[#IA developments|IA developments]] shall produce their "skeletons" or "embryos" of their core. Then, website assemblies shall make one product out of all.
| |
| − | | |
| − | : Development of any website is rarely a simple and straightforward process. To emerge on the [[World Wide Web]] ([[World Wide Web|WWW]]), any website goes through various [[product state]]s.
| |
| − | :# '''Website as an idea'''. Any website starts with an idea; it should be imagined first to be developed second. The first idea may be expressed in few words.
| |
| − | :# '''Website as a prototype'''. Before a website emerges on ''WWW'', it exists as its [[information architecture]]s (or [[information architecture|IA]]s). A separate section of this very wikipage, [[#Website IAs|Website IAs]] is dedicated to them.
| |
| − | :# '''Website as a MVP'''. In cases of ''Cyber'' website development, a [[minimum viable product]] ([[minimum viable product|MVP]]) is an early version of a future website that includes sufficient features to satisfy early adopters. To do so, the website shall have its [[hub webpage]]s, ''IA'' that would be implemented on its software and located on ''WWW''.
| |
| − | :# '''Website as a marketable'''. To serve a part of [[#The funnel|The funnel]], ''Cyber'' website shall possess those features that are developed in the [[#Content projects|Content]], [[#Design projects|Design]], [[#SEO projects|SEO]], [[#Software projects|Software]], and [[#WWW projects|WWW projects]].
| |
| − | | |
| − | ===WWW projects===
| |
| − | : For the purposes of this very wikipage, ''WWW projects'' refer to the [[website project]]s that are undertaken to integrate ''Cyber'' websites into the [[World Wide Web]] ([[World Wide Web|WWW]]) securely.
| |
| − | :* '''[[DNS record]]s''' to locate ''Cyber'' websites within ''WWW''. DNS records' drafts are published at [[CNM Wiki]]; [[CNM System Administrator]]s use those results to update the actual website records. DNS records for [[CDN]]-based websites might be complex.
| |
| − | :* '''[[SSL certificate]]s''' to encrypt interactions between ''Cyber'' websites and their visitors.
| |
| − | :* '''[[Webserver]]s''' to direct external requests to internal resources. ''Cyber'' websites normally rely on [[Apache HTTP Server]] and/or [[Nginx]] servers. They may serve separately or in sequence ''Nginx'', as highly productive, first, and ''Apache'', as highly reliable, second.
| |
| − | | |
| − | ==Website IAs==
| |
| − | For the purposes of this very wikipage, [[information architecture]]s or [[IA]] are images, layouts, mockup models, outlines, [[prototype]]s, sketches, wireframes, and/or words that represent classification, organization, and structure of content and other information at ''Cyber'' websites or similar products. Similarly to [[UX design]], ''IA'' strives to enhance user satisfaction; ''IAs'' of ''Cyber'' products shall help to make them accessible, credible, desirable, findable, usable, useful, and valuable. Dissimilarly from [[UX design]], ''IA'' shall help the ''Cyber'' to achieve the [[#Cyber objectives|Cyber objectives]]. In simple words, ''IA'' shall balance benefits for the ''Cyber'' and its users.
| |
| − | | |
| − | ===IA components===
| |
| − | : Key components of ''IA'' are:
| |
| − | :# '''Hierarchy''' of website and its webpages.
| |
| − | :# '''Roadmaps''' of every identified persona through the website.
| |
| − | :# '''Mockups''' of hub webpages at the [[websection box]] level.
| |
| − | :# '''Labels''' of groups of information for user orientation and, when used in sub-domain names, for [[search engine optimization]] ([[search engine optimization|SEO]]).
| |
| − | :# '''Navigations''' such as menus, breadcrumbs, and pagination.
| |
| − | :# '''Search tools''' that ensure findability of information.
| |
| − | | |
| − | ===IA developments===
| |
| − | : No ''Cyber'' IA can be developed immediately and completely. It starts with a sketch to be gradually upgraded up to a prototype. The ''IA''-development projects closes when the [[#Customer|Customer]] approves the ''IA''. Development of ''IA'' is a:
| |
| − | :* Marketing project since the ''IA'' shall serve interests of both users and the ''Cyber''.
| |
| − | :* Creative project since [[acceptance criteria]] rarely can be defined; product and project certainties rarely can be reached before the development starts. That is why [[#Contractors|Contractors]] shall be hired on a per-hour basis. In the industry, the most qualified architects are normally hired to develop the most important ''IA'' components such as the menu structure and landing page mockup.
| |
| − | :* Prerequisite project that shall be finished before the contractors to develop a website as a [[marketable]] can be hired. As [[product depiction]]s, the outputs of the ''IA''-development project shall be used for graphic design, UX design, and website assemblies.
| |
| − | | |
| − | ===Personas in IA===
| |
| − | : In [[marketing]], a ''persona'' is an imaginary product user that (a) represents a distinguishable type of customer and (b) has been created to design special appeals to that customer type while designing products.
| |
| − | | |
| − | : ''Cyber'' websites may serve a variety of customers. For instance, a school student and school principal may visit [[iDosvid.com]]. However, interests of the student differ from ones of the principal. Moreover, the [[#Team|Team]] would like the student to get enrolled into [[CNM Cyber Welcome Session]], while the [[#Team|Team]] would like the principal to contact ''Cyber'' administrators. So, their website roadmaps shall be different.
| |
| − | | |
| − | : [[Information architecture]]s (or [[Information architecture|IA]]s) shall serve all of its identified personas. If a subordinate IA serves one persona, and five personas are identified to be customers, the IA may be divided in one site-wide IA, which welcomes all of its customers and directs them to those webpages that are designed to serve specifically them and five separate subordinate IAs.
| |
| − | | |
| − | ==Website parts==
| |
| − | ''Cyber'' websites are eventual deliverables from web-projects; however, website components need to be developed before any website can be assembled. Other deliverables include [[webpage]]s, [[webpage section]]s, [[websection box]]es, [[information architecture]]s, [[web design]]s, [[SEO strategy|SEO strategies]], as well as contents such as audiovisuals, images, multimedia, and texts.
| |
| − | | |
| − | [[Website]]s are not created equal; neither are their developments. It may take about a couple of hours to setup a simple website if its content is ready. On the contrary, some other websites cost more than a million dollars.
| |
| − | | |
| − | ===Webpages===
| |
| − | : Any ''Cyber'' website is a collection of [[webpage]]s. At the ''Cyber'', those pages are divided in three categories:
| |
| − | :# '''[[Auxiliary webpage]]s''' are those that provide their visitors with supplemental services beyond essay information and hub navigation. Auxiliary pages include contact, error, and search pages, for instance.
| |
| − | :# '''[[Essay webpage]]s''' are those that cover one subject; they give the most complete information on a given topic that is available on that website.
| |
| − | :# '''[[Hub webpage]]s''' are those essential pages that lead their visitors to other pages or services, where ''essential'' means that the website cannot function properly without those pages. Every ''Cyber'' website has at least two ''hubs'' -- the authenticating and landing webpage.
| |
| − | | |
| − | ===Websections===
| |
| − | : Any ''Cyber'' webpage is a collection of two or more [[webpage section]]s. That ''section'' shall emerge on one user's screen or, at least on the top of the screen, after their clicks on some menu tab or other button. Every ''Cyber'' webpage shall have its main and footer sections at very least.
| |
| − | | |
| − | : With regards to the purpose, websections may serve three purposes:
| |
| − | :# '''[[Deal-closing websection]]s''' normally belong to online stores.
| |
| − | :# '''[[Lead-generation websection]]s''' normally belong to [[hub webpage]]s of [[#Featured|Featured]] websites and any page of [[#Traffic-generating|Traffic-generating]] websites.
| |
| − | :# '''[[Prospect-education websection]]s''' are normally headsections of [[essay webpage]]s of both [[#Featured|Featured]] and [[#Traffic-generating|Traffic-generating]] websites.
| |
| − | | |
| − | : A headsection is the most important for every webpage. ''Webpage sections'' present one or more [[websection box]]es. That box is the minimal rectangular element of [[webpage layout]]s that is distinguished from other rectangular parts both graphically and functionally. The headsection normally consists of a header and a box such as carousel, featured-image, grid, slider, or CTA (which stands for "call-to-action"). The headsection may also include a sidebar.
| |
| | | | |
| − | ==Product states==
| + | On this wikipage, ''projects'' specifically refer to those [[website project]]s that are undertaken to create [[#What Devs produce|What Devs produce]]. The ''Devs's'' deliverables include [[#Website deliverables|Website deliverables]] and [[#Work documents|Work documents]]. While working on projects, the ''Devs'' are engaged in the [[#What Devs do|What Devs do]] activities as discussed above. |
| − | For the purposes of this very wikipage, [[product state]]s refer to sets of conditions that ''Cyber'' products acquire during their development and service. The ''Coords'' work to bring the products into one or more of their states.
| |
| | | | |
| − | ===State definitions=== | + | ===Authorized projects=== |
| − | :# '''[[State of acknowledgment]]'''. In this state, the future deliverable exists in the form of a noticed and documented idea. | + | : Those [[#Projects|Projects]] that are authorized to practice with are listed on the [[CNM Website Projects]] wikipage. |
| − | :# '''[[State of certainty]]'''. In this state, the future deliverable exists as a validated [[product specification]].
| |
| − | :# '''[[State of capability]]'''. In this state, the functional deliverable has already been produced in accordance with all the requirements that have been approved for it.
| |
| − | :# '''[[State of applicability]]'''. In this state, the deliverable is not only functional, but can also be used for the purpose for which it was produced in ways that are described by a validated [[standing operational procedure]] ([[standing operational procedure|SOP]]).
| |
| − | :# '''[[State of manageability]]'''. In this state, the deliverable is not only used for the purpose for which it was produced, but also controlled, that is, the product undergoes periodic revisions and is either improved and its characteristics are improved, or withdrawn from service.
| |
| | | | |
| − | ===Hierarchy=== | + | ===DREPD patterns=== |
| − | : In practice, [[product state]]s 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. | + | : ''Main wikipage: [[DREPD]]'' patterns represent the steps in a projects progression. |
| | | | |
| − | ===Thresholds===
| + | : Although no single straightforward pattern of project advancement efforts, various developments tend to be cyclical. As an example, letters in the [[DREPD]] cycle represent five steps: |
| − | :{|class="wikitable" width=100% | + | :# '''D''' for "[[#Discovering the issues|Discovering the issues]]". To initiate a project, the ''Devs'' shall identify the website need that they would like to satisfy. Outside of website development, we can compare this step with a situation in which someone realizes that he or she needs a better Internet access. |
| − | !Product state!!Threshold
| + | :# '''R''' for "[[#Researching the grounds|Researching the grounds]]". To start the initiated project, the ''Devs'' shall study the website needs and work environments in some depth. Outside of website development, we can compare this step with someone's search for available Internet service provider's offers after he or she realized that they need to improve their Internet access. |
| − | |-
| + | :# '''E''' for "[[#Envisioning the results|Envisioning the results]]". To plan the researched project, the ''Devs'' shall imagine what the solutions should look like. Outside of website development, we can compare this step with someone's decision what Internet access they are willing to purchase. |
| − | |[[State of acknowledgment]]||A record is added to the [[idea management system]].
| + | :# '''P''' for "[[#Planning the production|Planning the production]]". To execute the project plan, the ''Devs'' shall decide how the imagined solution should be developed. Outside of website development, we can compare this step with someone's plans for how they purchase the needed Internet access and how they pay for it. |
| − | |-
| + | :# '''D''' for "[[#Doing to move forward|Doing to move forward]]". To start a new DREPD cycle, the ''Devs'' shall act on the plan, observe real situations, and re-identify the website need. Actually, the action verbs in that step starts with ''D''; ''do'' what is planned, ''detect'' what hasn't been expected, and ''discover'' new wills. That new discovery may start a new cycle; new data shall emerge while doing and/or after getting something done. Outside of website development, we can compare this step with someone's purchase of Internet access and getting lessons learned in order to make the next purchase better. |
| − | |[[State of certainty]]||A [[product specification]] is approved.
| |
| − | |-
| |
| − | |[[State of capability]]||[[Acceptance criteria]] are met.
| |
| − | |-
| |
| − | |[[State of applicability]]||A [[standing operational procedure]] ([[standing operational procedure|SOP]]) is approved.
| |
| − | |-
| |
| − | |[[State of manageability]]||Periodic reviews find that [[standing operational procedure]]s ([[standing operational procedure|SOP]]s) are both sound and followed.
| |
| − | |}
| |
| | | | |
| − | ==Devices of certainty==
| + | : This cycle or, to be more exact, cycle of cycles, can be applied to various types of developments, including audiovisuals, [[minimum viable product]]s ([[minimum viable product|MVP]]s), textual contents, prototypes, and [[website IA]]. |
| − | For the purposes of this very wikipage, a ''device of certainty'' refers to an instrument or tool that ensures:
| |
| − | * Product certainty, which their development shall deliver. When the [[#Customer|Customer]] agrees, products shall not necessarily possess their [[state of certainty]] for the beginning of their development, but this state shall be achieved during that development.
| |
| − | * Project certainty, which suggests the scope of product development. Project certainty cannot be reached unless product certainty is reached. Clearly, no one can know what to do unless they know what needs to be done. The scope of work depends on the scope of work product. Moreover, the overwhelming majority of ''Cyber'' projects cannot be fully predicted and, therefore, achieve their complete certainty only with their closure.
| |
| | | | |
| − | ===General certainty===
| + | : In the meanwhile, the ''Devs'' are encouraged to apply at least one [[DREPD]] cycle to every task mentioned in the [[#What Devs do|What Devs do]] section above. |
| − | : For the purposes of this very wikipage, a ''general certainty'' refers to those devices that may combine product and project certainties. | |
| − | :# '''[[Business requirement]]s'''. Description of the needs for which the development of the deliverable is undertaken.
| |
| − | :# '''[[#Funded demands|Demands of Team funded by Customer]]'''. Description of what the [[#Team|Team]] needs and, possibly, when and how it needs expressed when the [[#Customer|Customer]] has funded satisfaction of those needs. Those demands are expressed in either [[acceptance criteria]] or [[standing operating procedure]] ([[standing operating procedure|SOP]]).
| |
| − | :# '''[[Stakeholder requirement]]s'''. Description of the future deliverable made on behalf of various types of its stakeholders.
| |
| | | | |
| − | ===Product only certainty=== | + | ===Project variety=== |
| − | : A few devices ensure certainty of product deliverables: | + | : ''Main wikipage: [[Website project]]'' |
| − | :# '''[[Product depiction]]s'''. Representation in images, layouts, mockup models, outlines, [[prototype]]s, sketches, wireframes, and/or words of a deliverable to be created. [[Prototype]]s (from the Greek "prōtos" meaning "first", "original" and "typos" meaning "imprint", "pattern"). Instances, samples or models, following the example of which others are made or finalized. Prototypes of the deliverable are often built to test a perception, concept, or process. Prototypes can either be selected from existing products or produced during a project.
| |
| − | :# '''[[Product specification]]s'''. Set of tasks for developers of a deliverable regarding its required characteristics.
| |
| | | | |
| − | : [[Business requirement]]s, [[stakeholder requirement]]s, and [[acceptance criteria]] clarify [[product scope]]s, but may also clarify scopes of their production, delivery, and/or other elements of [[project scope]]s. | + | : The [[website project]] wikipage presents a general, not specific to the ''Cyber'', variety of website development endeavors. |
| | | | |
| − | ===Project only certainty=== | + | ===Sprint=== |
| − | : [[Project scope]]s depend on their [[product scope]]s, so any [[project document]] can get some glimpse into its product certainty. A few devices ensure certainty of project processes and product delivery: | + | : In [[CNM Agile]], a [[sprint]] refers to the completion of [[DREPD]] cycles that lead to a desirable deliverable [[work-product state]]. One sprint typically lasts for 3-5 weeks. |
| − | :# '''[[Project scope baseline]]'''. The combination of project work requirements that the [[#Customer|Customer]] has approved and that are used as the base to compare with actual results. For complex projects, the baseline normally includes a [[project scope statement]], [[work breakdown structure]] ([[Work breakdown structure|WBS]]), and [[WBS dictionary]].
| |
| − | :#* [[Project scope statement]]. General description of the project work and its desired results, as well as assumptions, constraints and other project requirements.
| |
| − | :#* [[Work breakdown structure]] ([[Work breakdown structure|WBS]]). Hierarchical decomposition of the complete project work.
| |
| − | :#* [[WBS dictionary]]. Detailed deliverable, activity, and scheduling data for each component in the [[work breakdown structure]] ([[work breakdown structure|WBS]]).
| |
| − | :# '''[[Project schedule baseline]]'''. The combination of project schedule requirements that the [[#Customer|Customer]] has approved and that are used as the base to compare with actual results.
| |
| − | :# '''[[Project cost baseline]]'''. The combination of project cost requirements that the [[#Customer|Customer]] has approved and that are used as the base to compare with actual results.
| |
| | | | |
| − | : [[Business requirement]]s, [[stakeholder requirement]]s, and [[acceptance criteria]] may or may not clarify [[project scope]]s in addition to clarifications of [[product scope]]s. | + | ==Projects of projects== |
| | + | [[File:Solution-project.png|400px|thumb|right|[[Problem]], [[solution]], and [[project]]]]Any authentic [[website]] is a unique deliverable by itself. A Website is made up of of different elements like audiovisuals, designs, DNS records, images, and texts, each of these elements needs to be developed and delivered before the website can be launched. |
| | | | |
| − | ==Administration==
| + | So, a bigger deliverable, which is a website in that case, is an aggregate of several smaller deliverables. Therefore, the website development consists of many projects. Several projects shall be undertaken in order to develop one website; several projects shall also be undertaken in order to develop each website component. |
| − | For the purposes of this very wikipage, [[administration]] is defined as the set of efforts that is undertaken to run ''Cyber'' resources such as its budgets, services, systems, and/or staffers of the [[#Office|Office]].
| |
| | | | |
| − | ===Administrators===
| + | The ''Devs'' normally practice with those projects that are listed on the [[CNM Website Projects]] wikipage; however, the ''Devs'' can also propose and initiate other other projects. |
| − | : At the ''Cyber'', several types of administrators can be distinguished depending on the category of administration:
| |
| − | :* '''Application administrators''' are administrative user roles in [[CNM app]]s. For example, an administrator of [[CNM Wiki]] can protect select wikipages from editing by non-admins. Application administrators are a software feature, which only system administrators may assign. Organizationally, [[CNM Cyber Project Manager]]s must request assigning admin roles to select members of the [[#Team|Team]] and, vice versa, request removing them when there is no longer need.
| |
| − | :* '''Executive administrators''', [[CNM Cyber Project Manager]]s, are those of the [[#Office|Office]] who manage ''Cyber's'' development, operations, and product groups. This administrator can appoint other members of the [[#Team|Team]] to administer a particular group of developments, operations and products or the ''Cyber'' as a whole.
| |
| − | :* '''Product administrators''' are those of the [[#Team|Team]] whom [[CNM Cyber Project Manager]]s have granted administration of a particular product. During its production, the deliverables are administered by the ''Coords''. The superior administrator of each product is at least one of [[CNM Cyber Project Manager]]s.
| |
| − | :* '''System administrators''' are dedicated positions intended for those associates who administer the technological systems of [[CNM Farms]]', [[Opplet]]'s, and [[CNM app]]s' software. The highest administrator of each attachment is at least one of the system administrators, so the latter can be described as super administrators of applications.
| |
| | | | |
| − | ===Customer=== | + | ===Problem recognition=== |
| − | : The customer provides requirements for future products and pays project budgets. In simple words, the customer orders products and pays for their production. The work of the ''Coord'' is paid insofar as it is part of the development of the product. The customer implies that the ''Coord'' works out projects in accordance with the instructions set out on this wikipage. Out of the goodness of heart and for professional training purposes, the customer may do the work of the ''Coord'' temporarily as long as the customer believes that the ''Coord'' will someday be able to work independently.
| + | To demonstrate how it may work, let's take the following hypothetical scenario: |
| | + | : Marie a ''Dev'', noticed that the landing screen of your website needs some background. After researching the requirements, she came up with a solution involving drawing. Marie is now working on a project to implement this solution. Marie describes the future video. She is not a graphic designer, but she may create a sketch or just describe that drawing in order to help [[CNMCyber Coordinator]]s hire needed designers. |
| | | | |
| − | ===Cyber objectives=== | + | ===Solution idea=== |
| − | :* ''Cyber's'' mission is to build a single-window platform that would responsibly and sustainably provide everyone with a wide range of career services. | + | : To demonstrate how it may work, let's take the following hypothetical scenario: |
| | + | : Tnya a''Dev'', found a problem with the landing screen of the kryvi.com website which needs some background. Tanya researched the constraints and came up with a solution by creating a drawing. Now, she is undertaking the solution idea project while planning for that drawing to be created. Tanya is not a graphic artist, but she is sketching and describing that drawing in order to help [[CNMCyber Coordinator]]s hire needed designers. |
| | | | |
| − | ===Organizations=== | + | ===Solution development=== |
| − | : Legally, the ''Coords'' are either [[volunteer]]s of [[The Economic Group]] or [[independent contractor]]s of [[Educaship Alliance LLC]]. The ''LLC'' is willing to employ the ''Coords'' as employees, but, to do so now, no legal infrastructure has setup yet. These organizations may issue their own policies and regulations. | + | To demonstrate how it may work, let's take the following hypothetical scenario: |
| | + | :# ''Solution development project''. Nadia is a graphic artist and is seeking opportunities in her field. While working as the ''Dev'', she discovered [[CNMCyber]]'s need to have a drawing for their kryvi.com website's landing screen. Nadia carefully reviewed available sketches and descriptions. To understand the constraints, Nadia attended a [[Careerprise conference]]. She was directed to the [[standing operating procedure]] ([[standing operating procedure|SOP]]) that described CNMCyber's policies and requirements related to image acquisitions. Particularly, Nadia found out that the drawings shall be submitted to [[CNM Lab]] in the [[SVG]] format. Then, Nadia envisioned the desired deliverable. After that, Nadia planned for her drawing to be created. Specifically, she decided how she would draw the solution and submit it as a deliverable and estimated her time commitment. Nadia proposed her plan to [[CNMCyber Coordinator]]s and was hired as a [[Careerprise contractor]] in addition to her ''Dev'' role. Now, Nadia is undertaking the solution development project while creating the drawing in order to deliver it to [[CNMCyber Coordinator]]s. |
| | | | |
| − | ==Team== | + | ===Solution deployment=== |
| − | For the purposes of this very wikipage, the ''Team'' refers to staffers of the ''Cyber''. Although [[#Contractors|Contractors]] and the [[#Customer|Customer]] are not formally part of the ''Cyber'' team, they are important parts of ''Cyber'' development and management.
| + | To demonstrate how it may work, let's take the following hypothetical scenario: |
| | + | : Anna a ''Dev'', identified a problem with landing screen of your website requires a background. After researching the constraints, Anna envisioned some drawing as the solution for that problem. Now, she is undertaking the solution idea project while planning for that drawing to be created. She describes the future video. Although not a graphic designer, Anna can either create a sketch or describe that drawing in order to help [[CNMCyber Coordinator]]s hire needed designers. |
| | | | |
| − | ===Office=== | + | ==Website-core projects== |
| − | : For the purposes of this very wikipage, the ''Office'' refers to entry-level staffers of the ''Cyber''. They may include [[CNM Cyber Project Manager]]s, [[CNM Cyber Recruiter]]s, [[CNM Cyber Security Analyst]]s, [[CNM System Administrator]]s, [[CNM Systems Engineer]]s, and [[CNM Web Developer]]s.
| + | [[Website]]s are complex products, so are their production. For the purposes of this very wikipage, ''website-core projects'' refer to those [[website project]]s that are undertaken to develop the core of websites rather than their components such as [[#Public contents|Public contents]], [[#SEO efforts|SEO efforts]], and non-essential [[#WWW settings|WWW settings]]. Thus [[Website-Core Projects]] focus on developing the main structure and components of a website. |
| | | | |
| − | ===Taskforce===
| + | Among [[#Website designs|Website designs]], [[CNMCyber Team]] classifies [[website IA]]s as the backbone of the website core, while [[graphic design]] and [[UX design]] as parts of [[Careerprise Funnel]]. |
| − | : For the purposes of this very wikipage, the ''Taskforce'' refers to the aggregate of the ''Coords''.
| |
| | | | |
| − | ==Contractors== | + | ===Website idea=== |
| − | With the exception of the [[#Communications|Communications]], [[#Documents|Documents]], [[#Meetings|Meetings]], and [[#Records|Records]], the ''Coords'' rarely develop and manage the [[#Project deliverables|Project deliverables]] directly or, or least, without someone else's assistance. For the most part, contractors develop and service them. The contractors perform on the basis of approved descriptions, [[#Funded demands|Funded demands]], and finalized by the ''Coors'' and/or other members of the [[#Team|Team]]. The ''Coords'' facilitate the [[#Hiring the contractors|Hiring the contractors]] and [[#Working with contractors|Working with contractors]] activities.
| + | A new website starts with an idea; which can be expressed through words or sketches on [[ CNM Wiki]] platform uploaded there as files. These sketches serve as drafts for the websites overall structure known as the [[website IA]]. |
| | | | |
| − | ===List of contractors=== | + | ===Wiki-based prototype=== |
| − | : The list of contractors is a part of the [[competency register]] created and updated during the [[#Studying the backgrounds|Studying the backgrounds]] activities. | + | : The [[CNMCyber Team]] utilizes [[CNM Wiki]] to develop early functional websites. Each webpage is represented by a separate Wikipage acting as a prototype. Internal site links shall be made manually. Titles of webpage prototypes on [[CNM Wiki]] shall have the webpage name starting with a capital letter between <code>[Domain-name]</code> and the word, <code>(prototype)</code> in parenthesis, for instance, [[CNMCyber.com About-us]]. The landing webpage is named "Home", for example, [[CNMCyber.com Home]]. All prototype pages belong to the <code>[Domain-name] Prototypes</code> category format under the [[:Category: Website Prototypes]]. |
| | | | |
| − | ===Payment models=== | + | ===CMS-based prototype=== |
| − | :* '''Fixed-price basis''' (in recruiting, known as ''contingency model''). When either [[acceptance criteria]] or [[standing operating procedure]] ([[standing operating procedure|SOP]]) is available, ''Cyber'' contractors are paid a fixed price. This price might be chunked in several payments and some payments may be made in advance. This model assumes that all of the three, "scope of work, terms, budget" are well defined. Otherwise, the [[#Team|Team]] risks to receive not what it needs, or not for the budgeted money, or when it no longer needs it. | + | : The [[CNMCyber Team]] utilizes [[content management system]]s like [[Educaship WordPress]] for website development. The ''Devs'' normally transfer website textual contents from [[CNM Wiki]] to a ''CMS''-based prototype. Placeholders are used for audiovisual elements that are not yet developed and [[lorem ipsum]] is used as a substitute for future texts. |
| − | :* '''Per-hour basis''' (in recruiting, known as ''retained model''). When neither [[acceptance criteria]] nor [[standing operating procedure]] ([[standing operating procedure|SOP]]) is available, ''Cyber'' contractors are paid per hour. Architects, consultants, designers, managers, and others whose jobs are not structured shall be hired on the per-hour basis.
| |
| | | | |
| − | : Those two models may be combined. For instance, compensation of agents, brokers, and sales representatives may consist of (a) payment for their time (sometimes, called a [[retainer]]) and (b) percentage of generated sales. | + | ===Website MVP=== |
| | + | : A [[minimum viable product]] is an early version of a [[CNMCyber website]] that includes enough features to satisfy early adopters. The ''Devs'' implement the [[website IA]] on a [[content management system|CMS ]] and make website accessible on [[World Wide Web|WWW]]. At this stage, [[Lorem ipsum]] shall no longer be used and audiovisual placeholders shall not look like construction pieces at the ''MVP'' stage of development. |
| | | | |
| − | ===Restrictions in awards=== | + | ===Website marketable=== |
| − | : To ensure diversity of contractors and, therefore, higher quality: | + | : A [[CNMCyber website]] is designed to be marketable and contribute to the [[Careerprise Funnel]]. During the ''Practice'' phase, the ''Devs'' usually don't focus marketable aspects of the website. However, after completing the [[ Website Development]] quarter of the ''Bootcamp'', they can work on website marketability as [[Careerprise Contractors]]. |
| − | :# No new contract can be awarded to the service contractor who serves the product currently.
| |
| − | :# The development contractor cannot also be the first service contractor.
| |
| − | :# Although the ''Coords'' are encouraged to serve as contractors outside of their ''Coord'' work, no one can simultaneously serve as the ''Coord'' and contractor working on the same product.
| |
| | | | |
| − | ===Types of contractors=== | + | ==What Devs do== |
| − | : For the purposes of this very wikipage, [[contractor]]s are distinguished in three types:
| + | In order to deliver [[#What Devs produce|What Devs produce]], the ''Devs'' are encouraged to follow the recommendations as follows. |
| − | :* '''Developers''' or development contractors create [[#Project deliverables|Project deliverables]] based on their [[acceptance criteria]] to be commissioned as ''Cyber'' products or their parts. The developers are routinely paid on the fixed-price basis for their performance; perspective developers shall be invited to volunteer to draft [[project charter]], [[product specification]]s, [[project scope statement]], [[acceptance criteria]], as well as other [[project document]]s.
| |
| − | :* '''On-call specialists''' provide the ''Coordinators'' with their expertise at any stage of product imagination, creation, commissioning, and productive life when their expertise is needed before either [[acceptance criteria]] or [[standing operating procedure]] ([[standing operating procedure|SOP]]) is available. On-call specialists are normally paid per hour.
| |
| − | :* '''Servicers''' or service contractors serve CNM Cyber products based on their [[standing operating procedure]]s ([[standing operating procedure|SOP]]s). The servicers are routinely paid on the fixed-price basis for their performance; perspective servicers shall be invited to volunteer to clarify their ''SOPs'', as well as other product documents.
| |
| | | | |
| − | ==Contractor agreements==
| + | Developing a website is a unique project, and there are no final instructions that can be followed to achieve success since every [[website project]] is unique. If any [[project]] is no longer unique, it is no longer a project. It is an [[ongoing operation]]. However, there are some suggested blueprints that developers can follow. The following guide outlines the typical processes that developers follow, while following the DREPD patterns. |
| − | The [[#Team|Team]] uses [[Careerprise contractor agreement]]s to hire its contractors directly; hereinafter, they are called the ''Contracts''. A blueprint of the ''Contract'' is published at the [[Careerprise contractor agreement]] wikipage.
| |
| | | | |
| − | Some portion of contractors is hired through [[freelance marketplace]]s such as [[Upwork]]; their blueprints are used in that case.
| + | While following the [[#DREPD patterns|DREPD patterns]], the ''Devs<nowiki>'</nowiki>'' practice can be divided in sets of processes. Every of the [[#Projects|Projects]] shall start with : |
| | + | # [[#Discovering the issues|Discovering the issues]],- The first step in any project is discovering the issues that need to be addressed. This involves understanding the project requirements and identifying any potential problems. |
| | + | # Go through [[#Researching the grounds|Researching the grounds]], - Once the issues have been identified, developers must research the grounds to gain a deeper understanding of the problem. This can involve researching the target audience, competitors, and technology solutions. |
| | + | # [[#Envisioning the results|Envisioning the results]], - With a clear understanding of the project requirements and potential solutions, developers can begin envisioning the results. This involves creating a clear vision of what the final product will look like and how it will function. |
| | + | # [[#Planning the production|Planning the production]], - Once the vision has been established, developers can begin planning the production process. This involves breaking down the project into smaller, manageable tasks and creating a timeline for completion |
| | + | # [[#Doing to move forward|Doing to move forward]] activities - With a solid plan in place, developers can start the doing to move forward activities. This involves coding, designing, and testing the website. |
| | | | |
| − | ===Content matters===
| + | The [[DREPD]] cycle runs several times as the project deliverable progresses from a [[#Website idea|Website idea]] to a [[#Wiki-based prototype|Wiki-based prototype]], [[#CMS-based prototype|CMS-based prototype]], and, eventually, [[#Website MVP|Website MVP]]. After that, [[CNMCyber Coordinator]]s take over the website projects to hire [[Careerprise contractor]]s in order to develop [[#Website marketable|Website marketable]]s. |
| − | : Any contract's content features at least two major matters:
| |
| − | :# '''Subject matters''' is what essentially the parties of the ''Contract'' are going to exchange. More specifically, they consist of two parts:
| |
| − | :#* [[#Funded demands|Funded demands]] is what the [[#Customer|Customer]] would like to exchange its funds for. Usually, the demands include requirements to the deliverable, its production, and delivery.
| |
| − | :#* Payment provisions that define what the contractor shall expect to be paid when the [[#Funded demands|Funded demands]] are satisfied.
| |
| − | :# '''Legal matters''' include legal provisions such as legal names, dates, statuses, ownership, representation, indemnification, confidentiality, communications, dispute-resolution procedures, warranties, and miscellaneous ones.
| |
| | | | |
| − | ===Funded demands=== | + | ===Discovering the issues=== |
| − | : For the purposes of this very wikipage, ''funded demands'' refer to those demands of the [[#Team|Team]] that are funded by the [[#Customer|Customer]]. The [[#Team|Team]] hires contractors to satisfy specific [[business need]]s when the [[#Customer|Customer]] agrees to fund such hiring. Before they enter the ''Contract'' or third-party contracts, these funded demands can be stated in a [[project charter]] and/or [[request for proposal]] ([[Request for proposal|RFP]]). For fixed-priced contracts, it can be stated in one of the following two: | + | : To initiate a [[website project]], the ''Devs'' shall understand the project requirements and identify any potential problems with the help of the steps below: |
| − | :* '''[[Acceptance criteria]]'''. A combination of those demands that a deliverable must satisfy to be acceptable by the [[#Customer|Customer]]. | + | :# '''Follow''' the [[#How to start|How to start]] for recommendations. |
| − | :* '''[[Standing operating procedure]]''' ([[Standing operating procedure|SOP]]). A set of instructions that cover both (a) regular business and/or technology operations and (b) actions in emergencies. ''SOP'' is applicable unless ordered otherwise. | + | :# '''Explore''' existing [[CNMCyber website]]s, their documentation at [[CNM Wiki]], other websites related to [[career service]]s that are available on the market. |
| | + | :# '''Compare''' existing [[CNMCyber website]]s, their documentation at [[CNM Wiki]], as well as other websites related to [[career service]]s that are available on the market to detect opportunities to help improve existing [[CNMCyber website]]s. |
| | + | :# '''Identify''' the [[business need]] that some [[CNMCyber website]] shall satisfy. |
| | + | :# '''Create''' a project wikipage called <code>[Domain-name] for CNMCyber page </code>, starting the identified ''need'', its reasoning and backgrounds by creating Purpose, Target audiences, Requirements (Business, Stakeholder's, Technical), States sections. |
| | + | :# '''Create''' a product wikipage called <code>[Domain-name]</code>, while starting describing the website by creating Design, Content, Prototypes, DNS records, SEO sections. |
| | + | :# '''Report''' on progress of the initial project discovery using the [[CNM Website Projects]] wikipage. |
| | + | :# '''Present''' the progress, plans and possible concerns during the weekly [[CNMCyber This Week]] meetings. |
| | | | |
| − | : For hourly-paid contracts the demand statement tends to be less concrete; at those cases, the [[#Team|Team]] "buys" contractor's time, not a particular deliverable, its production, or delivery. | + | : The initial project discovery ends when the [[business need]] is identified. New project discoveries belong to the [[#Doing to move forward|Doing to move forward]] activities. |
| | | | |
| − | ==Recruiting the Coords== | + | ===Researching the grounds=== |
| | + | : To start the initiated project, the ''Devs'' shall research the grounds to gain a deeper understanding of the problem with the help of the following steps: |
| | + | :# '''Study''' the website needs and project environments in some depth. |
| | + | :# '''Identify''' those sources, primarily [[stakeholder]]s and competitors, of information that can be useful for website development. |
| | + | :# '''Evaluate''' what output, a [[#Website idea|Website idea]], a [[#Wiki-based prototype|Wiki-based prototype]], [[#CMS-based prototype|CMS-based prototype]], or [[#Website MVP|Website MVP]], is expected from the current efforts, as well as its status of completeness. |
| | + | :# '''Update''' the project and product wikipages, while linking the new data to the identified sources. |
| | + | :# '''Report''' on progress of the project studies using the [[CNM Website Projects]] wikipage. |
| | + | :# '''Present''' the progress, plans and possible concerns during the weekly [[CNMCyber This Week]] meetings. |
| | | | |
| − | There is no single simple indicator by which one can judge whether a person can become a successful ''Coord'' and, if so, whether similar jobs would attract and motivate him or her. One never knows unless one tries.
| + | : The 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. |
| | | | |
| − | ===Coords' sourcing=== | + | ===Envisioning the results=== |
| − | : ''Main wikipage: [[WorldOpp Sourcing]]'' | + | : To plan the researched project, the ''Devs'' shall begin envisioning the results by creating a clear vision of what the final product will look like and how it will function using the steps below as a guide: |
| | + | :# '''Identify''' those target audiences who are supposed to use future deliverables. |
| | + | :# '''Create''' imaginary personas that would represent each of the identified audience. |
| | + | :# '''Produce''' [[stakeholder requirement]]s for each created persona using [[CNM Wiki]]. |
| | + | :# '''Conceive''' what the solutions should look like. |
| | + | :# '''Describe''' the solution or solutions using [[CNM Wiki]]. |
| | + | :# '''Report''' on progress of the product description using the [[CNM Website Projects]] wikipage. |
| | + | :# '''Present''' the progress, plans and possible concerns during the weekly [[CNMCyber This Week]] meetings. |
| | | | |
| − | : [[WorldOpp Sourcing]] encompasses the [[WorldOpp Outreach]] campaigns to attract attention of potential candidates and [[CNM Cyber Welcome Session]] to bring the candidates on the board. | + | :The product description efforts shall start when [[business need]]s are identified and end when a [[#Sprint|Sprint]] of the product wikipage development is completed. |
| | | | |
| − | ===Coords' orientation=== | + | ===Planning the production=== |
| − | : ''Main wikipage: [[CNM Cyber Orientation]]'' | + | : To execute the project plan, the ''Devs'' shall begin planning the production process by breaking down the project into smaller, manageable tasks and creating a timeline for completion with the help of the steps below: |
| | + | :# '''Examine''' the existing products that are going to be further developed if they are available. |
| | + | :# '''Analyze''' the collected project data while organizing that data on [[CNM Wiki]]. |
| | + | :# '''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. |
| | + | :# '''Decide''' how the imagined solution should be developed. |
| | + | :# '''Draft''' a plan of actions that need to be undertaken in order to execute the development decisions. |
| | + | :# '''Publish''' the project plan on [[CNM Wiki]]. |
| | + | :# '''Report''' on progress of the project planning using the [[CNM Website Projects]] wikipage. |
| | + | :# '''Present''' the progress, plans and possible concerns during the weekly [[CNMCyber This Week]] meetings. |
| | | | |
| − | :The [[CNM Cyber Orientation]] is designed to introduce promising ''Coords'' to the [[job market]], the ''Cyber'', its [[#Team|Team]], services, and the ''Cloud''. | + | : The project planning efforts shall start no later than completion of product wikipage's [[#Sprint|Sprint]] and end when a [[#Sprint|Sprint]] of the project wikipage development is completed. |
| | | | |
| − | ===Coords' placement=== | + | ===Doing to move forward=== |
| − | : ''Main wikipage: [[CNM Cyber Placement]]'' | + | : To start a new [[DREPD]] cycle, the ''Devs'' shall start the doing to move forward activities. This involves coding, designing, and testing the website with the help of the steps below: |
| | + | :# '''Act''' on the plan while doing what is planned such as creating prototypes, producing components, etc. |
| | + | :# '''Test''' the deliverable and, if necessary, its parts. |
| | + | :# '''Observe''' real situations, while detecting what hasn't been expected. |
| | + | :# '''Collect''' data related to the deliverables under development and their production. |
| | + | :# '''Analyze''' the collected project data while organizing that data on [[CNM Wiki]]. |
| | + | :# '''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. |
| | + | :# '''Treat''' creation of deliverables as primary source of data to revisit the [[#Researching the grounds|Researching the grounds]] activities. |
| | + | :# '''Revisit''' the [[#Researching the grounds|Researching the grounds]] activities when new data or new sources of data emerges in order to revisit further the [[#Envisioning the results|Envisioning the results]] and [[#Planning the production|Planning the production]] activities. |
| | + | :# '''Report''' on progress of the plan executing using the [[CNM Website Projects]] wikipage. |
| | + | :# '''Present''' the progress, plans and possible concerns during the weekly[[CNMCyber This Week]] meetings. |
| | | | |
| − | : The ''Placement'' is designed to introduce the learners to various positions, help to select the promising one, and place the learner as an apprentice into both the job and educational program. In their practice, the learners work as the ''Coords''. | + | :''Devs'' can create prototypes using this plan: |
| | + | :# Create a separate wiki page for each section of this wiki page, such as <code>[Domain-name] content</code>, <code>[Domain-name] design</code>. |
| | + | :# On the <code>[Domain-name] content</code> page, create the future possible website pages and their sections, such as the Landing page, Header, Footer, About us section, Our offers section, etc. |
| | + | :# A new wikipage is also created for each section, how to name them and what a category to create, read [[CNM Website Developer#Wiki-based prototype|here]]. |
| | + | :# Also, each section should have a description of the expected design and page format the same as the content. To see roughly what this design format should look like, visit [[iDosvid.com design]]. |
| | + | :# Design is a big part of website development, and can be considered a separate project, so the design page should also have sections of Requirements (Business, Stakeholder's, Technical) and States. |
| | + | :# To visualize the result described in the wiki, you need to transfer website textual content from CNM Wiki to a CMS-based prototype. Placeholders shall be used for those audiovisuals that haven't been developed yet; lorem ipsum shall be used to substitute future texts. Detailed instructions on CMS will be written separately for each CMS. |
| | + | ::At this stage, you can work in a team with other developers or coordinators. And you need to discuss requirements and preferences for content and design with the customer. |
| | | | |
| − | : The ''Coord'' is a temporary position, limited by the duration of the ''Placement''. Not everyone is attracted to work on creating something new. Not everyone is able to work in conditions of uncertainty. | + | : The project execution efforts shall start no later than completion of project wikipage's [[#Sprint|Sprint]] and end when the [[CNMCyber website]] becomes a [[market exchangeable]]. The ''Devs'' though progress websites to only [[minimum viable product]]s ([[minimum viable product|MVP]]s). |
| − | :* If the job of the ''Coord'' suits the participant, he or she moves towards the business analyst, systems engineer, partner coordinator, event organizer, information structure or solution creator, product or user experience designer, and product, information resources or development manager, and other occupations in projects.
| |
| − | :* If unable or unwilling, the participant is promoted to Contract or Systems Administrator, Usability Analyst, Accountant, Graphic Designer, Operations Engineer, Purchasing, Account Manager, and Procurement Manager and other occupations in operations.
| |
| | | | |
| − | : During the ''Placement'', students should be introduced to different professions from a programmer to an accountant. The specialty will be selected based on the results of the practice, and then it will be necessary to select a curriculum with a partner and organize an internship. We hope to organize the internship ourselves, but it will be difficult to replace educational institutions. Nothing unreal is foreseen, but everything needs to be worked out. Until the third course is ready, the ''Coords'' can work on it. | + | :To get a website as an [[Minimum viable product]], ''Devs'' can: |
| | + | :#Contact the [[CNMCyber Coordinator|coordinators]] to hire people, for those projects that you or your fellow developers can't do yourself after the prototyping project, mostly designers. |
| | + | :#Work on software that powers websites, when in your and the customer's opinion, the design and content are ready. If you know HTML5, CSS and JavaScript or have a good knowledge of some CMS - you can do it yourself. Or you can ask the coordinators to hire a Frontend Developer. |
| | + | :#Manage [[SEO]] and integrate the website into the [[WWW]]. Here you also have options to do it yourself or hire a specialist. |
| | | | |
| | ==See also== | | ==See also== |
| | ===Related lectures=== | | ===Related lectures=== |
| − | :*[[Vacancies at CNM Cyber]] | + | :*[[Vacancies at CNMCyber]] |
| | | | |
| − | [[Category: CNM Cyber Welcome Session]][[Category: Articles]] | + | [[Category: WorldOpp Orientation]][[Category: Articles]] |
