We focus far more on this delivery of working software because people can understand that.
我们更加关注工作软件的交付，因为人们能够理解这一点。
The principal measure of progress is working software.
主要的进度度量标准是工作软件。
The second major point is that we focus on working software.
第二个主要区别在于，我们关注的是工作的软件。
Regular delivery of working software increases feedback opportunities.
定期的交付工作软件增加反馈机会。
First, the resulting DSL's are easy to transform into working software.
首先，最终得到的DSL很容易变换成可工作的软件。
If you build software, working software should be the primary measure of progress.
要是你构建软件，可工作的软件应该是首要的进度度量指标。
For instance, is "comprehensive documentation" at the opposite pole from "working software"?
例如，“全面文档化”和“工作软件”相对立吗？
But we focus far more on this delivery of working software because people can understand that.
但是，我们更加关注工作软件的交付，因为人们能够理解这一点。
Nothing should interfere with the team's delivery of working software by the end of the iteration.
在迭代结束前，任何事情都不应该干扰团队创建可以运行的软件。
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.
模式：部署者或无头流程只需输入单一命令，即可为用户生成有效的软件。
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.
作为一般规则，我建议开发团队签入创建软件所需的所有文件。
Rational Team Concert may not be part of this, because the point is to show off working software, not the list of tasks.
RationalTeam Concert可能不是它的一部分，因为重点是展示运行的软件而非任务的列表。
I favor short iterations because it emphasizes the need to get real, working software in users' hands to get concrete feedback.
我喜欢短迭代，因为它强调使用户获取真正的、有效的软件以返回具体反馈的需要。
Delivering working software early shortens the feedback loop between business and IT, allowing them to collaborate more effectively.
及早交付可运行的软件缩短了业务和IT间的反馈周期，这使得他们能够更有效地协同合作。
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.
如果这样做能帮助团队继续完成他们的任务并(通过交付可用的软件)提供价值，我完全支持。
If you are in consulting, then perhaps documents and slides are enough, but deploying working software is eventually the goal for most organizations.
如果您从事的是咨询业，也许文档和幻灯片就足够了，但是部署工作软件最终是大多数组织的目标。
Your basis for this argument is that Agile focuses on delivering working software that puts the priority on customers' most keenly required features.
这一论点的基础就是敏捷关注的是交付有效用的软件，并且将客户最需要的特性作为高优先级处理。
In an ideal world, you want to do the right thing: produce working software that meets the needs of your stakeholders in the most appropriate way possible.
在理想的世界里，你希望做正确的事情：开发可以工作的软件，它能够以最适当的方式满足利益相关者的需求。
In order to drive home iterative development in software engineering, each team must demonstrate working software each Friday rather than attending a lecture.
在软件工程课程中，为了驱动迭代开发，每一支团队必须在每一个周五演示运转的软件，而不仅仅是出席讲座。
Even so, most practitioners would agree that our ability to deliver appropriately featured working software on time and within budget leaves a lot to be desired.
即便如此，大多数从业者还是认同我们按时交付特定软件而不超出预算的能力仍有待大幅提高。
Your iterations will not happen and working software won't get delivered unless you can include and adapt domain variations as part of your development practices.
除非你能引入并把领域变化作为你的开发实践的一部分，否则你的迭代很难进行，工作软件也不会正常发布。
If you are like me and want to produce working software quickly, then the faster you can spot issues that will affect delivery speed, the better, don't you think?
如果您和我一样，想快速地生产出能够工作的软件，那么越快发现影响交付速度的问题越好，难道您不这么认为吗？
An important RUP concept is that you should deliver working software, incrementally, on a priority basis, during each Elaboration and Construction phase iteration.
一个重要的RUP概念是，在细化及构造阶段迭代中，您应该增量地，在优先级的基础上交付工作软件。
Each subteam should be responsible for one or more subsystems, enabling them to work as a small agile team responsible for delivering working software on a timely basis.
每个子团队应该负责一个或几个子系统，让他们可以像小敏捷团队那样，负责按时交付可工作的软件。
Similarly when we write software, we're very good at getting requirements and turning them into code. To turn that beautiful code into working software we need to deploy and test it.
同样地，在编写软件时，也许我们非常擅于总结需求并且将其转换为代码，但我们也需要通过部署和测试把美妙的代码转变成有用的软件。
应用推荐