Aim: everyone with software responsibilities is competent, empowered and able to carry out their tasks correctly, efficiently and consistently, to high quality and under varying conditions. The key competencies per role are those of Annex B; any extra experience, capability or qualification a role needs is written into the Software Quality Assurance Plan. The supplier keeps documented evidence of each person's technical knowledge, qualifications, experience and training to show a fit safety organisation, and maintains procedures for managing competence against the roles in line with its quality standards. Once competence has been shown to an Assessor or through certification, each individual keeps it up and develops it further, which may be evidenced by a logbook of the activity being done correctly and of added training (the competence clause 7.2 of EN ISO 9001:2015 or of ISO/IEC/IEEE 90003:2018 may serve). Responsibilities follow Tables B.1 to B.9.
This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.