agile

A mindset grounded in the values and principles outlined in the Manifesto for Agile Software Development.

Key Points

  • Centers on values and principles rather than rigid processes or tools.
  • Encourages iterative work, continuous learning, and rapid feedback.
  • Prioritizes customer value, collaboration, and responding to change.
  • Guides behaviors across roles, practices, and frameworks, not just software teams.

Example

A cross-functional team plans in two-week iterations, meets daily to inspect progress, reprioritizes the backlog with the product owner, and frequently releases small increments to gather user feedback—demonstrating the agile mindset in action.

PMP Example Question

In an organization shifting to adaptive delivery, what best describes the term "agile"?

  1. A prescribed set of tools and ceremonies that must be followed exactly
  2. A contracting method that fixes scope but allows flexible schedule
  3. A mindset based on the values and principles of the Agile Manifesto
  4. A linear, document-driven development lifecycle

Correct Answer: C — A mindset based on values and principles

Explanation: Agile refers to a mindset that emphasizes the Agile Manifesto's values and principles, not a rigid process, contract type, or sequential lifecycle.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management, not on Udemy.

See What Is Included