Developments at the Wiki

CNM Cyber suites

Developments at the Wiki (hereinafter, the Lectio) is the lesson part of Wiki Editing Essentials lesson that introduces its participants to wiki edit concepts. This lesson belongs to the CNMCT Entrance section of the CNM Cyber Placement.

Content

The predecessor lectio is What Wiki Categories Are.

Script

CNM Wiki is a development hub. Here, the CNM Cyber Team develops requirements for future CNM Cyber services and CNM apps. The software and some other deliverables are further developed at another hub called CNM Lab.

Two categories of wikipages are used in the development of requirements.

First, those pages that belong to the Category:Product Epics are utilized to express product epics. Secondly, those pages that belong to the Category:Sprint Backlogs are utilized to express the results of Sprint Zeros.

Any development starts with a vision of what needs to be developed. Before CNM Cyber was developed, somebody imagined what CNM Cyber could be, what it could do, and who would use it. The content that describes a future work product, its part, or feature is called product epic.

The Category:Software Epics is reserved to develop requirements for CNM apps such as CNM Wikiware, while the Category:Service Epics is reserved for requirements for CNM Cyber services such as CNM Wiki. Both categories are subcategories of the Category:Product Epics.

A bigger product epic should further be divided in smaller user stories. Eventually, one story presents a feature that can be developed in one Sprint. The stories and their drafts are published at those Talk pages that are attached to the Category:Product Epics.

At CNM Wiki, a Talk page is any wikipage that is attached to a content page. Talk pages can be used for discussions related to the "content page" matters; Talk pages can be accessed via the "Discussion" tab in the page type menu.

Besides requirements, the Talk pages of CNM Wiki may be used to publish any notes about the content pages and any content drafts.

Collectively, those user stories that are developed for one work product are called a product backlog. One user story that is included in the backlog is called product backlog item or PBI.

After the backlog is developed, project coordinators and product owners together decide what PBIs would be developed next. This phase is called Sprint Zero. Those PBIs that are selected become sprint backlog items or SBIs. All together, they are called sprint backlog and published at the wikipages that belong to the [[Category:

The attached Talk pages are utilized for development iterations or sprints.

, as well as all the other deliverables that need to be developed for the Project, are going to be developed in a few Sprints, which will continue until the particular target deliverable, its part, or feature is completely developed. These Sprints make up the development cycle as follows:

   Product epic Sprints (Sprints A0+) that aim to produce a product epic or a general description of the service or any product such as a software application that supports that service.
   User story Sprints (Sprints B0+) that aim to produce a user story or a specific description of the desired function from the end-user point of view. Product epics may serve as a source for user stories.
   SBI Sprints (Sprints C0+) that aim to produce a Sprint backlog through including user stories as PBIs into a product backlog and grooming that backlog.
   Prototype Sprints (Sprints D0+) that aim to produce a prototype of a future deliverable based on a SBI that is taken out of the Sprint backlog.
   MVP Sprints (Sprints E0+) that aim to produce a minimum viable product (MVP) out of the tested prototype.
   Marketable product Sprints (Sprints F0+) that aim to produce a marketable product as an improved MVP.

Key terms

Talk page, Category:Product Epics, Category:Software Epics, Category:Service Epics

Closing

The successor lectio is What Project Work Is.