Types of software changes in discussion

From Cynefin.io
Jump to navigation Jump to search

The community can contribute and discuss options over a number of different areas associated with the Workbench.

Different contributors will have different interests and skills to bring to the discussions and these represent a current thinking in terms of demarcating such discussion areas (open to additional ideas).

These are:

Improvements to existing framework and modules

At any point in the deployment history of the Workbench improvements in functionality may be identified. Examples are (not complete):

  1. Improved wording.
  2. Improved information content. An example would be discussing messages or counts, percentages that might improve an existing display.
  3. Improved/extended user configuration options. An example might be giving the user a choice to whether a brush on a triad will keep or remove the shaded brush area after mouse removal. Currently it is removed by default.
  4. Minor layout changes within a display that will enhance its readability.
  5. Changes to ordering of display

These are discussed here

New Module Ideas

There exists a host of different ideas around new modules ideas. These should be one of (or combined, hopefully)

  1. An analyst user or client real-world problem definition or question that requires an open discussion of various ways in which this issue/question/problem can be supported in the Workbench.
  2. A statistical or algebraic idea that seems to be potentially useful, and thus of interest to explore, experiment and test.

This area is discussed here

UX and UI Improvements

While the structure of the Workbench does not fundamentally change, and it should be deployed using the standard CognitiveEdge colours, fonts and logos, there is still a lot of areas where useful discussion and input is needed.

This area is discussed here

Workbench Architectural Change Requirements

This is the R and R-Shiny technical area, and involves discussions and coding in the Workbench Framework.

This is discussed here