CNM Technology Board

The CNM Technology Board (hereinafter, the Board) is the part of the CNM Digital Team that approves or disapproves its strategy. The CNM IT Office supports the Board.

Organization

Key members

• Gary Ihar -- gary
• Michael Confoy -- michaelc

Meetings

Hybrid bi-weekly

Decisions

Majority; two weeks for a decision

Methodologies

We need someone to own tasks. If you own it and can do it all, great. If you will need more than one person on it, that should be noted once we have the tasks in the wiki or via response to this if necessary. For example, MichaelC is looking for someone that would like to do some of the work under his direction for the training task as it can be very useful learning experience as a software evaluation using a bake off is a common practice.

Deciding on ...

... team's endeavors

The Board approves or disapproves the strategy for the development of CNM Digital known as CNM Digital Transformation.

... team's services

The Board defines the portfolio of the services included into CNM Digital and the technology behind the services.

... the technology

The Board defines the CNM Cloud, which is the bundle of technology that supports CNM Digital.

Endeavors

New meeting model

Determine mechanism for virtual meetings, .i.,e., free

Backlog

Main wikipage: CNM Digital

Create backlog page or section of page on wiki with these tasks, who is lead on task and link to work on task.

I am willing to take task #3. For that I will need to coordinate with someone who can edit the wiki. Should be able to complete initial draft during a 1-hour working session on a Tuesday night. (If necessary, it could be done with much less time as a copy-paste from this email, but I would hope to have better quality than that.)

Seed wiki page with user stories ( friendsofcnm.org ): what is this Ken?

There is a question about task #10. Task #10 is to begin the process of creating project requirements in the form of user stories on one or more wiki pages. Each user story has a user story card which has a notes section with status information. Here is some information about that. The backlog email is a list of short descriptions of tasks or projects with some status information. That is a good place for us to start. Frequently Agile projects or Hybrid-Agile projects have task cards and/or story-cards describing the tasks to be completed. The tasks are often given as user stories in a certain form. (Sometimes these are on actual large index cards or post-it notes, but often they are on electronic task cards in a system like JIRA or a wiki or some other project management software system.)

So requirements are often actually "Agile Stories" describing the desired outcome at very high level in the form of completing the blanks in this sentence: "As a [blank <type-of-user>] I want [blank <some-goal-or-objective>] so that [blank <benefit-or-value>]". Example from government website: "As an Editor, I want a way to review content before it is published so that I can assure it is optimized with correct grammar and tone." [Retrieved from public website https://tech.gsa.gov/guides/user_story_example/ ]. All this is simpler when you see it than when you try to understand it from a descriptive paragraph.

(I think one of the wiki pages already has at least one user-story.)

New wiki software

   Migrate Wiki to TikiWIki on hold, see below
       LDAP
       Migrate
       Decision on migration path from MediaWiki to TikiWiki
       Decision on server setup/expert for setup
   Evaluate alternatives to Mediawiki in detail, determine what the wiki evaluation bake off should be, see below, Michael

Three Wiki solutions for evaluation:

Wiki software

First public release date

Latest stable release

Stable release date

Software license BlueSpice MediaWiki

31 March 2011

3.0.1

2019-01-17[±]

GPLv3 PmWiki

01/08/02

02/02/15

2019-05-13[±]

GPL Tiki Wiki CMS Groupware

9 October 2002

19.1

2019-02-14[±]

LGPL

Onboarding

   Document recruiting and orientation processes and/or best practices and/or recommendations for future
   Create instruction for beginner program coordinators as part of on-boarding process (CNM IT Project Coordinator)

Registration

   CNM registration project, Gary for volunteers
       Real accounts to database so user updates can happen with database
       Define how usability testing happens
       Registration of new volunteers on wiki

Training

   Technical links/sources as part of mentoring process: NIST for security, see below, Michael

   Work with Gary to determine Digital Ocean server deployment requirements
       Gary can provide ssh access to the Linux Ubuntu droplets
       DigitalOcean already has 3 droplets

NIST Security Links:

https://csrc.nist.gov/

https://www.nist.gov/cyberframework https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.04162018.pdf

https://www.nist.gov/sites/default/files/documents/2017/04/03/baldrige-cybersecurity-excellence-builder-v1.0.pdf

https://csrc.nist.gov/CSRC/media/Publications/sp/800-171/rev-2/draft/documents/sp800-171r2-draft-ipd.pdf https://csrc.nist.gov/CSRC/media/Publications/sp/800-171b/draft/documents/sp800-171B-draft-ipd.pdf https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171A.pdf https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-163r1.pdf

Q&As

I love to hear about the Board. Please tell me more.

Scroll to the top of this page and read. Ask specific questions when you have those.