Here's how you can identify the key principles of Agile Methodologies that interviewers look for.

People and communication over processes and tools, Working software over extensive documentation, Customer collaboration over strict contracts and Adapting to change over following a fixed plan are foremost important in agile

The Agile Manifesto outlines 4 core values: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. When discussing these values in an interview, emphasize your experience with direct communication, delivering functional products, working closely with customers, and adapting to changing product needs. Although the focus is on the "left" sides of the values, the "right" sides are still important. You need processes, tools, contracts, and plans, but the emphasis should be more on the left.

Interviewers seek candidates who grasp fundamental Agile principles: Customer Collaboration: Emphasizing continuous engagement to deliver value. Iterative Delivery: Incremental releases for early feedback and adaptation. Self-organizing Teams: Empowered groups that adapt and make decisions. Adaptability: Embracing change for responsiveness and competitive advantage. Continuous Improvement: Iterative refinement through regular retrospectives. Transparency: Open communication and visibility across projects. Prioritization: Focus on delivering high-value features promptly. Demonstrate these principles in your experience to showcase Agile proficiency effectively

Hiring managers are far more interested in what you delivered using Agile, less so in quizzing you on the Manifesto. I would encourage anyone interviewing for an Agile role to focus far more on how they've operationalized the four values and the 12 principles, and specifically how you reduced cycle time, improved quality, and especially how your teams' products improved your employer's bottom line. Also describe how you included the stakeholder in building the product roadmap, planning, refinement, demos, etc.

Beyond the 4 values, the Agile Manifesto lists 12 guiding principles. Interviewers often look for your understanding of principles like satisfying the customer through early and continuous delivery, welcoming changing requirements, and delivering working software frequently. Many people find it challenging to explain the principle: "Simplicity—the art of maximizing the amount of work not done—is essential." Since the Agile Manifesto has only 4 values and 12 principles, it is important to understand all of them. Try to understand this principle as it is often asked during technical interviews for explanation.

From a technical interviewer's perspective, it's crucial to use the correct terminology. For a light framework like Scrum, there aren't too many terms to remember, so precision is important. For example, instead of using the term "roles," use "accountabilities" to ensure clarity and accuracy in your discussions. Even in this article, the author used the wrong terminology.

When discussing Agile frameworks, remember that they are just that—frameworks. Talk about how you have tailored these frameworks to fit your organizational needs. Share examples of adaptations or customizations you implemented to address specific challenges, improve efficiency, or better align with your team's workflow. This demonstrates your practical understanding of Agile and your ability to apply it flexibly to achieve the best outcomes.