 SSD structure and tools, and can better engage with beta data testing. Feedback to date has been insightful, and directly correlated to periods directly following project presentations. 22 Given the known time constraints and varied skills-confidence within the sector, it was effective to ensure a persistent and minimalistic channel for wider feedback. 9.4. Direct stakeholder driven iteration Gaining support from a project ‘champion’ within a given LA improved the development progress; the project benefited directly from having senior colleagues with direct access to LAs’ data/infrastructure teams, in order that more simplistic database system tests and sample runs could be achieved with very low time-overheads. This enabled an accelerated development cycle with specific pilot partners. Our iterative approach also allowed us to overcome unexpected hurdles – for example, learning mid- project that some CMS platforms can operate on more than one database technology, dependent on LA preference. This naturally complicated development work, but the stakeholder-driven iterative approach helped us find issues early and adapt our work to address them. 9.5. Trust dependent rapid development We were able to improve development pace where our tests could be run by colleagues without elevated privileges on the required systems. Direct feedback of this sort enabled a rapid iterative development cycle, and this process has been heavily dependent on the trust from LAs towards D2I, and a strong desire on the part of LAs to support positive change in the sector. We also saw evidence that increased development and testing pace was directly tied to levels of consistency across deployed instances of each CMS; CMS products allow for different kinds of customisation, with some products enab