CTO Roundtable #8
Hype or game changer? Are durable teams the way to develop software in 2021?
- 30.03.2021
- 15:00
- How to keep your engineering team effective and motivated?
- Who owns the running of a developed system?
- What works better – initiative-based teams or durable teams?
- How does team setup influence the recruitment process?
Projects vs products
More and more CTOs see the benefits of forming durable teams over single-project teams. Normally, at the end of a project, the team is disbanded and assigned to new ones with some new team members. On the other hand – the project is a platform, application or system that is created, maintained and supported by one team that is solving problems and providing benefits to specific business needs.
Our host, Gerbert Oude Velthuis invited a few experienced guests to talk about the differences between product development and project development. They focused on plenty of real-life insights that may help you understand when it’s worth to go with durable teams and when initiative-based team approach may be an advantage.
Gerbert Oude Velthuis
CTO at Travelia and General Manager at The Software House NL
Sriram Narayan
Author of the book "Agile IT Org Design"
Frank van den Brink
Technical Director & Software Development Consultant at Pragmatist
Rémi Tuyaerts
Chief Technology Officer at Fibr
What topics we discussed?
- 01What are the differences between durable teams and initiative-based teams?
- 02When durable teams are good for your business?
- 03How to make durable teams attractive enough for developers?
- 04How do you prevent silos between durable teams?
- 05How do you handle the team fatigue?
- 06How to set your team for long-term value delivery?