Empower Developers and Streamline Delivery


Tal Joffe
Nielsen, Engineering Director

Tal is a Web development director in Nielsen where he is also the organizer of the "Big web theory" meetup group, editor and writer of the Nielsen Tel Aviv tech blog and a champion of design best practices, functional programming, and clean code.
Tal is trying to combine his passion for technology and methodology to create happy effective teams that deliver great results.
In his spare time, Tal listens to many podcasts and will happily talk about them


Traditionally the development process of a product or feature is being passed around between people with different roles - Scrum masters, Architects, developers, QA, DevOps, etc.
By empowering developers to do most or all of these responsibilities we allow for a streamlined process.

You can rightfully argue that a QA professional, for example, will be much better on average than a developer in finding bugs but in some cases, the cost to the process and the lack of flexibility is greater than the benefit.

After working this way for a few years I want to share how we managed to get this approach working for us and where we are still trying to improve.

I'll also share what this approach does to the culture of an R&D organization and what can we benefit from it in terms of growth opportunities and retention for developers.