The definition of a sprint is normally a fixed amount of time in which features are implemented based on priority; so time is fixed and content is variable.
The idea of the sprints is to deliver potentially shippable code; that does not mean that each of these versions must be deployed at the customers. Often there is also another process around this in which for instance validation and deployment can take place. Or every 1 of 2/3/4 sprints is a release sprint.
The idea is that at the end of each sprint you should be deployable, fully and completely (actually, even within the sprint). This release will have reduced functionality, but it should be fully usable within the limits of the partial implementation. The client is not involved, generally, nor the Q/A department (if you have a dedicated one "before final release"). Who gets involved is:
internal business experts (e.g. if you are developing a software for medical data access, you will have someone with direct experience in that field)
internal QA and interface usability experts (they refine the interface, and hunt for bugs of the sprint)
If the client wants to see something, you are always ready to show him. This will keep him interested, give him a sense of progress, of security (you are doing something, and he can see progressive improvements) and eventually he can provide you useful feedback.
我工作的公司（以及我认识的大多数其他敏捷公司）从事 Web 开发，这些问题不是问题。 您的系统管理员在每个冲刺结束时（理论上）直接部署到网络服务器。 在实践中，我说我们会部署大约每一个已完成的冲刺。
The company I work for (and most other Agile companies I know) work in web development, where these issues aren't a concern. Your sys-admin deploys right to the webserver at the end of each sprint (theoretically). In practice, I say we deploy about every other completed sprint.
发布评论
评论（4）
每个冲刺都没有实际部署。 它们是可部署的，但并不总是部署的。
“整个应用程序是否会重新编译，并且客户端是否会使用更新的功能重新安装应用程序？”
当然。 这是一个新版本。 营销人员经常介入并将几个冲刺捆绑到一个大包中进行发布。
“应用程序是否使用某种框架设计，新功能可以简单地插入当前安装的应用程序中？”
很少。
Each sprint isn't actually deployed. They're deployable, but not always deployed.
"Does the entire application get recompiled and the client reinstall the application with the updated features?"
Of course. It's a new release. Marketing often intervenes and bundles several sprints into a big package for release.
" Is the application designed using some sort of framework were the new features can simply be plugged into the currently installed application? "
Rarely.
冲刺的定义通常是一段固定的时间，在这段时间内根据优先级实现功能； 所以时间是固定的，内容是可变的。
冲刺的想法是交付潜在的可交付代码； 这并不意味着这些版本中的每一个都必须部署在客户处。 通常还有另一个围绕此的过程，例如可以在其中进行验证和部署。 或者每 2/3/4 个冲刺中的 1 个都是发布冲刺。
The definition of a sprint is normally a fixed amount of time in which features are implemented based on priority; so time is fixed and content is variable.
The idea of the sprints is to deliver potentially shippable code; that does not mean that each of these versions must be deployed at the customers. Often there is also another process around this in which for instance validation and deployment can take place. Or every 1 of 2/3/4 sprints is a release sprint.
这个想法是，在每个冲刺结束时，您应该可以完全部署（实际上，即使在冲刺内）。 此版本将减少功能，但在部分实现的限制内应该完全可用。 一般来说，客户和 Q/A 部门都不参与（如果您在“最终发布之前”有专门的部门）。 参与的人员包括：
如果客户想看什么，你随时准备向他展示。 这会让他保持兴趣，给他一种进步感、安全感（你正在做某事，他可以看到逐步的改进），最终他可以为你提供有用的反馈。
The idea is that at the end of each sprint you should be deployable, fully and completely (actually, even within the sprint). This release will have reduced functionality, but it should be fully usable within the limits of the partial implementation. The client is not involved, generally, nor the Q/A department (if you have a dedicated one "before final release"). Who gets involved is:
If the client wants to see something, you are always ready to show him. This will keep him interested, give him a sense of progress, of security (you are doing something, and he can see progressive improvements) and eventually he can provide you useful feedback.
我工作的公司（以及我认识的大多数其他敏捷公司）从事 Web 开发，这些问题不是问题。 您的系统管理员在每个冲刺结束时（理论上）直接部署到网络服务器。 在实践中，我说我们会部署大约每一个已完成的冲刺。
The company I work for (and most other Agile companies I know) work in web development, where these issues aren't a concern. Your sys-admin deploys right to the webserver at the end of each sprint (theoretically). In practice, I say we deploy about every other completed sprint.