2024 · Montpellier, France · Hybrid
Responsible-IT consultant (coaching) — public sector
CGI — Public body in charge of public finances and taxation
Technical eco-design coaching of the development team, following on from the initial assessment and its action plan. One step of fifteen months of support at the same public body, on the development of its internal online banking service.
The first workshop, the day after the readout: a round table with the development team, each person's role and the scope they were responsible for — front end, batch, queries, CI/CD — then a walk-through of the action plan for them to take on: enabling compression, simplifying the DOM, cutting the number of requests, maximising the cache, putting monitoring tools in place.
Workshops every fortnight. At each session, each person reported on their fortnight's work, on the eco-design questions they had met in doing it and on what they had put in place. Every question and every improvement point was recorded in a question-and-answer file, reusable as a reference on other projects.
The role shifted as the sessions went on: actively proposing fixes and improvements at first, then simply validating and recording decisions, questioning eco-design having become a working habit and the team self-sufficient.
Coaching too of the eco-design reference person, a project director: clarifying strategy questions and preparing an internal lessons-learned session. It was on that occasion that environmental criteria were raised to the level of the applications' architecture document, to be weighed alongside financial and security criteria when the architects' committee grants approval.
Functional coaching, finally: folding eco-design criteria into the approval of business requests and updating the specification template, so that the questions are anticipated before they reach the developers.
A load of around two days a month.
Achievements
Environmental criteria written into architecture governance
Environmental criteria raised to the level of the applications' architecture document, to be weighed alongside financial and security criteria when the architects' committee grants approval.
A team that became self-sufficient
Actively proposing fixes and improvements in the early sessions, then simply validating and recording decisions: questioning eco-design had become one of the team's working habits.
- 2 days of support a month
Fortnightly workshops over five months
Workshops every fortnight with the development team: each person reporting on their fortnight's work, on the eco-design questions met and on what had been put in place.
Eco-design anticipated upstream of development
Eco-design criteria added to the approval of business requests and objectives spelled out in the specification template, so that the questions are anticipated before they reach the developers.
A reusable question-and-answer file
Every question and improvement point raised in the workshops recorded, forming a reference on how to approach eco-design, reusable on other projects.