Meeting minutes
<gb> /issues/193 -> #193
<gb> /issues/228 -> #228
New Business
JXZ: old spreadsheet vs. new spreadsheet metrics "has exec. sponshorship" if they have it does it mean optimized.
Charles: I would say this is fine and can be granular and additional notes can specify why its not in the optimized state if there is exec sponsorship or any of these type of binary proof points.
David: this is 1.0 so there is room for improvement.
JXZ: I am trying to get other organizations to do this maturity model, I will add an issue in Github on how to improve this.
Github Issue #228 Syncing proof points in the MM document and the assessment tool
<gb> /issues/228 -> #228
<gb> Issue 228 Determine if the proof points in the MM document and the assessment tool should be synced (by jeffkline)
Dr Keith: For these where there are discrepancies between sheet and document my vote would be to keep the document version.
Charles: +1
JXZ: think more broadly about different types of style guides.
Charles: what about "all style guides, such as ..."
Dr. Keith: "including but not limited to ..."
… artifacts vs. just work.
David: not a fan of using the term artifacts.
Neha: design assets.
Charles +1
<JXZ> +1 assets
SusiPallero: What kind of design outcome?
Jennifer: what about deliverables?
<SusiPallero> adding some options "design deliverables handed off to developers" or "design deliverables provided to developers"
David: accessibility Reviews added to spreadsheet
Dr. Keith: Jobs to be Done JTBD, different things that a user would do to complete a task.
JXZ: Maybe change to scenarios?
SusiPallero: I would remove JTBD for including people with disabilities. its a framework, its user agnostic.
… so we can remove that portion.
… I wouldn't mention a framework, consider people with disabilities is important.
Jennifer: we don't want to be too prescriptive. subset of user needs.
… User Stories / User Needs / Scenarios instead.
SusiPallero: Personas. or any other framework / exercise used. incl. people with disabilities.
SusiPallero: Analogy: Design systems from atoms -> organisms, so components are like atoms, but you can loose a11y when you combine them to create organisms.
Dr. Keith: so many organizations think of components at the engineering level. So we may want to go to "elements" or something which incorporate all those considerations.
<SusiPallero> “Accessibility considerations are integrated into individual components of the design system as well as into their composition within higher-level structures.”
janina: are we talking about web design.
David: well this is ICT section so this is web design.
… May need to separate this into 2
Susi: I posted in IRC an option
David: Yes thats great.
Janina: I agree
Dr_Keith: Agile, definition of done, seems too agile specific. can we get this level without getting into agile frameworks.
SusiPallero: Maybe Unit testing requirements. remove definition of done. is too prescriptive.
<SusiPallero> "Accessibility is validated as part of the unit testing process"
Janina: accessibility signoff / approval
SusiPallero: you have to test them should accessibility part of the unit testing.
Charles: Accessibility Gate: This term directly implies a specific stage in the development process where accessibility is rigorously evaluated, and the product cannot proceed to the next phase or release without passing this gate. It signifies a mandatory checkpoint for accessibility compliance.
or
Accessibility Release Criteria: This term refers to the specific accessibility standards or requirements that must be met before a product can be released. This creates a clear set of items that must be checked, and passed before a product can be moved to a released state.
Jennifer: Release criteria and sign-off.
<JXZ> quit