To organize testing and prioritize our effort, we need to map Krita and assign priorities to individual parts of the application. The output of this work will be the component/priority matrix.

To assemble the component/priority matrix:

1. Break down Krita into around 30-40 high-level components (a component may be a feature, functionality, code function, data files, ...). Every component is a row in the matrix.
2. For every component, fill out the columns in it’s row:
   1. Strategic. Is this our main selling point? Is this something no other product has? If the answer is yes, mark the “Is it strategic?” column.
   2. Technical considerations. What are the technical considerations tied to this component? If there is anything important or outstanding, add relevant keywords to the “Technical considerations” column. The keywords and their meaning are listed in the “Table of Technical considerations” below.
   3. Priority. Should this component be given preferential treatment? If yes, mark the component as “High” priority in the respective column. Less important components can be marked as “Low”. For everything else there is “Normal”. Skimp on the “High” priority: the testing resources are rather scarce at the moment.
   4. For any kind of notes there is the “Notes” column.

Table of Technical considerations

The work-in-progress matrix is available in a google sheet here: https://docs.google.com/spreadsheets/d/1civb1_5FqJp8eG5Tyi0WjfAV4dOtp4Bn8I22sbUjTLg/edit?usp=sharing

The component/priority matrix will of course grow with Krita over time. It’s not done once, but rather needs to be revisited with every new version we release.