T3CON Recap - EVB-IT Contracts Guide for TYPO3 Projects
Understanding EVB-IT Contracts: A Modern Guide for TYPO3 Projects
In the evolving landscape of public sector IT projects, EVB-IT contracts have become a crucial framework for successful project delivery. These standardized contracts, while initially seeming bureaucratic, represent years of practical experience in managing complex IT projects - particularly relevant for TYPO3 public sector implementations in government institutions. At T3CON2024, lawyer and IT law specialist Stephan Schmidt delivered an insightful talk on how these contracts, especially the EVB-IT Cloud agreement, serve as a practical toolbox for TYPO3 projects.
Stephan Schmidt
TCI Rechtsanwälte
Stephan Schmidt is a specialist lawyer of IT law and founding partner of the law firm TCI Rechtsanwälte. He has been advising national and international companies and the public sector on IT contracts, IT procurement and IT security law issues for almost 20 years.
The Evolution of EVB-IT
Breaking Down the Silos
One of the most significant recent developments is the new framework agreement that fundamentally changes how these contracts work. As Schmidt explained:
"Previously, I sometimes had to conclude two, ultimately three EVB-IT contracts for tenders, which hopefully didn't contradict each other. Now I can hang all these contract types as modules into one contract through the framework agreement."
The framework now encompasses twelve distinct templates, providing structured agreements for various government IT contracts, including specialized contracts for hardware purchase, software licensing (Types A and B), service agreements, maintenance, system contracts, development, and the newer cloud services agreement.
The Digital Revolution
EVB-IT is embracing digital transformation with EVB-IT Digital, an open-source solution that runs in the web browser. "We noticed earlier that even in the public sector, things are slowly becoming more agile," Schmidt noted. The platform includes a form designer and framework agreement capabilities, with all contracts exportable to Word format for further customization.
Cloud Contracts: A Modern Approach
The EVB-IT Cloud contract represents a significant modernization of the framework, covering:
- Infrastructure-as-a-Service
- Software-as-a-Service
- Platform-as-a-Service
- Managed Cloud Services
Schmidt emphasized the practical importance of security requirements: "Does your provider who maintains your websites actually have a security officer? Or do they just have, in quotation marks, a €9.95 data protection officer they've never seen in their life?"
The cloud contract introduces specific technical and government CMS security requirements, including:
The Art of Project Management
Effective project management isn’t just about technical execution—it’s about managing content, communication, and change. Schmidt highlighted three key areas where projects often face hurdles and shared practical strategies to navigate them.
Content and Collaboration
One of Schmidt's most practical insights addressed a common project challenge: "You can be the best agency in the world, but the content must be delivered by the customers, and if they don't do that, the project won't be finished in time."
Avoiding the 'Hey Joe' Syndrome
Schmidt warned against informal project changes, describing what he calls the "Hey Joe syndrome" - where project communications become scattered and unmanaged, leading to scope creep and missed deadlines. The solution lies in structured change management processes and clear communication channels.
Planning for the End
Schmidt emphasized the need to plan for government website exit management: "Like in a good marriage contract, there are divorce regulations." He advised including comprehensive exit clauses that cover:
- Data transfer procedures
- Migration support timelines
- Transition assistance requirements
- Post-contract data retention periods
His practical advice on data handling was particularly noteworthy: "Many say at contract end, the provider must delete everything. That's perhaps not the smartest idea... I prefer to make a follow-up solution - keep it for 6 months, so you have time to ensure everything is transferred correctly."
TYPO3-Specific Implementation
For TYPO3 projects, Schmidt recommended using the EVB-IT Development contract, while noting its need for updates. He suggested structuring it with:
- Fixed-price arrangements for standard components
- On-demand options for additional features
- Clear maintenance provisions under Section 5
- Development regulations under Section 6
A crucial technical note: "Be careful, because maintenance is Section 5, further development is Section 6. If you're not careful, your contractor will develop further, but it's completely unclear whether they must maintain what they developed."
The Future of EVB-IT
The framework continues to evolve, with plans to better accommodate open-source solutions, like EVB-IT Digital, and modern development practices. Upcoming changes include:
- Enhanced open source provisions
- Updated technical specifications
- Improved digital workflow integration
- Modernized security requirements
Why EVB-IT Contracts Matter
EVB-IT contracts, while sometimes seen as bureaucratic obstacles, actually represent a thoughtful approach to managing complex IT projects. Their evolution toward more flexible, digital-first solutions shows how government contracting is adapting to modern development practices.
For TYPO3 developers and agencies, understanding these contracts isn't just about compliance - it's about learning from a framework that has been refined through years of real-world project experiences, successes, and failures. Whether you're working in the public sector or not, the principles embedded in EVB-IT contracts offer valuable insights for structuring successful TYPO3 projects.
Did you enjoy this recap? If you would like to relive all the exciting moments from T3CON24, be sure to check our our recap of the entire conference!
