Agile Fundamentals for Product Managers: Core Values, Principles and Team Practices

You are interviewing for a product manager role. Explain what the Agile approach to building software is and walk through its key principles. ```hint Separate the ideas from the rituals Agile is often confused with one framework's meetings. Start with the small set of values and principles behind it, and for each one say what it changes about how a team plans, builds and ships. ``` ### Clarifying Questions - Should I cover Agile as a general set of values and principles, or focus on a framework the team uses day to day, such as Scrum or Kanban? - Do you want me to include how a product manager works inside an Agile team (backlog, sprint planning, reviews), or only the methodology itself? - Would a comparison with a plan-driven (waterfall) approach help, to show when Agile fits and when it does not? ### What a Strong Answer Covers - What Agile is (a philosophy rather than a single process) and the problems of plan-driven delivery it responds to - The core values and principles, each explained by its practical effect on a team - How frameworks such as Scrum and Kanban turn the principles into roles, cadences and artifacts - Where the product manager fits: ordering the backlog, defining outcomes and acceptance criteria, handling fixed dates - The limits of Agile and the most common ways teams misapply it ### Follow-up Questions - A regulatory deadline fixes both the launch date and most of the scope of a feature. How do you plan it in an Agile team? - How would you tell whether a team is genuinely Agile or only running the ceremonies? - When would you choose Kanban over Scrum for a product team, and what would you measure in each?