WGU E007 AGILE METHODOLOGY
PERFORMANCE ASSESSMENT | COMPLETE
AGILE TRANSFORMATION SCENARIO,
SCRUM, KANBAN & LEAN ANALYSIS |
2026/2027 UPDATED [QUESTIONS 1–
100] AND ANSWERS | DETAILED
RATIONALES
2. Introduction
The WGU E007 Agile Methodology Performance Assessment practice bank is
designed to help learners strengthen their understanding of Agile principles, iterative
delivery, team collaboration, and organizational transformation. It is intended for
students preparing to analyze Agile business scenarios, evaluate project-management
approaches, and develop recommendations grounded in Agile, Scrum, Kanban, and
Lean practices.
Agile methodologies are important because organizations often need to respond to
changing customer needs, uncertain requirements, evolving priorities, and frequent
feedback. Successful implementation requires more than adopting ceremonies or tools;
it involves changing how teams plan, collaborate, measure progress, manage work,
and deliver value.
This practice bank uses scenario-based multiple-choice questions to develop applied
reasoning across Agile values and principles, Scrum accountabilities and events,
Kanban flow management, Lean thinking, backlog refinement, estimation,
stakeholder engagement, risk management, metrics, and organizational change.
Detailed rationales explain why the best answer fits the scenario and why the
alternatives are less appropriate.
Use these questions to practice identifying problems, evaluating trade-offs, and
justifying recommendations. The material is an original study resource, not an official
WGU assessment or a verified answer key. Confirm the current assessment
requirements and rubric in your WGU course materials before submitting any
performance-assessment work.
3. Core domains tested
1.
,Agile foundations: Agile values, principles, adaptability, and iterative delivery.
2.
3.
Agile transformation: Organizational readiness, leadership support, culture,
resistance, and change management.
4.
5.
Scrum framework: Accountabilities, events, artifacts, commitments, and
empirical process control.
6.
7.
Kanban methodology: Visualization, work-in-progress limits, flow, pull
systems, and delivery predictability.
8.
9.
Lean principles: Value identification, waste reduction, continuous
improvement, and systems thinking.
10.
11.
Requirements and backlogs: User stories, acceptance criteria, prioritization,
and refinement.
12.
13.
Planning and estimation: Relative estimation, capacity, forecasting, and sprint
planning.
14.
15.
Stakeholder collaboration: Feedback, transparency, product goals, and
expectation management.
16.
17.
Quality and delivery: Definition of Done, technical debt, testing, integration,
and incremental releases.
, 18.
19.
Metrics and performance: Velocity, cycle time, lead time, throughput, and
cumulative flow.
20.
21.
Risk and dependency management: Early risk identification, impediments,
uncertainty, and cross-team coordination.
22.
23.
Continuous improvement: Retrospectives, experiments, root-cause analysis,
and measurable improvement.
24.
25.
Scenario analysis: Selecting and justifying an Agile approach for a particular
organizational problem.
26.
4. QUESTIONS 1–100
Agile foundations and principles
Q1: A software company completes projects using detailed
annual plans. Customer requirements frequently change, but
teams are penalized whenever they deviate from the original
scope. What is the most appropriate Agile transformation
recommendation?
A) Increase the number of approval layers for changes. B) Adopt iterative delivery,
frequent stakeholder feedback, and reprioritization based on business value. C) Freeze
requirements earlier to prevent customer involvement. D) Eliminate planning because
Agile teams should not plan.
Rationale: B is correct because Agile supports adapting to change while delivering
value incrementally. A adds bureaucracy, C conflicts with responding to changing
needs, and D misrepresents Agile: planning remains essential but is revisited as new
information emerges.
, Q2: A product team delivers every sprint but discovers that
customers rarely use the completed features. Which action
best addresses the underlying problem?
A) Increase the number of features delivered per sprint. B) Measure success
exclusively through developer utilization. C) Validate assumptions with users and
prioritize work according to demonstrated customer value. D) Extend every sprint
until all requested features are complete.
Rationale: C is correct because delivery volume does not guarantee useful outcomes.
A may increase waste, B measures activity rather than value, and D undermines the
timeboxed feedback cycle without resolving whether the features are needed.
Q3: A business sponsor asks an Agile team to commit to a
fixed scope, fixed date, and fixed cost despite substantial
uncertainty. What is the strongest response?
A) Guarantee all three constraints without assessing risk. B) Refuse to provide any
forecast. C) Promise the scope and quietly reduce testing if the deadline becomes
difficult. D) Explain the trade-offs, forecast using available evidence, and identify
options for adjusting scope, time, or resources.
Rationale: D is correct because transparent forecasting and explicit trade-offs support
informed decisions. A creates an unsupported commitment, B avoids useful planning,
and C sacrifices quality and hides risk.
Q4: A team releases a minimum viable product (MVP). Which
outcome best indicates that the MVP served its intended
purpose?
A) It contains every feature originally proposed. B) It has the largest possible
codebase. C) It tests a meaningful product hypothesis with the smallest practical
investment and produces useful learning. D) It eliminates the need for future customer
feedback.
Rationale: C is correct because an MVP is intended to validate assumptions and
generate learning. A and B emphasize size rather than learning, while D contradicts
the ongoing feedback required for product development.
Q5: An organization introduces daily stand-ups but retains
centralized decisions, delayed releases, and punishment for
reporting problems. Why is the transformation unlikely to
succeed?
A) Daily stand-ups are incompatible with Agile. B) Agile requires every decision to
be made by the executive team. C) Ceremonies alone do not change the organizational
PERFORMANCE ASSESSMENT | COMPLETE
AGILE TRANSFORMATION SCENARIO,
SCRUM, KANBAN & LEAN ANALYSIS |
2026/2027 UPDATED [QUESTIONS 1–
100] AND ANSWERS | DETAILED
RATIONALES
2. Introduction
The WGU E007 Agile Methodology Performance Assessment practice bank is
designed to help learners strengthen their understanding of Agile principles, iterative
delivery, team collaboration, and organizational transformation. It is intended for
students preparing to analyze Agile business scenarios, evaluate project-management
approaches, and develop recommendations grounded in Agile, Scrum, Kanban, and
Lean practices.
Agile methodologies are important because organizations often need to respond to
changing customer needs, uncertain requirements, evolving priorities, and frequent
feedback. Successful implementation requires more than adopting ceremonies or tools;
it involves changing how teams plan, collaborate, measure progress, manage work,
and deliver value.
This practice bank uses scenario-based multiple-choice questions to develop applied
reasoning across Agile values and principles, Scrum accountabilities and events,
Kanban flow management, Lean thinking, backlog refinement, estimation,
stakeholder engagement, risk management, metrics, and organizational change.
Detailed rationales explain why the best answer fits the scenario and why the
alternatives are less appropriate.
Use these questions to practice identifying problems, evaluating trade-offs, and
justifying recommendations. The material is an original study resource, not an official
WGU assessment or a verified answer key. Confirm the current assessment
requirements and rubric in your WGU course materials before submitting any
performance-assessment work.
3. Core domains tested
1.
,Agile foundations: Agile values, principles, adaptability, and iterative delivery.
2.
3.
Agile transformation: Organizational readiness, leadership support, culture,
resistance, and change management.
4.
5.
Scrum framework: Accountabilities, events, artifacts, commitments, and
empirical process control.
6.
7.
Kanban methodology: Visualization, work-in-progress limits, flow, pull
systems, and delivery predictability.
8.
9.
Lean principles: Value identification, waste reduction, continuous
improvement, and systems thinking.
10.
11.
Requirements and backlogs: User stories, acceptance criteria, prioritization,
and refinement.
12.
13.
Planning and estimation: Relative estimation, capacity, forecasting, and sprint
planning.
14.
15.
Stakeholder collaboration: Feedback, transparency, product goals, and
expectation management.
16.
17.
Quality and delivery: Definition of Done, technical debt, testing, integration,
and incremental releases.
, 18.
19.
Metrics and performance: Velocity, cycle time, lead time, throughput, and
cumulative flow.
20.
21.
Risk and dependency management: Early risk identification, impediments,
uncertainty, and cross-team coordination.
22.
23.
Continuous improvement: Retrospectives, experiments, root-cause analysis,
and measurable improvement.
24.
25.
Scenario analysis: Selecting and justifying an Agile approach for a particular
organizational problem.
26.
4. QUESTIONS 1–100
Agile foundations and principles
Q1: A software company completes projects using detailed
annual plans. Customer requirements frequently change, but
teams are penalized whenever they deviate from the original
scope. What is the most appropriate Agile transformation
recommendation?
A) Increase the number of approval layers for changes. B) Adopt iterative delivery,
frequent stakeholder feedback, and reprioritization based on business value. C) Freeze
requirements earlier to prevent customer involvement. D) Eliminate planning because
Agile teams should not plan.
Rationale: B is correct because Agile supports adapting to change while delivering
value incrementally. A adds bureaucracy, C conflicts with responding to changing
needs, and D misrepresents Agile: planning remains essential but is revisited as new
information emerges.
, Q2: A product team delivers every sprint but discovers that
customers rarely use the completed features. Which action
best addresses the underlying problem?
A) Increase the number of features delivered per sprint. B) Measure success
exclusively through developer utilization. C) Validate assumptions with users and
prioritize work according to demonstrated customer value. D) Extend every sprint
until all requested features are complete.
Rationale: C is correct because delivery volume does not guarantee useful outcomes.
A may increase waste, B measures activity rather than value, and D undermines the
timeboxed feedback cycle without resolving whether the features are needed.
Q3: A business sponsor asks an Agile team to commit to a
fixed scope, fixed date, and fixed cost despite substantial
uncertainty. What is the strongest response?
A) Guarantee all three constraints without assessing risk. B) Refuse to provide any
forecast. C) Promise the scope and quietly reduce testing if the deadline becomes
difficult. D) Explain the trade-offs, forecast using available evidence, and identify
options for adjusting scope, time, or resources.
Rationale: D is correct because transparent forecasting and explicit trade-offs support
informed decisions. A creates an unsupported commitment, B avoids useful planning,
and C sacrifices quality and hides risk.
Q4: A team releases a minimum viable product (MVP). Which
outcome best indicates that the MVP served its intended
purpose?
A) It contains every feature originally proposed. B) It has the largest possible
codebase. C) It tests a meaningful product hypothesis with the smallest practical
investment and produces useful learning. D) It eliminates the need for future customer
feedback.
Rationale: C is correct because an MVP is intended to validate assumptions and
generate learning. A and B emphasize size rather than learning, while D contradicts
the ongoing feedback required for product development.
Q5: An organization introduces daily stand-ups but retains
centralized decisions, delayed releases, and punishment for
reporting problems. Why is the transformation unlikely to
succeed?
A) Daily stand-ups are incompatible with Agile. B) Agile requires every decision to
be made by the executive team. C) Ceremonies alone do not change the organizational
