live_tv
Livestream Starting Soon
00
Hours
:
00
Minutes
:
00
Seconds
Up next in 10
Agile Review Series: Agile Change Management
Full 150 Agile Review & Questions Video: https://youtu.be/Z-teNScLspI
How do Agile teams adapt to evolving needs while staying focused on value delivery? In this video, we’ll explore Agile Change Management — how Agile teams embrace change, balance flexibility with focus, and collaborate effectively to handle new requests, stakeholder input, and shifting priorities.
This is the 13th video in our 15-part Agile Review & Question series.
You’ll learn how Agile teams manage change through backlog reprioritization, servant leadership, stakeholder engagement, and adaptive contracts — all while protecting the Sprint Goal. Then, you’ll test your understanding with 10 scenario-based practice questions (Questions 121–130) with detailed explanations.
✅ You’ll learn how to:
• Manage change requests while maintaining sprint focus
• Differentiate between changes that can and cannot be accepted mid-sprint
• Support the Product Owner’s role in backlog reprioritization
• Handle change collaboratively in Agile and hybrid environments
• Foster adaptability and transparency using Agile principles
By practicing these questions, you’ll strengthen your ability to manage change the Agile way — a key skill for both the PMP® exam and real-world project delivery.
Chapters:
0:00 Agile Change Management Overview
3:35 Question 121
Show More Show Less View Video Transcript
0:00
The topic we'll cover is agile change
0:02
management. How agile teams respond to
0:04
evolving needs, manage change
0:06
collaboratively, and maintain focus
0:09
while still embracing flexibility. In
0:12
agile, change isn't a disruption. It's
0:14
part of the process. Agile teams are
0:16
designed to adapt continuously, and this
0:19
mindset is what truly separates agile
0:21
from traditional predictive approaches.
0:23
On the PMP exam, you'll be tested on how
0:26
well you understand this adaptive
0:28
mindset and how change is handled in
0:31
both agile and hybrid environments.
0:33
Agile teams welcome late stage changes
0:36
when they create more value for the
0:38
customer. That's because the product
0:40
backlog is a living artifact. It's
0:42
constantly updated as new insights
0:44
emerge from stakeholder feedback, shifts
0:47
in the market, or evolving business
0:49
priorities. This ensures teams are
0:51
always focused on delivering the highest
0:54
value work first. The product owner
0:56
plays a central role here. They evaluate
0:59
change requests, collaborate with
1:01
stakeholders, and decide how to rep
1:02
prioritize the backlog. This ensures
1:05
that the team adapts without losing
1:06
sight of the product vision and customer
1:08
needs. Now, here's something important
1:10
for the exam. Not every change should be
1:13
handled the same way. Some changes can
1:15
be incorporated immediately while others
1:17
must be deferred. If a change supports
1:20
the current sprint goal, such as a small
1:22
clarification or a critical defect fix,
1:24
the team can adapt and bring it into the
1:26
sprint. But if a change would undermine
1:29
the sprint goal, like adding a new
1:30
feature request or introducing major new
1:33
scope, it should not disrupt the sprint.
1:35
Instead, the product owner places it in
1:37
the product backlog to be prioritized
1:39
later. This distinction is a common exam
1:43
trap. Look for keywords like critical
1:45
defect or clarification for changes that
1:48
can be included right away and keywords
1:50
like new feature request or outside the
1:54
current sprint scope for changes that
1:56
should be deferred. The golden rule is
1:59
to protect the sprint goal. Agile
2:02
leaders also rely on empathetic
2:03
listening and servant leadership when
2:05
responding to change, creating trust and
2:08
helping teams stay focused while
2:10
stakeholders feel heard. And through
2:12
feedback loops like sprint reviews and
2:14
backlog refinement, agile ensures that
2:16
change isn't disruptive. It's built into
2:18
the system. Another key area is
2:21
stakeholder feedback. Agile thrives on
2:23
short feedback loops, integrating input
2:25
through sprint reviews, backlog
2:27
refinement, or even ad hoc
2:29
conversations. This keeps products
2:30
aligned with real customer needs, not
2:33
outdated assumptions. Contract design
2:36
also matters. Agile friendly contracts
2:39
include flexibility clauses that allow
2:41
for scope adjustments without triggering
2:43
massive renegotiations. This creates
2:45
space for change while still managing
2:47
accountability and risk. Finally, agile
2:51
teams must balance change with
2:53
sustainability. It's not about chasing
2:55
every request. It's about adapting while
2:58
maintaining a healthy pace, avoiding
3:00
burnout, and preserving long-term
3:02
delivery capability. In hybrid
3:05
environments, change can be more
3:06
complex, blending agile adaptability
3:09
with predictive controls. Here you'll
3:11
want to understand how teams balance
3:13
documentation, governance, and vendor
3:15
constraints with the need to remain
3:17
responsive. Now, we'll go through 10
3:19
practice questions that will test your
3:21
knowledge of agile change management
3:23
strategies, leadership behaviors,
3:25
backlog rep prioritization, and how
3:28
agile organizations stay flexible
3:30
without losing focus. Let's get into the
3:32
first question in this topic. Question
3:35
121. Midway through a release, a key
3:39
stakeholder requests a significant
3:40
feature change after learning about new
3:42
market regulations. The team is
3:44
concerned this could disrupt their
3:46
progress. The project manager wants to
3:48
demonstrate agile's approach to handling
3:50
latest stage changes. What is the best
3:53
course of action? A. Work with the team
3:56
to explain to the stakeholder that
3:58
changes should wait until after the
4:00
sprint to protect the team's focus. B.
4:03
Facilitate a meeting with the team and
4:05
stakeholder so the team can decide
4:07
whether to adjust the backlog based on
4:08
the request. C. Collaborate with the
4:11
team to capture the change and schedule
4:13
it for a future release cycle to avoid
4:16
disrupting the current plan. D.
4:19
Collaborate with the product owner to
4:20
evaluate the request, update the backlog
4:22
if it adds value, and rep prioritize
4:24
work accordingly. You can pause the
4:27
video here if you need more time to work
4:29
on the question. The correct answer is
4:32
D. This question tests your
4:34
understanding of how agile embraces
4:36
latest stage change requests that
4:38
deliver value. Agile does not freeze
4:41
requirements once planning has occurred.
4:43
Instead, it adapts through continuous
4:46
backlog refinement and rep
4:47
prioritization. Choice D is the best
4:50
option because the product owner has
4:51
ownership of the backlog. They evaluate
4:53
the request, determine whether it adds
4:55
value, and if so, adjust priorities, so
4:58
the team's work aligns with business and
5:00
regulatory needs. Choice A is incorrect.
5:03
Protecting sprint focus may sound
5:05
reasonable, but rejecting latest stage
5:07
changes goes against agile principles.
5:10
Choice B is incorrect. Involving the
5:12
team in backlog decisions appears
5:14
collaborative, but backlog ownership
5:17
rests with the product owner, not the
5:19
developers. Choice C is incorrect.
5:22
Deferring the change to a future release
5:24
cycle avoids disruption but sacrifices
5:27
responsiveness and timely delivery of
5:30
value. Let's move on to the next
5:32
question if you're ready. Question 122.
5:35
During a sprint, a developer privately
5:37
tells the project manager that they feel
5:39
overwhelmed with their workload and
5:41
unsupported by teammates. What should
5:43
the project manager do? A, listen to the
5:46
developer's concern, acknowledge it, and
5:49
bring the topic to the team so they can
5:50
discuss how to handle workload balance.
5:53
B, meet individually with other team
5:55
members to understand their perspectives
5:57
before making adjustments to
5:59
assignments. C. Express appreciation for
6:02
the developer's openness and encourage
6:04
them to raise the concern directly with
6:06
the team during the next standup. D.
6:09
Note the concern and plan to bring it up
6:11
during the retrospective so the team can
6:13
collectively discuss workload and
6:15
support. You can pause the video here if
6:18
you need more time to work on the
6:20
question. The correct answer is A. This
6:23
question tests your understanding of how
6:25
agile leaders use empathy and
6:27
transparency to support the team.
6:29
Leadership in agile is not about
6:30
directing work but about enabling the
6:32
team to address challenges openly.
6:35
Choice A is the best option because
6:37
listening to the developer's concern,
6:39
acknowledging it and bringing it to the
6:41
team promotes transparency, shared
6:43
responsibility and collective problem
6:45
solving. Choice B is incorrect. Speaking
6:48
to individuals separately may seem
6:50
empathetic but reduces transparency and
6:52
risks creating side conversations.
6:55
Choice C is incorrect. Encouraging
6:58
openness is positive, but it puts the
7:01
burden back on the developer instead of
7:03
the leader, creating psychological
7:05
safety. Choice D is incorrect.
7:08
Retrospectives allow team discussion,
7:09
but waiting delays action and leaves the
7:12
developer unsupported during the sprint.
7:14
Let's move on to the next question if
7:16
you're ready. Question 123. A large
7:19
program is being managed using a hybrid
7:22
approach. Agile teams deliver components
7:24
iteratively, while predictive governance
7:26
requires formal change control for scope
7:29
at the program level. A new stakeholder
7:31
request impacts both agile work streams
7:33
and the program's critical milestones.
7:36
How should the project manager handle
7:38
this change? A. Ask the product owner to
7:41
evaluate and accept the request in the
7:43
backlog and then inform the program PMO
7:45
so governance artifacts can be updated
7:48
afterward. B. Coordinate with team leads
7:51
to plan the change into the next sprint
7:52
through backlog refinement and release
7:54
planning and submit the change to the
7:56
change control board. C. Collaborate
7:59
with the product owner to update the
8:00
backlog while also submitting the change
8:03
for program level review to assess
8:05
milestone and scope impacts. D. Submit
8:08
the change to the program CCB for an
8:11
expedited decision, allowing teams to
8:13
continue limited planning activities
8:15
while awaiting formal approval. You can
8:18
pause the video here if you need more
8:19
time to work on the question. The
8:21
correct answer is C. This question tests
8:24
your understanding of how to manage
8:26
change in hybrid environments. In a
8:28
hybrid project, agile teams remain
8:30
flexible through backlog adaptation
8:33
while predictive governance requires
8:35
formal oversight for scope and milestone
8:37
impacts. The project manager must ensure
8:40
both sides are respected. Choice C is
8:43
the best option because it integrates
8:45
backlog rep prioritization with program
8:48
level change review. This balances agile
8:51
adaptability with predictive governance.
8:53
Choice A is incorrect. Allowing the
8:56
product owner to update the backlog
8:58
first and notifying the PMO afterward
9:01
creates misalignment and risks
9:03
unapproved changes slipping into
9:05
delivery. Choice B is incorrect.
9:08
Involving team leads in the CCB is
9:10
proactive, but it bypasses backlog
9:12
ownership by the product owner and can
9:14
undermine proper prioritization.
9:17
Choice D is incorrect. Escalating
9:19
quickly sounds efficient, but pushing
9:22
the decision entirely to the CCB removes
9:24
collaboration and risks unnecessary
9:27
delays. Let's move on to the next
9:29
question if you're ready. Question 124.
9:33
During a sprint review, stakeholders
9:34
suggest several adjustments to improve
9:36
the product's usability. The development
9:39
team is enthusiastic but worried about
9:41
disrupting ongoing work. What is the
9:44
best way for the project manager to
9:45
ensure this feedback is handled in line
9:47
with agile principles? A. Ask the
9:50
product owner to log the stakeholder
9:52
feedback and wait until the next
9:54
retrospective to discuss how it should
9:56
be addressed. B. Work with the product
9:58
owner to capture the feedback as backlog
10:00
items, refine them as needed, and
10:02
prioritize them against existing work.
10:05
D. Facilitate a workshop with the
10:07
product owner, stakeholders, and
10:09
developers to immediately adjust the
10:11
current sprint backlog to include the
10:13
changes. D. Encourage the product owner
10:16
to have the team make small usability
10:19
adjustments right away during the sprint
10:22
to demonstrate responsiveness.
10:24
You can pause the video here if you need
10:26
more time to work on the question. The
10:29
correct answer is B. This question tests
10:32
your understanding of how agile
10:33
incorporates stakeholder feedback
10:35
without losing focus on sprint
10:37
commitments. Agile teams welcome
10:39
feedback, but integrate it through
10:41
backlog management and prioritization,
10:43
not by disrupting ongoing sprint work.
10:46
Choice B is the best option because the
10:48
product owner ensures that feedback
10:50
becomes properly refined backlog items
10:53
and prioritized alongside existing work,
10:55
maintaining both responsiveness and
10:57
focus. Choice A is incorrect.
11:00
Retrospectives are for improving the
11:02
team's process, not for deciding how
11:05
product feedback should be handled.
11:08
Choice C is incorrect. Involving
11:11
everyone to change the sprint backlog
11:13
mid-sprint disrupts commitments and
11:15
reduces focus on the sprint goal. Choice
11:18
D is incorrect. Making adjustments on
11:20
the fly may seem responsive, but it
11:22
undermines sprint discipline and
11:24
introduces scope creep. Let's move on to
11:27
the next question if you're ready.
11:29
Question 125. During a sprint, a
11:32
stakeholder requests a change to an
11:34
upcoming feature. The developers are
11:36
eager to implement it immediately
11:37
because it seems straightforward and
11:39
useful. The scrum master suggests
11:41
documenting the request for visibility.
11:43
What is the correct way to handle this
11:45
change in agile? A. The product owner
11:48
should review the request, determine its
11:50
value, and update the backlog if
11:52
appropriate, adjusting priorities as
11:54
needed. B. The developers should add the
11:57
request directly to the sprint backlog
11:59
since they are closest to the technical
12:01
work. C. The scrum master should track
12:03
the request in the impediment log and
12:05
bring it up at the next retrospective
12:07
for team discussion. D. The project
12:09
manager and product owner should perform
12:11
an impact analysis and decide if the
12:13
change should be included in the
12:15
backlog. You can pause the video here if
12:18
you need more time to work on the
12:19
question. The correct answer is A. This
12:23
question tests your understanding of the
12:24
product owner's role in managing change.
12:27
In agile, the product backlog is the
12:29
single source of work and the product
12:31
owner is accountable for ensuring all
12:33
changes are evaluated for value and
12:36
prioritized appropriately. Choice A is
12:39
the best option because the product
12:40
owner reviews the request, determines
12:42
its value, and updates the backlog if
12:45
necessary. This keeps ownership clear
12:47
and ensures prioritization aligns with
12:50
business goals. Choice B is incorrect.
12:53
Developers provide valuable technical
12:54
insight but do not own backlog
12:56
prioritization, and adding items
12:58
directly to the sprint backlog
13:00
undermines product ownership. Choice C
13:02
is incorrect. The scrum master focuses
13:04
on team effectiveness, not backlog
13:07
management. and the retrospective is the
13:08
wrong form for product level change
13:10
requests. Choice D is incorrect. While
13:13
collaboration between the project
13:15
manager and product owner may sound
13:17
thorough, backlog ownership rests solely
13:20
with the product owner, not shared
13:21
decision-making with the project
13:23
manager. Let's move on to the next
13:25
question if you're ready. Question 126.
13:28
A project is being delivered through an
13:30
agile vendor partnership. The sponsor
13:32
wants to ensure the contract can handle
13:34
scope adjustments as priorities evolve
13:37
without requiring lengthy renegotiations
13:39
for every change request. Which type of
13:42
clause best supports agile ways of
13:44
working? A. Include a contract clause
13:47
allowing changes but require formal
13:50
customer sign off on each adjustment
13:52
before backlog rep prioritization.
13:55
B. Allow the project manager to approve
13:58
minor changes directly while major
14:00
changes must still follow the standard
14:02
change approval process. C. Use a time
14:05
and materials contract clause that
14:08
allows ongoing changes and backlog rep
14:10
prioritization. D. Define contract terms
14:13
that support backlog rep prioritization,
14:16
enabling the vendor and customer to
14:18
adjust features collaboratively within
14:20
agreed constraints. You can pause the
14:22
video here if you need more time to work
14:24
on the question. The correct answer is
14:26
D. This question tests your
14:28
understanding of agile friendly contract
14:30
clauses. Agile contracts should enable
14:33
adaptation, collaboration, and
14:35
responsiveness without burdensome
14:37
renegotiation.
14:38
Choice D is the best option because it
14:41
defines terms that support backlog rep
14:43
prioritization while explicitly
14:45
requiring vendor and customer
14:47
collaboration within agreed constraints.
14:50
This ensures flexibility while keeping
14:52
both parties aligned. Choice A is
14:55
incorrect. While it allows changes
14:57
requiring formal signoffs on every
14:59
adjustment adds bureaucracy and slows
15:01
adaptation. Choice B is incorrect.
15:04
Approvals by the project manager create
15:05
a tiered change process that feels
15:07
predictive and undermines agile
15:09
collaboration. Choice C is incorrect.
15:12
Time and materials contracts offer
15:14
flexibility and support rep
15:16
prioritization, but without explicit
15:18
collaboration and boundaries, they may
15:20
lead to scope ambiguity and
15:21
misalignment. Let's move on to the next
15:24
question if you're ready. Question 127.
15:27
Midway through the release, a regulatory
15:29
body issues new requirements that must
15:32
be addressed. Stakeholders agree these
15:34
are high priority, but the team is
15:36
already committed to its current sprint
15:38
backlog. What should the project manager
15:40
do to ensure the work is handled
15:42
appropriately? A. Ask the product owner
15:45
to incorporate the requirements into the
15:46
current sprint backlog so the team can
15:48
address regulatory requirements
15:50
immediately. B. Capture the requirements
15:53
with the product owner and defer
15:55
discussion of priority until after the
15:57
sprint review to preserve the current
15:59
sprint commitments. C. Collaborate with
16:02
the product owner to add the new
16:03
requirements to the product backlog and
16:05
adjust prioritization for upcoming
16:07
sprints. D. Partner with a product owner
16:10
to conduct a quick impact analysis with
16:13
stakeholders and decide collectively
16:14
whether to bring the items into the
16:16
current sprint, then update the backlog.
16:19
You can pause the video here if you need
16:21
more time to work on the question. The
16:23
correct answer is C. This question tests
16:26
your ability to respond to mid-sprint
16:28
change while honoring agile roles and
16:30
commitments. Agile teams welcome change,
16:33
but any adjustment must respect the
16:35
product owner's authority and maintain
16:37
focus on the sprint goal. Choice C is
16:40
the best option because it reflects the
16:42
product owner's accountability for
16:44
backlog prioritization. The request is
16:46
captured and factored into future sprint
16:48
planning, keeping team commitments
16:50
stable and respecting agile roles.
16:53
Choice A is incorrect. Although
16:55
well-intentioned, inserting work
16:57
mid-sprint disrupts focus and should
16:59
only be done if it aligns with the
17:01
sprint goal or is a critical blocker.
17:04
Choice B is incorrect. Delaying
17:06
discussion until the sprint review
17:08
ignores agile responsiveness and value
17:10
delivery. Decisions should be made based
17:13
on impact, not ceremony timing. Choice D
17:17
is incorrect. This adds unnecessary
17:19
group decisionmaking to something that
17:21
is within the product owner's
17:23
responsibility, which may lead to role
17:25
confusion and delays. Let's move on to
17:28
the next question if you're ready.
17:30
Question 128. A new stakeholder request
17:34
arrives during the second day of the
17:35
sprint. The request is aligned with
17:37
business objectives but not directly
17:39
related to the current sprint goal. The
17:42
stakeholder insists the team should
17:44
begin work on it immediately due to
17:46
visibility with senior leadership. What
17:48
should the project manager do? A support
17:51
the product owner in deferring the
17:53
request to the backlog for future
17:55
prioritization as it does not align with
17:57
the current sprint goal. B. Encourage
18:00
the product owner to adjust the sprint
18:01
goal to accommodate the new request so
18:04
the team can maintain leadership
18:06
support. C. Facilitate a team discussion
18:09
to determine if the request can be
18:11
squeezed in without impacting sprint
18:13
velocity. D. Recommend adjusting the
18:16
sprint backlog immediately to respond
18:18
quickly to business leadership needs.
18:21
You can pause the video here if you need
18:23
more time to work on the question. The
18:26
correct answer is A. This question tests
18:29
your understanding of how agile
18:30
maintains sprint focus by protecting the
18:33
sprint goal from unplanned changes.
18:36
Agile leaders support the product
18:37
owner's role in prioritization and help
18:40
the team stay committed to delivering
18:41
planned value. A is the best option
18:44
because the product owner manages the
18:46
backlog and must protect the current
18:48
sprint goal unless the new item is
18:50
critical and directly related. Deferring
18:53
the item maintains team focus and
18:55
respects the agile framework. Choice B
18:58
is incorrect. Although adjusting the
19:00
goal may sound reasonable, doing so
19:02
mid-sprint undermines the team's
19:04
original commitment and weakens the
19:06
purpose of having a sprint goal. Choice
19:08
C is incorrect. While team discussions
19:11
are helpful, squeezing in extra work
19:13
without proper prioritization and sprint
19:15
goal alignment leads to overcommitment
19:17
and process breakdown. Choice D is
19:20
incorrect. Reacting quickly to
19:22
stakeholder demands by changing the
19:23
sprint backlog disregards the agreed
19:26
plan and the product owner's
19:27
responsibility for prioritization.
19:30
Let's move on to the next question if
19:31
you're ready. Question 129. Partway
19:35
through a sprint, a senior executive
19:37
bypasses the product owner and directly
19:39
asks a team member to begin working on a
19:41
new customer-driven feature. The team
19:43
member feels pressured and brings the
19:45
request to the project manager. What
19:47
should the project manager do? A. Thank
19:50
the team member for raising the concern
19:52
and advise them to accommodate the
19:54
request as executive input should be
19:56
prioritized.
19:58
B. Work with the scrum master to coach
20:00
the team member on managing stakeholder
20:03
requests without disrupting sprint
20:05
commitments. C. Meet with the executive
20:08
and the team to negotiate a revised
20:09
sprint plan that includes the new
20:11
feature request. D. Ask the product
20:15
owner to immediately add the request to
20:17
the sprint backlog since the team has
20:19
been directly approached by leadership.
20:22
You can pause the video here if you need
20:24
more time to work on the question. The
20:26
correct answer is B. This question tests
20:29
how well you apply agile principles when
20:31
external pressure threatens team
20:33
autonomy. Agile teams are self-managing,
20:36
but leadership influence can challenge
20:38
that balance. A strong project manager
20:41
respects roles and reinforces product
20:43
owner authority while protecting the
20:45
sprint. B is the best option because it
20:48
upholds agile principles. The scrum
20:50
master supports team empowerment and
20:52
shields the team from external
20:54
disruption. Coaching the team member,
20:56
reinforces the sprint commitment and the
20:58
role of the product owner in handling
20:59
new requests. Choice A is incorrect.
21:03
while it acknowledges the team member,
21:04
encouraging them to act on executive
21:06
requests, bypasses the product owner,
21:09
and breaks the sprint structure. Choice
21:11
C is incorrect. Negotiating sprint scope
21:14
mid-sprint undermines the planning
21:16
process and encourages ongoing
21:18
disruption from outside. Choice D is
21:21
incorrect. Adding the work without PO
21:24
prioritization and stakeholder
21:26
discussion creates a precedent that
21:28
weakens the product owner's authority.
21:31
Let's move on to the next question if
21:33
you're ready. Question 130. Midway
21:36
through a sprint, the product owner
21:38
receives a stakeholder request and
21:40
confirms that it aligns with the
21:41
business case and supports the current
21:43
sprint goal. However, the development
21:46
team expresses concern about whether
21:48
they have enough capacity to deliver the
21:50
additional work without compromising
21:51
current sprint commitments. What should
21:54
the project team do? A. Collaborate with
21:57
the product owner to assess available
21:59
capacity and if feasible add the item to
22:01
the sprint backlog. B. Acknowledge the
22:03
team's capacity concerns and prioritize
22:06
the request in the product backlog for
22:08
the next sprint to ensure the team stays
22:10
focused. C. Notify the PMO to revise
22:13
sprint scope and adjust the delivery
22:15
baseline in light of the request. D.
22:18
Work with the product owner and
22:20
facilitate a replanning session with all
22:22
stakeholders to redefine sprint
22:24
commitments. You can pause the video
22:26
here if you need more time to work on
22:28
the question. The correct answer is A.
22:32
This question tests your ability to
22:33
balance agile flexibility with team
22:35
capacity and commitment. When a change
22:37
supports the sprint goal in the business
22:39
case, the team should explore
22:40
incorporating it, but only if it's
22:43
feasible within their current capacity.
22:45
A is the best option because it promotes
22:47
collaboration, respects team input, and
22:50
ensures any addition won't jeopardize
22:52
current sprint work. Agile allows for
22:55
change, but only with team buyin and
22:57
capacity confirmation. Choice B is
23:00
incorrect. While it shows empathy and
23:02
planning, it delays a change that's
23:04
aligned with the sprint goal and might
23:06
be feasible, missing an opportunity to
23:08
deliver value now. Choice C is
23:11
incorrect. Involving the PMO introduces
23:14
unnecessary bureaucracy for a change
23:16
that should be handled within the team.
23:19
Choice D is incorrect. A full replanning
23:21
session is excessive for requests that
23:23
could be integrated without altering the
23:25
sprint goal or commitments. You've now
23:27
completed all 10 questions for the agile
23:30
change management. That's 130 agile
23:33
questions mastered so far. Keep it up.
23:36
You're sprinting toward PMP success.
23:38
When you are ready, I will see you at
23:40
the next topic.