原文：https://deviq.com/feedback

1. 反馈（Feedback）

反馈（Feedback）是极限编程的核心价值之一。

Feedback is an Extreme Programming value:

我们将通过交付可工作的软件认真对待每一次迭代承诺。我们会尽早演示我们的软件，然后经常仔细聆听（客户的反馈）并进行所需的更改。我们将讨论该项目，并使我们的流程适应它，而不是让客户适应我们。

We will take every iteration commitment seriously by delivering working software. We demonstrate our software early and often then listen carefully and make any changes needed. We will talk about the project and adapt our process to it, not the other way around.

一些实践被设计为全面地增加反馈并减少反馈回路（Feedback Loop，采取行动与收到反馈之间的时间）。例如，结对编程（Pair Programming）要比计划的代码审查（Code Review）提供更多和更快的反馈，持续集成（Continuous Integration，CI）与不频繁的集成相比可提供更快的问题反馈，小版本发布（Small Releases）则提供终端用户对软件的快速反馈。

Several practices are designed to increase feedback overall and reduce the feedback loop (the time between when an action is taken and when feedback on it is received). For example, pair programming provides more and faster feedback than scheduled code reviews, continuous integration provides faster feedback on integration problems than infrequent integration, and small releases provide rapid feedback from end users of working software.

频繁的交付可工作软件会减少开发团队开始实施该功能与用户使用该功能之间的时间。很有可能开发人员误解了用户想要的功能，或者用户将根据目前已交付的功能来更新他们想要的功能。收到反馈的时间越早，开发团队就能越快和更便宜地修改软件以适应新的需求。

Frequent delivery of working software decreases the amount of time between when the development team begins implementing a feature and when that feature is in users’ hands. It’s quite likely that either the developers misunderstood exactly what the user wanted, or that the user will update what they want based on what has been delivered so far. The sooner this feedback is received, the faster and cheaper it is for the development team to modify the software to suit the new requirements.

2. 关于反馈的名人名言

1. “作为软件开发人员，我们可以通过两种方式失败：我们可以错误地建造东西，或者我们可以建造错误的东西。” —— 史蒂夫·史密斯

   “As software developers, we can fail in two ways: we can build the thing wrong, or we can build the wrong thing.” – Steve Smith