What are your thoughts on developer productivity teams?

Gene, what do you suppose the origin of the ancient, powerful order (aka the bureaucracy, aka silos) is given that it exists in so many organizations?

Gene, what do you suppose the origin of the ancient, powerful order (aka the bureaucracy, aka silos) is given that it exists in so many organizations?

Part 2 kicks off with the announcement of the one month feature freeze for Parts Unlimited which we saw in TPP was a huge success. I've read about the successful feature freezes with LinkedIn's Inversion and Microsoft's freeze for SQL Server security updates in the early 00s, but I was wondering if yal knew about some unsuccessful feature freezes and what might have characterized those vs the successful ones?

What are some ways you would recommend to convert Executive Management to the rebellion? I think it is easier to find the engineers and developers and not hard to convince them to work towards the greater good. I think it is harder to find the Executives that could help, what are some ways you think we can approach those as we start seeing positive movement of the needle?

What are some ways you would recommend to convert Executive Management to the rebellion? I think it is easier to find the engineers and developers and not hard to convince them to work towards the greater good. I think it is harder to find the Executives that could help, what are some ways you think we can approach those as we start seeing positive movement of the needle?

@genek Having looked across the industry are there any signs/signals that represent a likely show-stopper for transformations? What are the lead dominos that have to fall, before one can pull off the mindset change. Accelerate and The State of DevOps Reports give a number of items involved, but are there things that are the linchpins to the transformation being successful or unsuccessful?

Do you have any suggestions on ways to quantify value of having a feature freeze, or after a feature freeze quantifying the value of what was accomplished? How about any suggestions on typical/general items to prioritize first for a feature freeze that would make the biggest difference?

@genek Follow up on my previous question regarding distinguished engineer. I think asking what about org size and distinguished engineers was the wrong framing. Allow me to retry: what are the inflection points in an organization where considering a distinguished engineer role makes sense?

@genek To what measure would you agree that Organisation and Architecture are a mirror of each other. This makes it difficult that if you want to address either you have to address both. Tech Debt needs to be addressed with the Operational and Organisational debts that go with it. Same question for accelerating DevOps with rearchitecting in Monolithic environments. Getting the code of 200 devs to merge and build without issues is difficult. Breaking down into smaller services / smaller teams is a way of accelerating the devops practices in my view (and a path to Microservices too). Is there a max team size to Service that you would recommend?

@genek To what measure would you agree that Organisation and Architecture are a mirror of each other. This makes it difficult that if you want to address either you have to address both. Tech Debt needs to be addressed with the Operational and Organisational debts that go with it. Same question for accelerating DevOps with rearchitecting in Monolithic environments. Getting the code of 200 devs to merge and build without issues is difficult. Breaking down into smaller services / smaller teams is a way of accelerating the devops practices in my view (and a path to Microservices too). Is there a max team size to Service that you would recommend?