Update / NEWEST DLC Spreadsheet - Step 2

[jake-abma]

I've started a "NEW" approach for DLC.

Based on updated spreadsheet:
https://docs.google.com/spreadsheets/d/1fzPlHjHIaSQn9GvpJd86SDpV49U8Beg_iXj6K5aeyGg/edit#gid=627214460

And:
https://w3c.github.io/maturity-model/#development-lifecycle-proof-points

The reason for the 'updated' approach is that to my opinion the structure for 'categorization' as is right now is 'phase' based (Design, Development, User Experience, Quality Review Through Release, and one from another perspective... ICT Development Training)

This is not an Outcome based setup and doesn't fit the structure of the other Dimensions.

The challenge with DLC is that the 'flow' or 'phase' based explanation is a nice one to have to present what needs to be done when and where, but overlap, duplications, grey area's, and other organizational approaches, make this seem more fit as 'tags' to Outcomes or Proof Points.

Short examples are:

1. We don't have QA in our organization, so who's responsible now?
2. UX and Design is intertwined, so a clear separation is not what we have
3. "Quality Review Through Release" and then "Testing process includes automated accessibility testing" is not per se part of the 'release' but in development already
4. Checklists for Design, UX, and Development might be the same or have great overlap, so where does it fit?
5. Etc. etc.

It doesn't mean for DLC the 'phase' approach is not valuable, instead it is, but for this reason I'll setup a "Outcome based approach with a 'phase tagging' column. This way it will fit nicely with the one already worked out, Knowledge and Skills, while preserving all work done.

Next step will be optimizing the "outcomes" and "Proof Points" based on all present now.

NEWEST OUTCOME ICT DLC Evidence - Jake
https://docs.google.com/spreadsheets/d/1fzPlHjHIaSQn9GvpJd86SDpV49U8Beg_iXj6K5aeyGg/edit#gid=1296637612

!!! NEW VERSION and Simplified Spreadsheet / Table for the Dimensions !!!
https://docs.google.com/spreadsheets/d/1sbfh2Kone3Poe9CGw-llOriBPK3GnGDj3YY2GmDZH80/edit#gid=600224467

[jake-abma]

ps. see the example image below I also used to get a grip on the Dimension (others were used too but always good to provide an example...)

Multiple assets/artefact are 'shared' for phases, or only slightly tweaked for the phase / person in the phase... to prevent duplications or being to prescriptive of responsibilities a tagging approach for phases seems the better approach.

[jake-abma]

The Outcomes and Proof Points are updated!

The mapping between the 'older' and 'newer' ones I will attach as a Word doc.
DLC NEWEST.docx

The result can be seen at:
https://docs.google.com/spreadsheets/d/1fzPlHjHIaSQn9GvpJd86SDpV49U8Beg_iXj6K5aeyGg/edit#gid=1296637612

[jake-abma]

When in progress / evaluated, the spreadsheet may look like this

FLOW NEWEST OUTCOME ICT DLC Evidence - Jake:
https://docs.google.com/spreadsheets/d/1fzPlHjHIaSQn9GvpJd86SDpV49U8Beg_iXj6K5aeyGg/edit#gid=1019313952

[jake-abma]

UPDATED "Integrate Testing and Review Processes" order to reflect a bit more the phase steps... from "Idea Conception, Design, UX, Dev, to QA..."

[jake-abma]

Changed:

Utilizing assistive technology for testing

To:

Utilizing Assistive Technology and Tools for testing

[jake-abma]

As 'creating' and 'maintaining' are already part of the Rating/Levels (Launch... optimize) and as the Design System may be separated in a Design Library and Component library, I've changed the Outcome text:

Changed:

Creating and Maintaining Design / Component System

To:

Developing Design and Component System

[jake-abma]

Changed:

Accessibility code features are implicitly secured

To:

Accessibility component features are implicitly secured

[jake-abma]

!!! NEW VERSION and Simplified Spreadsheet / Table for the Dimensions !!!
https://docs.google.com/spreadsheets/d/1sbfh2Kone3Poe9CGw-llOriBPK3GnGDj3YY2GmDZH80/edit#gid=600224467