Agile Principles

The twelve guiding rules for agile project delivery, as set out in the Agile Manifesto.

Key Points

  • Deliver value early and often, welcoming changes even late in development.
  • Collaborate closely with customers and cross-functional teams to clarify needs.
  • Measure progress by working product increments and maintain a sustainable pace.
  • Continuously improve through reflection, simplicity, and technical excellence.

Example

A product team runs two-week iterations, ships a small working feature each sprint, invites stakeholders to review, accepts a new high-value request mid-release, and uses a retrospective to adjust their Definition of Done for better quality.

PMP Example Question

Which action best aligns with Agile Principles during a fast-changing project?

  1. Lock the scope after planning to prevent rework.
  2. Release working increments frequently and reprioritize with the customer as needs evolve.
  3. Delay integration testing until all features are complete.
  4. Centralize decisions with the project manager to speed approvals.

Correct Answer: B — Release working increments frequently and reprioritize with the customer

Explanation: Agile Principles emphasize frequent delivery of working product and close customer collaboration to respond to change.

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


Become an AI-First Agile Leader!

HK School of Management and Technology helps you apply AI to Agile work with practical, prompt-based workflows for real-world Scrum challenges. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More