The "IKEA effect" describes how people tend to value an object more if they make or assemble it themselves. The same thing applies to building features.
What does it mean to own a feature from end to end? How will a product look when it is programmed by developers who understand its value, compared to developers that don't?
Building a feature is more than just coding. It is a rich, dynamic, fulfilling process - and the developer, who eventually brings it to life - should be an integral part of it. It’s not just choosing the right components, but for instance, keeping track of your users’ behavior once in production.
In this talk, I’ll share a methodology that encourages ownership and the effect it has on the developer’s work. I’ll provide practical examples and tools we use that strengthen this user-developer connection.
I believe that the portion of knowledge and responsibilities developers are given over the non-coding parts of a project, has a major effect on the product's success and the developers’ motivation.