什么是范围渐变？
Progressive elaboration should not be confused with scope creep.
请勿将逐步完善与范围潜变混淆。
In my work as a WebSphere Consultant, scope creep is of Paramount concern.
在我作为WebSphere顾问的工作中，范围渐变是我最为关注的内容。
Scope creep is a natural phenomenon in enterprise software development.
范围渐变是企业软件开发中的正常现象。
It is described early in the project and made more detailed through scope creep.
也是在项目的早期被描述出来并随着范围的蔓延而更加详细。
I have seen some extremely detailed requirements documents that don't help avoid scope creep.
我曾见过一些虽然非常详细但却无助于避免范围渐变的需求文档。
Follow this line of reasoning, however, and you will soon meet your Nemesis: scope creep.
然而，照这个逻辑推理下去，你很快会受到惩罚：项目范围蔓延。
The definitional scope creep afflicting the machine learning arena mirrors these challenges.
在定义上的范围蔓延困扰着机器学习反映了这些挑战。
If the requirements are loosely defined, then consider the risk of scope creep exponentially increased.
如果没有准确地定义需求，范围渐变的风险指数将上升。
Having this discipline and convincing the project stakeholders of this perspective is key to avoiding scope creep.
您必须采用此规程并说服项目参与者相信此观点，这是避免范围渐变的关键所在。
Many projects fail because of scope creep, and the project manager needs to be diligent in guarding against it.
许多项目失败的原因正是因为需求渐变，而项目经理需要勤快些，对此加以防范。
As the definition above stated, the fundamental cause of scope creep more often than not revolves around requirements.
如上面的定义所述，范围渐变的基本原因时常涉及需求这一主题。
This approach, sometimes called in-place reengineering, reduces the risks from scope creep and unforeseen complications.
这个方法有时被称为就位再工程，可减少由于相应范围无控制地扩大或未预见到复杂情况而导致的风险。
This is important because it helps to avoid "scope creep," the addition of new requirements as the project progresses.
这是很重要的，因为它有助于避免“超出范围”，即，项目进展的附加的新需求。
Scope creep (also called requirement creep) in project management refers to uncontrolled changes in a project's scope.
项目管理中的范围渐变(也称为需求渐变)是指项目范围的无控制更改。
You can review the report to determine the amount of scope creep that has occurred throughout an iteration or over time.
可以检查报表，以确定在整个迭代期间或一段时间内的范围扩张量。
Adding requirements without clear justification constituted scope creep and could have a negative impact on our schedule and budget.
添加需求而没有清晰的调整将导致项目范围的蔓延并对项目的时间计划和预算有着负面的影响。
A critical best practice for avoiding scope creep, therefore, is to facilitate the change of requirements at any stage of the development process.
因此，防止范围渐变的一个关键最佳实践是，在开发过程的任一阶段都能够方便地进行需求更改。
Scope creep is a term used to define a series of small scope changes that are made to the project without scope-change management procedures being used.
范围蔓延是一个术语，用以定义在未经范围变更管理过程而进行的针对项目的一系列小型的范围变更。
However, this approach can lead to scope creep, and result in the framework becoming a DE facto custom-developed service Gateway or web services-compliant Broker.
然而，这种方法可能引起范围蠕变(scope creep)，并最终导致该框架实际上变成了用户开发的服务网关或Web服务兼容代理。
Recently, we had a project due at the end of the month, but due to "scope creep" that was outside our control on another initiative, the project had to be delayed.
最近，我们有一个本月底到期的项目，但由于“范围蔓延”超出了我们对其他行动的控制，该项目不得不延迟。
In particular, the area of security posed a huge opportunity for scope creep, so we had to work closely with ASDI to understand exactly what their security needs were.
尤其是，安全方面对项目范围的蔓延产生了巨大的机会，因此我们必须与asdi密切的工作以准确的理解他们需要什么样的安全。
Targeting scope creep early and knowing best practices for enabling an organization to combat it is often a key insight to bringing a project into that 5-15% bracket of solid success.
早些关注范围渐变，并了解如何使组织防止范围渐变的最佳实践，通常是将项目带入那5- 15%可靠成功的关键。
Targeting scope creep early and knowing best practices for enabling an organization to combat it is often a key insight to bringing a project into that 5-15% bracket of solid success.
早些关注范围渐变，并了解如何使组织防止范围渐变的最佳实践，通常是将项目带入那5- 15%可靠成功的关键。
应用推荐