Management by Objectives (MBO)

A goal-focused performance management method that sets clear, measurable objectives and judges performance by how well results align with project outcomes.

Key Points

  • Objectives are jointly agreed and cascaded from organizational strategy to project and individual goals.
  • Goals should be specific, measurable, achievable, relevant, and time-bound, with success criteria defined upfront.
  • Performance is reviewed by comparing actual results to the agreed objectives and the project's outcomes.
  • Requires regular feedback and the ability to adapt goals as project priorities evolve.

Example

In a software release project, the project manager and team lead agree on objectives: reduce average cycle time by 20% and achieve a 95% automated regression pass rate by the end of the release. Team performance is evaluated against these targets and the quality of delivered features.

PMP Example Question

Which approach focuses on setting measurable goals and assessing team performance based on achievement of project-related results?

  1. Management by Objectives (MBO)
  2. Management by Walking Around (MBWA)
  3. Earned Value Management (EVM)
  4. Delphi Technique

Correct Answer: A — Management by Objectives

Explanation: MBO emphasizes agreed, measurable objectives and evaluates performance by how well those goals tied to project outcomes are met.

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