I was totally with the presentation until about 40% of the way in. My objections with these kinds of "more agency for the team" approaches are as follows: 1) W

I was totally with the presentation until about 40% of the way in. My objections with these kinds of "more agency for the team" approaches are as follows: 1) We are assuming dev teams want to do the extra work of defining what to make, or put another way, are happy with being responsible for it. Also for the people that do think that way, it assumes their teammates are likewise motivated. 2) In my experience, developers are not people-oriented and therefore will naturally resist collaboration at some level, especially with with customers. 3) Does any developer really think their time is well-spent participating in investigatory market research, advocated in this presentation? Thoughts? Disclaimer: I am a developer. I can get enthused about these approaches, but often gravitate back to the hermit-like mentality that drove me to programming in the first place. I can't help but think that a lot of this non-programming activity would be better served if organisations today just embraced the Business Analyst role more.