Maturity Model Task Force Minutes
Minutes | Topics | Resolutions
Display information about these minutes
Showing minutes for channel(s):
2024
- 12 June: Maturity Model
- 5 June: Maturity Model
- 29 May: Maturity Model Task Force
- 22 May: Maturity Model
- 15 May: Maturity Model
- 1 May: Maturity Model
- 24 April: Maturity Model
- 17 April: Maturity Model
- 10 April: Maturity Model
- 3 April: Maturity Model
- 27 March: Maturity Model
- New Business
- Maturity Model Scoring Subgroup Update
- Github Issues 43, 78, 85, 102, 103, 104 (Usability doc feedback)
- Github Issue #101 What do we mean with 'aspects'? Used in two ways i.c.w. 'dimensions'
- Github Issue #107 Definition of "Full maturity" needs to be adjusted, as there is no need to optimize anymore by then
- 13 March: Maturity Model
- 28 February: Maturity Model
- 14 February: Accessibility Maturity Model Task Force
- New Business
- Github Issues 43, 78, 85, 103, 104 (Usability doc feedback)
- Maturity Model Scoring Subgroup Update
- Github Issue #103 Where are the "Outcomes" in the Maturity Model Structure?
- Github Issue #102Proof Point definition to be adjusted to fit under an Outcome
- Github Issue #101 What do we mean with 'aspects'? Used in two ways i.c.w. 'dimensions'
- 7 February: Maturity Model Task Force
- New Business
- Github Issues 43 and 85 (Usability doc feedback) https://docs.google.com/document/d/1Wrhomdc2gJWIkDPOveiH3_ig1bddTMonEhIDZIzohrc/edit#heading=h.93exgeg396jg
- Maturity Model Scoring Subgroup Update
- Github Issue #78 3.3.2 Ratings for Evaluation - Support section: why is knowledge and skills mentioned (Update from Charles, stacey)
- Github Issue #104 Proof points = Written or tangible evidence, according to definition, not an 'or' / 'other' part / sub-section (will usability do address?)
- Github Issue #103 Where are the "Outcomes" in the Maturity Model Structure?
- 31 January: Maturity Model Task Force
- 24 January: MAgenda+ New Business
- 17 January: Accessibility Maturity Model Task Force
2023
- 20 December: Maturity Model
- New Business
- Discuss timeline for Maturity Model release Candidate, next year or are we just expectations.
- Github Issue #43 & #83 Usability Update
- Github Issue #85 Inconsistencies in Inactive ratings for various dimensions
- Github Issue #89 ICT Development Lifecycle ratings outcomes aren't stated like the outcomes are in Silver
- 13 December: Maturity Model
- New Business Agenda+ CSUN (should we meet) Agenda+ Working Draft end of year update Agenda+ Do we cite a particular WCAG profile as a conformance target? It seems reasonable to cite that WCAG profile A would arguably be in (Lionel’s question) Agenda+ MM Draft usability update (GitHub Issue 43) Agenda+ GitHub Issue #132 (see previous minutes) Agenda+ Github Issue #79 Section 3.3.2 Rating for evalu
- New Business
- Github Issue #83 Section 3.7.2 Ratings for Evaluation - Culture: proof points vs. ratings mismatch
- Github Issue #85 Inconsistencies in Inactive ratings for various dimensions
- 6 December: Maturity Model Teleconference
- 29 November: maturity model
- 15 November: Maturity Model
- 1 November: Maturity Model
- new business
- Equity Considerations Estimate
- MM Draft usability update
- GitHub Issue #145 Linking would make it easier to use
- GitHub Issue #153 The effectiveness of knowledge/skill acquisition should be measured
- Github Issue #83 Section 3.7.2 Ratings for Evaluation - Culture: proof points vs. ratings mismatch
- 25 October: Maturity Model
- Equity Subgroup Update from Sheri
- General discussion of the term 'proof points'
- New Business
- GitHub Issue #140 Executive sponsor in place vs Executive leadership in place
- GitHub Issue #142 Business strategy includes accessibility as a market differentiator
- GitHub Issue #143 communities of practice. Question, communities we serve
- 18 October: maturity model
- 4 October: Maturity Model
- New Business
- GitHub Issue 21 Flow of "A Maturity Model is:" need a little bit of love
- GitHub Issue #28 No "Appendix" present for "1.3 Existing Research" (Delete?)
- GitHub Issue #43 Should "proof points" and "ratings for evaluation" sections be combined for clarity?
- GitHub Issue #45 Would it be better to avoid the overlap between section 3.3 and sections 3.1 and 3.2?
- 20 September: Maturity Model
- 30 August: Maturity meeting August 30th 2003
- 23 August: Maturity Model
- 16 August: Maturity Model Task Force
- 9 August: (MEETING TITLE)
- 2 August: Maturity Model
- 19 July: Maturity Model Task Force Weekly Teleconference, 19 July 2023
- 12 July: Maturity Model
- 5 July: Maturity
- 28 June: Maturity Model
- 14 June: Msturity Model
- 7 June: Maturity Model
- Spreadsheet Update
- TL;DR Update from Stacey: https://lists.w3.org/Archives/Public/public-maturity/2023Jun/0000.html
- Support Dimension Update https://lists.w3.org/Archives/Public/public-maturity/2023May/0019.html
- Stakeholder Document Update
- Publication Update Update
- support dimension update
- publication update
- 24 May: W3C Accessibility Maturity Model
- ghrulhub
- Under 3.4.1.2 Development category of proof points, the examples of “Accessible developer implementation resources” seem more about information. Where might you consider software and hardware tools that help with accessible development, such as access to screen readers or switches?
- Continue with Susanna’s updates to Support Dimension https://lists.w3.org/Archives/Public/public-maturity/2023Apr/0013.html
- Continue with Stakeholder Document Update – Lionel, Jeff, and Stacey
- 17 May: Maturity Model Teleconference
- 10 May: Maturity Model
- 3 May: Maturity Model
- Discuss any activities the Task Force might want during TPAC in September. Are there other W3C WG we want to have a joint meeting with? What agenda for those meetings? Note this is NOT about any breakout sessions we might want to hold on Wednesday of TPAC
- Review Susanna’s updates to Support Dimension https://lists.w3.org/Archives/Public/public-maturity/2023Apr/0013.html
- Some of the design process questions seem to make sense for large organizations where process, templates and checklists are more formal parts of a large organization. Were there discussions of how these might be framed for small organizations? (e.g. not having a formal design review process, but we do have design reviews; is the way forward to become more formal even if the team has three members?)
- Under 3.4.1.2 Development category of proof points, the examples of “Accessible developer implementation resources” seem more about information. Where might you consider software and hardware tools that help with accessible development, such as access to screen readers or switches?
- 19 April: (MEETING TITLE)
- 12 April: (MEETING TITLE)
- 29 March: Maturity Model Task Force
- 22 March: (MEETING TITLE)
- 1 March: Maturity Model Task Force
- 15 February: Maturity Model
- 8 February: Maturity Model Task Force
- 25 January: Maturity Model
- Task Force CFC Update
- Intersection of Equity SubGroup and Maturity Model
- Prioritizing Jason White’s Issues, Recap of Last Week’s Meeting
- Github Issue #42 Section 3.1 (communication) should be clarified.
- Github Issue#15 Potentially unfamiliar terms/abbreviations in section 3 should be defined/explained.
- Github Issue#17 The application of the model to decentralized organizations could be clarified, as could the nature and roles of the valid outputs of applying the model in an evaluation.
- 18 January: Maturity Model Subgroup
- Discussion on Sheris mail Maturity model homework
- Github Issue #18 What's the relationship with ISO/IEC 30071-1:2019?
- Github Issue #52 Section 2 (and elsewhere, if necessary): broaden the range of standards relevant to the maturity model.
- Github Issue #91 Proof points should include measures of the extent to which processes are successful
- 11 January: Maturity Model Subgroup Teleconference
- 4 January: Maturity Model Subgroup
2022
- 14 December: Maturity Model
- 7 December: Maturity Model Teleconference
- 30 November: Maturity Model Teleconference
- 16 November: Maturity Model Subgroup
- 9 November: Maturity Model
- 2 November: (MEETING TITLE)
- 19 October: Maturity Model Subgroup
- 12 October: Maturity Model
- 5 October: Maturity Model Subgroup
- 28 September: Maturity Model
- 7 September: (MEETING TITLE)
- 17 August: Maturity Model
- 10 August: (MEETING TITLE)
- 3 August: Maturity Model
- 20 July: Maturity Model
- 29 June: Maturity Model
- 22 June: Maturity Model
- 15 June: Maturity Model
- 8 June: Maturity Model
- Check in with Jeff about generic Proof Point statement about cross-referencing
- Check in with Janina on any pending issues Agenda+ Check in with Jeff on deleting redundant text in Knowledge and skills reconciling his edits Agenda+ review generic K&S statement Agenda+ Check in with Mary Jo on github merger Agenda+ Check in with Jake on his final review
- review generic K&S statement
- Check in with Mary Jo on github merger
- Syncing to ISO 30071
- future of this group
- 1 June: Maturity Model
- 25 May: Maturity Model
- 18 May: Maturity Model
- 11 May: Maturity Model
- Check in with Jeanne and Janina on sorting out group ID and zoom
- We Check in with Sheri on document language change to US English
- Check in with Mary Jo on grammar review
- Check in with Sheri on adding generic sentence to each dimension “Training programs have been established and ongoing to ensure necessary skills for this dimension”
- Check in with Mary Jo on capitalization of defined terms
- 4 May: Maturity Model
- 27 April: (MEETING TITLE)
- 20 April: W3C Accessibility Maturity Model
- 13 April: Maturity Model