2. Organisational Context and Governance
2.1 Legal Entity and Structure
OpenRemote is an open source project with a professional organisation registered in The Netherlands (as of here called OpenRemote). The management team consists of the CEO, CTO, and Product owner.
2.2 Management Commitment
The management team of OpenRemote, consists of CEO, CTO, and Product owner. The Chairman of the Advisory Board advises on long term ambition and performance and improvement targets.
The management team is committed to quality, safeguarded by peer review and a PDCA cycle which is linked to a short term (daily and weekly) and long term (half-yearly) cycle.
The half year cycle is organised as a face to face meeting of the whole organisation, during which strategic direction, product development (roadmap), key project realisations, and overall planning are evaluated. Performance related to quality of processes is reviewed and used to define improvements, translated into actions. A risk assessment approach is used to set priorities and select improvement actions.
The daily (stand-up) and (two)weekly meeting cycle, with the complete team, is primarily intended to review and plan the running program of projects as well as product development and define and monitor short term corrective or preventive quality improvement actions. The meeting also monitors the long term improvement actions defined during the half year cycle.
2.3 Roles and Responsibilities
This is preliminary information, as OpenRemote, we are working on this subject and will publish an update soon.
OpenRemote defines clear roles and responsibilities to ensure effective governance of quality, security, and operational processes. The CEO is accountable for the overall management system, including quality and compliance. The CTO is responsible for technical governance, product security, and Product owner for a secure development lifecycle.
Specific responsibilities are assigned for information security management, incident response, risk management, and system operations. Segregation of duties is applied where appropriate to reduce risks related to unauthorised access or conflicting responsibilities, particularly in areas such as system administration, code deployment, and financial management.
| Role | Roles and Responsibilities |
|---|---|
| CEO | Sales Financial and Personnel management Quality officer |
| CTO | System architecture Technical Roadmap Security lead and incidence response coordinator Infrastructure administration |
| Quality officer | Security officer, ISMS owner, Quality compliance monitoring |
| Product owner | Roadmap and programming Capacity and sprint planning Secure development lifecycle |
| Project manager | Project realisation Project production deployment |
| Topic owner | Manages a main topic or feature Gatekeeper to define and plan issues |
| Project technical lead | Project architecture Technical project realisation |
| UX manager | Marketing visual communication User requirements refinement for product features Product UX |
| Software developers | Code development Code review of development work of colleagues |