Difference between revisions of "What the DevOps Is"
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[File:Cnm-digital.png|400px|thumb|right|[[ | + | [[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]][[What the DevOps Is]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of the '''[[Digital Transformations]]''' [[lesson]] that introduces its participants to [[CNM Lab]]. This ''lesson'' belongs to the [[CNMC for Experience]] session of [[EmployableU Concepts]]. |
| Line 8: | Line 8: | ||
===Script=== | ===Script=== | ||
| − | :Many [[enterprise]]s distinguish [[ongoing | + | :Many [[enterprise]]s distinguish [[ongoing operation]]s or so-called ''old businesses'' and [[project]]s or so-called ''new businesses''. [[DevOps]] is an engineering practice that merges both. |
:In ''DevOps'', [[new product development]] or the '''Dev''' part organically feeds [[operations]] or the '''Ops''' part and, vice versa, the ''operations'' feed their further development. A framework that represents a chain of phases of ''DevOps'' is called [[DevOps process]]. | :In ''DevOps'', [[new product development]] or the '''Dev''' part organically feeds [[operations]] or the '''Ops''' part and, vice versa, the ''operations'' feed their further development. A framework that represents a chain of phases of ''DevOps'' is called [[DevOps process]]. | ||
| Line 14: | Line 14: | ||
:Depending on [[organizational culture]], technology, and other factors, these phases may vary. In the development loop, they may include planning, building, and verifying. In the operations loop, the phases may include deploying, using, and monitoring in order to start planning a new development. | :Depending on [[organizational culture]], technology, and other factors, these phases may vary. In the development loop, they may include planning, building, and verifying. In the operations loop, the phases may include deploying, using, and monitoring in order to start planning a new development. | ||
| − | : | + | :[[CNMCyber Team]] has developed its [[CNMCT DevOps process]]. In its ''observe and envision'' phase, [[product epic]]s are drafted on [[CNM Wiki]]. In its ''define'' phase, [[product owner]]s shall publish on [[CNM Page]] those ''epics'' that they approve. In its outline phase, [[CNMCyber Coordinator]]s draft [[user story|user stori]]es on [[talk page]]s of [[CNM Wiki]]. In the ''prioritize'' phase, [[product owner]]s include select ''stories'' in the [[sprint backlog]]. If needed, mock-ups emerge as deliverables from the prototype phase. In the ''create and test'' phase, the ''Team'' build [[minimum viable product]]s ([[MVP]]s). [[Marketable product]]s emerge as deliverables from the release and deploy phase to be observed and re-envisioned. In this way, the loops re-start again. |
:The [[CNMCN DevOps process]] is built with a chain of tools that [[CNM Page]], [[CNM Wiki]], and [[CNM Lab]] offer. This chain is called [[CNMCT DevOps toolchain]]. Each of any [[DevOps toolchain]] shall fit one of the phases of a [[DevOps process]]. So does [[CNM DevOps toolchain]]. | :The [[CNMCN DevOps process]] is built with a chain of tools that [[CNM Page]], [[CNM Wiki]], and [[CNM Lab]] offer. This chain is called [[CNMCT DevOps toolchain]]. Each of any [[DevOps toolchain]] shall fit one of the phases of a [[DevOps process]]. So does [[CNM DevOps toolchain]]. | ||
| Line 20: | Line 20: | ||
:The bulk of development of [[CNMCT DevOps process]] occurs in two [[development hub]]s. The ''hub'' is a center of development in which two or more developing parties work on one or more [[deliverable]]s. | :The bulk of development of [[CNMCT DevOps process]] occurs in two [[development hub]]s. The ''hub'' is a center of development in which two or more developing parties work on one or more [[deliverable]]s. | ||
| − | :At [[CNM Wiki]], | + | :At [[CNM Wiki]], [[CNMCyber Team]] creates the [[requirement]]s that reflect what needs to be developed. These ''requirements'' include [[product epic]]s, [[epic story|epic stori]]es, [[user story|user stori]]es, and [[requirements specification]]s. This ''hub'' is open to the general public 24/7. |
| − | :At [[CNM Lab]], the [[Friends Of CNM]] leads implementations of those ''requirements'' that | + | :At [[CNM Lab]], the [[Friends Of CNM]] leads implementations of those ''requirements'' that [[CNMCyber Team]] created. This private ''hub'' is used to develop viable [[computer file]]s, [[software]], as well as security-sensitive documentation. |
===Key terms=== | ===Key terms=== | ||
Latest revision as of 22:13, 29 October 2023
What the DevOps Is (hereinafter, the Lectio) is the lesson part of the Digital Transformations lesson that introduces its participants to CNM Lab. This lesson belongs to the CNMC for Experience session of EmployableU Concepts.
Content
The predecessor lectio is What CNM Agile Is.
Script
- Many enterprises distinguish ongoing operations or so-called old businesses and projects or so-called new businesses. DevOps is an engineering practice that merges both.
- In DevOps, new product development or the Dev part organically feeds operations or the Ops part and, vice versa, the operations feed their further development. A framework that represents a chain of phases of DevOps is called DevOps process.
- Depending on organizational culture, technology, and other factors, these phases may vary. In the development loop, they may include planning, building, and verifying. In the operations loop, the phases may include deploying, using, and monitoring in order to start planning a new development.
- CNMCyber Team has developed its CNMCT DevOps process. In its observe and envision phase, product epics are drafted on CNM Wiki. In its define phase, product owners shall publish on CNM Page those epics that they approve. In its outline phase, CNMCyber Coordinators draft user stories on talk pages of CNM Wiki. In the prioritize phase, product owners include select stories in the sprint backlog. If needed, mock-ups emerge as deliverables from the prototype phase. In the create and test phase, the Team build minimum viable products (MVPs). Marketable products emerge as deliverables from the release and deploy phase to be observed and re-envisioned. In this way, the loops re-start again.
- The CNMCN DevOps process is built with a chain of tools that CNM Page, CNM Wiki, and CNM Lab offer. This chain is called CNMCT DevOps toolchain. Each of any DevOps toolchain shall fit one of the phases of a DevOps process. So does CNM DevOps toolchain.
- The bulk of development of CNMCT DevOps process occurs in two development hubs. The hub is a center of development in which two or more developing parties work on one or more deliverables.
- At CNM Wiki, CNMCyber Team creates the requirements that reflect what needs to be developed. These requirements include product epics, epic stories, user stories, and requirements specifications. This hub is open to the general public 24/7.
- At CNM Lab, the Friends Of CNM leads implementations of those requirements that CNMCyber Team created. This private hub is used to develop viable computer files, software, as well as security-sensitive documentation.
Key terms
- DevOps, DevOps process, CNMCT DevOps process, DevOps toolchain, CNMCT DevOps toolchain, development hub, computer file (digital file)
Closing
- Is the concept of CNMCT DevOps process explained well?---Yes/No/I'm not sure
What Requirements Are is the successor lectio.
