Benetech Engineers Questions

[clapierre]

In filling out the ICT section of the Maturity Model Excel Spreadsheet, our Engineers had these two questions.

1. 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. Where there discussions of how these might be framed for small organizations? (e.g. we do not have 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?)
2. 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?

[clapierre]

From meeting 5/24/23
Fazio: Not the size of the time. May affect recourses but nothing is prohibitive. Okay to stay at level of maturity. I would leave it there as an option. Not punitive. Publishing is up to you

jlkline: Recourses is broad term – human, training, tools. That’s maybe how we want to answer. Not specific but devs should have all recourses needed.

SusiPallero: Even if not formal you have a process. You’re always running the same task – may apply even if the team is not huge. Write it to be clear that it applies sot regular activities.

jlkline: Sm org man not have process. Its about consistency and that is a process and they could claim. Ie. design reviews every time.