Question19 In an Agile project, how does the team handle changes to requirements late in development?Select one alternative: Changes are discouraged to maintain the original project schedule and scope. Changes are welcomed and incorporated, as Agile prioritizes customer collaboration and responding to evolving needs. The team can only accept changes if they don’t affect the budget or timeline. The team conducts a formal change request process to determine the feasibility of implementing the change. ResetMaximum marks: 1

Question

BlackTom AI · Accepted Answer

Question: In an Agile project, how does the team handle changes to requirements late in development?

Option 1: Changes are discouraged to maintain the original project schedule and scope.
- This view runs counter to Agile principles. Agile methodologies embrace change, particularly late in development, because new insights and customer feedback can deliver higher value. Treating changes as something to be discouraged can hinder adaptability and customer value.

Option 2: Changes are welcomed and incorporated, as Agile prioritizes customer collaboration and responding to evolving needs.
- This statement aligns with core Agile concepts. Agile processes value customer collaboration and responsiveness to change over rigid adherence to a fixed plan. Late changes are expected to be evaluated and, if valuable, incorporated into the product backlog and iterations.

Option 3: The team can only accept changes if they don’t affect the budget or timeline.
- While budget and timeline considerations exist, Agile does not gate changes on maintaining those constraints as a condition for acceptance. The prioritization is about value and adaptiveness; if a change provides high value, it may be pursued even if it influences budget or schedule, usually through re-prioritization and iteration planning.

Option 4: The team conducts a formal change request process to determine the feasibility of implementing the change.
- Agile environments typically minimize formal change control in favor of lightweight, collaborative decision-making (e.g., product owner prioritization, backlog refinement, and sprint planning). A formal change request process is more characteristic of rigid traditional methodologies, not standard Agile practice.

Summary of reasoning: The most compatible stance with Agile is that changes are welcomed and incorporated because Agile emphasizes customer collaboration and responsiveness to change. The other options misrepresent Agile by advocating discouragement, rigid constraints, or formal change control processes that slow adaptability.

查看解析

登录即可查看完整答案

类似问题

A drawback of Agile development is:

A major advantage of Agile over Waterfall is:

Which of the following best describes Agile development?

Which of the following best describes the agile approach to failure?

In agile thinking, what is the purpose of continuous improvement?

What does the agile mindset prioritize over individual success?

A(n) Blank ______ methodology aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements.

更多留学生实用工具

考试浏览器助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单