敏捷设计并不是要在项目开始阶段忽略设计。
Agile design doesn't try to ignore design at the beginning of a project or phase.
阐明了基于协同与商务的产品敏捷设计方法。
The product agile design approach based on collaboration and commerce is discussed.
并且应用好“面向对象设计”是做到敏捷设计的关键。
And, applying a good "Object Oriented design" is the key to achieve such a smart design.
讨论了需求的获取、系统的敏捷设计、代码的重构等过程。
The obtaining of requirements, construct structure of system, refractoring the code base on agile method is discussed.
这给敏捷设计会话设置了一个强制性目标：眼光要超越单个项目的范围。
This gives the Agile design sessions a compelling goal: To look beyond the scope of a single project.
论文主要研究筒型结构件夹具的敏捷设计方法和夹具性能分析方法。
The agile design method of fixture for cylinder-shaped framework part and the analysis approach of fixture performance are mainly researched in the dissertation.
会议的问答部分提出的一个共同的主题就是，将敏捷设计融入到一个还不太具备敏捷性的生态系统中。
One common theme that arises during the talk's question-and-answer portion concerns fitting agile design into an ecosystem that hasn't quite swallowed the agile red pill.
敏捷设计反对这个观点，因为人们倾向于过高地估计他们在早期制定精确决策的能力，因而他们将遭受不断扩大的后果。
Agile design objects to this notion because people tend to overestimate their ability to make accurate decisions early, and they suffer the ever-expanding consequences later.
您的设计必须是能够指导业务开发和决策制定的蓝图，并且要足够敏捷以快速改变方向。
Your design must be a blueprint that can guide business development and decision making, plus be nimble enough to change course quickly.
敏捷流程依赖频繁的重构和单位测试来改进设计。
Agile processes rely on frequent refactoring and unit tests to improve designs.
您可能对这些宣传信以为真，并开始在考虑到敏捷性的情况下着手设计和规划。
You may have bought into the hype and started designing and planning with agility in mind.
图1显示了敏捷项目中需求定义与设计的迭代循环过程。
Figure 1 illustrates an iterative cycle for requirement definition and design for agile projects.
也许你已经有了一个设计流程，不过我还是建议你考虑“敏捷法”。
You might already have one. However, I would suggest that you consider the Agile approach.
我认为[敏捷开发]对面向对象的设计有一些影响，当人们[使用]……增量式开发，而不是试图[事先弄清楚所有需求]时。
I think some of the influence [on agile development] was object-oriented design, when people [used]... incremental development, rather than trying to figure out [all the requirements a priori].
当设计好之后，敏捷业务过程能够允许业务代理为最通用的变化业务价值表达一组敏捷点。
When well designed, agile business processes can allow business agents to express a set of agility points for the most commonly changed business values.
在敏捷软件开发的世界中，设计模式的使用、重构，它们都是使用适应性重用的例子。
In the Agile software world the use of design patterns and refactoring are examples of adaptive reuse applied.
另外，经典的前敏捷开发是个体独自“拥有”那些设计和编码。
Additionally, classical, pre-agile development often involves code and designs that are exclusively "owned" by individuals.
在编写代码时，不需要在测试期间为了查看预期的优势而去掌握诸如敏捷编程、极限编程或测试优先设计等方法。
You don't need to commit yourself to methodology such as agile programming, extreme programming, or test-first design to see the advantages of planning for testing when you are writing your code.
依赖于紧急设计的敏捷方法学则尝试一种不同的方法。
Agile methodologies that rely on emergent design try a different approach.
不是因为有些产品的开发还不能敏捷实践，我就在硬件项目中用过敏捷方法，包括芯片设计项目。
Not because there are products that are not ready to use agile practices. I’ve even used agile approaches on hardware products, including chip design.
在敏捷开发项目的计划和设计之前学习有关全球化知识对于项目的成功起着关键性的作用。
Learning about globalization before planning and designing for agile development projects is the key to project success.
要记住：敏捷没有强制如何定义概念或是整体的设计方向，但是很善于执行具体的设计研究和良好的规划。
Remember, Agile does not mandate how to define concepts or overall design direction, but it is a great way to execute on solid design research and well laid plans.
设计模式的书籍在那时同时出版，而且，设计模式比任何敏捷书籍都成功。
The design patterns book came out at the same time and design pattern was a bigger success than any of the agile books.
敏捷项目需要真正的多面手来担当测试人员：拥有能读懂需求、设计和代码的技能的人。
Agile projects require true generalists as testers: people who have requirements -, design -, and code-understanding skills.
敏捷开发者应该是有设计能力的，而敏捷架构师应该是有编写代码的技能的。
Agile developers are expected to have design skills, and agile architects are expected to have coding skills.
这条设计原则非常类似敏捷经常用在软件开发中的设计原则(分离关注点，避免浪费等)。
This design principle is very similar to agile design principles (separation of concerns, avoid waste etc.) that are often used in software development.
因此，您需要密切考虑您的设计有多敏捷。
As a result, you need to take a close look at how nimble your design is.
可用性专家和《可用性工程》的作者JakobNielsen，最近提出了这样的担心：敏捷方法对使用传统方式设计可用性会造成威胁。
Jakob Nielsen, usability guru and author of usability Engineering, raises the concern that Agile methods are a threat to traditional approaches to designing usability.
除此之外，Jeff发现他的角色发生了变化：“由于我开始在敏捷团队内工作，我变得喜欢协同设计。”
In addition, Jeff finds his role has changed: "as I've begun to work within Agile teams, my approach has changed to favor collaborative design."
设计规格真的如此不敏捷?
应用推荐