Difference between revisions of "What CNM Agile Is"

From CNM Wiki
Jump to: navigation, search
 
Line 4: Line 4:
  
 
|2||'''[[CNM Agile]]''', [[project management]], [[Agile methodology]]; '''[[development hub]]''', [[document]], [[computer file]], [[software]]; '''[[requirement]]''', [[product epic]], [[user story]]; '''[[requirements specification]]''', [[CNM Cyber requirements]], [[CNM Cloud requirements]]
 
|2||'''[[CNM Agile]]''', [[project management]], [[Agile methodology]]; '''[[development hub]]''', [[document]], [[computer file]], [[software]]; '''[[requirement]]''', [[product epic]], [[user story]]; '''[[requirements specification]]''', [[CNM Cyber requirements]], [[CNM Cloud requirements]]
 +
 +
:'''[[CNM Agile]]'''. A [[product development framework]] that represents an adaption of the [[Agile methodology]] to the learning and testing needs of the [[CNM Cyber Team]].<div style="background-color:#efefef; padding: 5px; margin: 15px;">
 +
:*'''[[Project management]]'''. Practice and a set of [[concept]]s that are based on that practice that define culture of managing of [[project]]s from the moment when the [[project manager]] is authorized and up to the project closing. ''Project management'' aims to achieve specific goals and to meet specific success criteria. This ''management'' often has a defined beginning (often, constituted by funding) and ending (often, constituted by bringing desired [[deliverable]]s to their beneficiary).
 +
:*'''[[Agile methodology]]'''. A [[product development framework]] that is based on development of deliverable increments in frequent [[iteration]]s based on evolving [[requirement]]s.</div>
 +
 +
:'''[[Development hub]]'''. A center of development in which two or more developing parties work on one or more [[deliverable]]s.<div style="background-color:#efefef; padding: 5px; margin: 15px;">
 +
:*'''[[Document]]'''. A single piece of [[data]] that represents one or more [[idea]]s, [[change]]s, [[process]]es, [[product]]s, and/or [[system]]s. Those ''documents'' that are created to be used by people include bills of sale, books, instructions, memos, messages, national constitutions, passports, [[wikipage]]s, written articles, etc. In [[information technology]], a ''document'' can be a [[computer file]] or a [[system document]] such as a [[database record]]. [[Web browser]]s use [[web document]]s to display [[webpage]]s, etc.
 +
:*'''[[Computer file]]''' ([[digital file]]). Any [[document]] that is created as a computer resource and is stored discretely in a [[computing device]].
 +
:*'''[[Software]]'''. One or more [[computer file]]s that present the data and programs that make the [[computing device]] produce specified results.</div>
 +
 +
:'''[[Requirement]]'''. An expressed demand, desire, expectation, and/or wish to have or not to have a certain [[product]] and/or a certain capability, condition, feature, and/or property. The plural term, [[Requirement|requirements]], may refer to the aggregate of various ''requirements'' that the [[product owner]] or another authority for the ''requested product'' and/or its development [[process]] has approved, verified, and/or validated.<div style="background-color:#efefef; padding: 5px; margin: 15px;">
 +
:*'''[[Product epic]]'''. A detailed description of a proposed product that is designed to make its potential consumer understand what this product shall do. At [[CNM Cyber]], the ''Epic'' is any [[wikipage]] that describes a desired product.
 +
:*'''[[User story]]'''. A brief description of a [[solution requirement]] to a desired system that is written from the point of view of a [[customer]] or [[end-user]] of this system. In other words, the ''story'' is a high-level, informal, brief, non-technical description of a solution capability that provides value to its [[stakeholder]]. The ''story'' is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to implement it. <code>In order to ..., as a ..., I need to ...</code> or, using another format, <code>In order to [achieve some goal], as a [type of user], I need to [perform some task or execute some function]</code> is a generic example of the ''story''.</div>
 +
 +
:'''[[Requirements specification]]'''. A [[requirement]] in a form of technical description of a proposed [[system]].<div style="background-color:#efefef; padding: 5px; margin: 15px;">
 +
:*'''[[CNM Cyber requirements]]'''. The [[requirements specification]] for [[CNM Cyber]].
 +
:*'''[[CNM Cloud requirements]]'''. The [[requirements specification]] for [[CNM Cloud]].</div>

Revision as of 00:32, 20 April 2020

What CNM Agile Is

Digital Transformations

|2||CNM Agile, project management, Agile methodology; development hub, document, computer file, software; requirement, product epic, user story; requirements specification, CNM Cyber requirements, CNM Cloud requirements

CNM Agile. A product development framework that represents an adaption of the Agile methodology to the learning and testing needs of the CNM Cyber Team.
Development hub. A center of development in which two or more developing parties work on one or more deliverables.
Requirement. An expressed demand, desire, expectation, and/or wish to have or not to have a certain product and/or a certain capability, condition, feature, and/or property. The plural term, requirements, may refer to the aggregate of various requirements that the product owner or another authority for the requested product and/or its development process has approved, verified, and/or validated.
  • Product epic. A detailed description of a proposed product that is designed to make its potential consumer understand what this product shall do. At CNM Cyber, the Epic is any wikipage that describes a desired product.
  • User story. A brief description of a solution requirement to a desired system that is written from the point of view of a customer or end-user of this system. In other words, the story is a high-level, informal, brief, non-technical description of a solution capability that provides value to its stakeholder. The story is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to implement it. In order to ..., as a ..., I need to ... or, using another format, In order to [achieve some goal], as a [type of user], I need to [perform some task or execute some function] is a generic example of the story.
Requirements specification. A requirement in a form of technical description of a proposed system.