Be sure to indicate that you are open to exploring options that are the best fit for each team. Candidates that indicate a preference for stringent process, process-driven roles, or even enforcing standards across all of the teams that contribute to a program will likely be excluded from follow-up interviews.

"My preferred development methodology is one that fits the unique needs of the team working to develop the solution and the stakeholders involved. Understanding various methodologies at a conceptual level is helpful, but I find that things tend to break down in a team setting when the process is followed too stringently. The goal for me is to have a well-defined toolkit to pull from as needed and to be flexible enough to respond quickly to the need for change.

Generally speaking, I like to work with my teams to agree to a process that allows us to incrementally and continually deliver value to our users and stakeholders. I find it easier for teams to tackle smaller bodies of work than to take on multi-year projects that feel like they never end. I also like to ensure that the teams I work with reflect regularly and work to find new and exciting ways to add value. Other than that, I think the specific recipe for success varies team-to-team. I am good with and will offer my full support to whatever they decide is the best fit as long as they can prove it works and they are happy with it."