Agile vs. Scrum Explained, and How a PM Runs the Backlog, Sprints and Ceremonies

Explain Agile and Scrum as you understand them, and walk through how you apply them in your own work as a product manager. ```hint Concept first, then your seat at the table Decide which of the two terms is a mindset and which is a concrete framework before describing either, then name the specific events and artifacts you personally own versus the ones the engineering team or the Scrum Master runs. ``` ### Clarifying Questions - Are you more interested in the concepts themselves or in how I have applied them, including where my teams departed from standard Scrum? - Should I describe the PM as also holding the Scrum Product Owner role, or as working alongside a separate Product Owner? - Is the focus a single team, or several Scrum teams delivering one product? - Should the answer cover how sprint work fits with reviews that sit outside the team, such as risk, legal or compliance sign-off? ### What a Strong Answer Covers - An accurate distinction between Agile as a set of values and Scrum as one framework, with Scrum's accountabilities, events and artifacts described correctly. - The PM's own responsibilities inside the process and where they end relative to the developers and the Scrum Master. - Concrete working habits across the sprint cycle, illustrated with an example of how the candidate ran or changed the process. - How the candidate adapts Scrum to fixed dates, cross-team dependencies, interrupt-driven work or external reviews. - How the candidate judges whether the process is working, without turning team metrics into targets. ### Follow-up Questions - Stakeholders want a fixed launch date and a fixed scope. How do you reconcile that with sprint-by-sprint planning? - The team's completed work has dropped for three sprints in a row. What do you look at first? - When would you recommend Kanban instead of Scrum for a team you work with?