How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

Unapproved Change Requests

Change proposals are documented as change requests; until a formal decision approves them, they remain unapproved and must not be implemented.

Key Points

  • Requests for changes are logged as change requests and tracked through change control.
  • No work should start on an unapproved change request.
  • Impact analysis (scope, schedule, cost, risk, quality) is done before a decision is made.
  • Each request is either approved, deferred, or rejected, and its status is communicated and recorded.

Example

A stakeholder asks to add an extra reporting field mid-sprint. The project manager documents it as a change request and queues it for the change control board. Until the board approves it, the team does not modify the backlog or deliverables.

PMP Example Question

Midway through execution, a stakeholder asks the team to immediately add a new feature. The project manager identifies this as an unapproved change request. What should the project manager do next?

  1. Implement the change to keep the stakeholder satisfied.
  2. Record the request, perform impact analysis, and submit it for formal approval before any work begins.
  3. Reject the request and close the ticket permanently.
  4. Ask the team to build a quick prototype while waiting for approval.

Correct Answer: B — Record, analyze impacts, and seek formal approval before implementation

Explanation: Unapproved change requests must not be implemented. They should be documented, analyzed, and sent through the formal change control process for a decision.

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.

Seven 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


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now