1. Composition

The Technical Commission is composed by :

• the IT development manager (Solution Architect P-CDP-02-001 et Associative Product Owner P-CDP-01-001) coordinating the Technical Commission
• a maximum of one delegate per member of the Association (Institutional Product Owner)

The term of office is 2 years, renewable without limit.

The Technical Commission meets as many times as its business requires. The decision-making process is the same as that of the Committee (Art. 18 of the Botalista Association statutes).

The activities of the Technical Commission are coordinated by  the IT development manager (Solution Architect P-CDP-02-001 et Associative Product Owner P-CDP-01-001).

Organizational chart of the Technical Commission

2. Decision and vote

The Technical Commission can only validly deliberate if half of the members with voting rights are present ; of the members present, at least one must be a representative of the City of Geneva within the meaning of the Article 12 of the Botalista Association statutes.

The Technical Commission takes its decisions as far as possible by consensus. If this is not possible, a vote is taken, possibly secret at the request of one of the members. In the event of a tie, the voice of the IT development manager counts double. He can also take any decision by electronic consultation.

3. Responsibilities

The Technical Commission is responsible in particular :

• synthesize the needs of users of the Botalista Community software
• quantify the needs and possible developments
• de préaviser la priorisation, en concertation avec le responsable des développements informatiques, des corrections et évolutions à apporter au progiciel Botalista
• de participer avec le représentant des utilisateurs aux tests du progiciel Botalista avant la mise en production de nouvelles versions.

4. Operation

The Technical Commission, during its meetings, decides on the major orientations to be given to the Botalista Community software (Big picture Agile). These major orientations should make it possible to project developments winto a fairly long future (6 to 12 months). Generaly these choices relate, for example, to the creation of a new module (BOTA-HER, etc.) or meta functionalities (use of the application on mobile phones for example).

Then, in charge of the Associative Product Owner P-CDP-01-001) to write and follow the progress of the Product Backlog in connection with the objectives defines by the Technical Commission. As defined in the Botalista Policy and Processes, the prioritization of each of the community's needs is done by all the partners via the Story Point. This consultation is done electronically.

Each of the development cycles is notified to the Institutional Product Owners by the Associative Product Owner, which makes it possible, in consultation with the Releases Manager, to plan the user test phases.