Working software over comprehensive documentation.
复杂文档上的Working soft ware(工作软件)。
This results in no working software until very late in the cycle.
这会导致没有可用的工作软件，直到周期的晚期才会改变。
Regular delivery of working software increases feedback opportunities.
定期的交付工作软件增加反馈机会。
First, the resulting DSL's are easy to transform into working software.
首先，最终得到的DSL很容易变换成可工作的软件。
Working software can be delivered frequently, in weeks rather than months.
可以按照数周而不是数月的间隔频繁地交付可工作的软件。
You can determine this by counting the number of iterations that produced working software.
您通过计算产生的可运行的软件来确定您的答案。
And we switched to an iterative approach where every four weeks we produce working software.
而且我们采用了一种迭代的开发方式，每隔四个星期就会研发新的工作软件。
But we focus far more on this delivery of working software because people can understand that.
但是，我们更加关注工作软件的交付，因为人们能够理解这一点。
Unlike the software engineering course, they weren't motivated to have working software each week.
和软件工程课程不同，他们没有被推动每周都完成一部分软件工作。
Nothing should interfere with the team's delivery of working software by the end of the iteration.
在迭代结束前，任何事情都不应该干扰团队创建可以运行的软件。
If you value comprehensive documentation as much as or more than working software, you are not Agile.
如果您评估的结果是完全文档化过多或者超过工作软件，那么您就不是敏捷的。
The course project will have weekly iterations where working software is expected to be demonstrated.
课程的项目采用每周迭代的方式，期望工作软件成果能够进行演示。
The only true measure of progress on a software development project is the delivery of working software.
衡量软件开发项目进展情况的唯一真正标准就是工作软件的交付。
Pattern: Deployers, or headless processes, can type a single command to generate working software for users.
模式：部署者或无头流程只需输入单一命令，即可为用户生成有效的软件。
Once you have the information for each iteration, you can calculate a working software quotient, W, as follows
一旦您有了每次迭代的这个信息，您可以计算一个运行软件的比值，W，如下所示
The only true measure of progress on a software development project is the regular delivery of working software.
对软件开发项目进展的唯一真正的度量是工作产品的定期交付。
Joint iteration Demos - at the end of each iteration the working software is demonstrated to the project sponsors.
联合迭代演示——在每次迭代结束时，团队会向项目发起人演示可以工作的软件。
Written documents and slideware aren't enough to meet most business requirements-you need working software for that.
已编写的文档和幻灯片演示并不足以满足大多数业务需求——您需要相关的工作软件。
As a general rule, I recommend that development teams check in all of their files necessary to create working software.
作为一般规则，我建议开发团队签入创建软件所需的所有文件。
Where Iw is the number of iterations that produced working software and it is the total number of iterations, as before.
假定Iw是产生可运行软件的迭代数值，I t是总的迭代数，跟前面的一样。
Clearly, Agile is oriented around results: incremental delivery of working software that prioritizes customer requirements.
明显地，敏捷是面向结果的：区分客户需求优先级的工作软件的增量交付。
And this proof comes in the form of actual, working software — even if it's in its early stages, and only partly functional.
这个证据可以带来实际的可工作的软件，即使在早期阶段只能产生部分功能。
I favor short iterations because it emphasizes the need to get real, working software in users' hands to get concrete feedback.
我喜欢短迭代，因为它强调使用户获取真正的、有效的软件以返回具体反馈的需要。
If you have to deliver working software every couple of weeks, I can't fool around for very long on that sort of a project.
如果您必须每隔几个星期就交付软件，我就不可能在这种项目上做傻事。
Delivering working software early shortens the feedback loop between business and IT, allowing them to collaborate more effectively.
及早交付可运行的软件缩短了业务和IT间的反馈周期，这使得他们能够更有效地协同合作。
When EA attempts at iterations occur, they are usually time-box decompositions - there is no working software at the end of the period.
当在一个迭代发生时尝试EA时，常常会割裂时间盒——在这个周期结束时并没有得到可工作的软件。
If doing this allows the team to continue working on their tasks providing value (via working software) to the clients, I'm all for it.
如果这样做能帮助团队继续完成他们的任务并(通过交付可用的软件)提供价值，我完全支持。
Managing all configuration files in a centralized Repository, which makes it possible to generate working software using a Scripted deployment.
这个模式在一个集中的存储库中管理所有配置文件，这样就可以使用ScriptedDeployment生成有效的软件。
If you are in consulting, then perhaps documents and slides are enough, but deploying working software is eventually the goal for most organizations.
如果您从事的是咨询业，也许文档和幻灯片就足够了，但是部署工作软件最终是大多数组织的目标。
If you are in consulting, then perhaps documents and slides are enough, but deploying working software is eventually the goal for most organizations.
如果您从事的是咨询业，也许文档和幻灯片就足够了，但是部署工作软件最终是大多数组织的目标。
应用推荐