In Kanban, if there is an urgent request to implement or a really important user story, the team can just put it on top of the queue.
有了看板，如果来了一个紧急的请求需要实现，或者一个非常重要的用户故事，团队只需把它放在队列的顶端即可。
Scaling this model up to a large administration team, lots of queue managers, or large Numbers of queues and channels, exacts an increasingly large toll on each queue manager.
为了对此模型进行扩展，以用于大型管理团队、大量队列管理器或大量队列和通道，需要对每个队列管理器增加大量的负载。
With a large team and lots of queue managers, tracking down a specific adverse event is a practical impossibility when there are no logs, or when the logs are distributed across many workstations.
对于大型团队和大量队列管理器的情况，在没有日志或日志分布在很多工作站时，可能追溯到具体的不良事件。
In that case a completely different team than the team that administers WebSphere MQ would control security for the queue manager.
对于这种情况，可以由WebSphereMQ管理团队之外的团队来控制队列管理器的安全性。
If the WebSphere MQ administration team USES a desktop client to access the queue managers, the configurations proposed here will break that access.
如果WebSphereMQ管理团队使用桌面客户端访问队列管理器，此处所建议的配置将阻止此访问。
Analysis of change requests can be a drain on resources, and it is important that the change request queue does not put undue demands on the team and affect the project timeline.
对更改请求进行分析可能会耗尽资源，并且更改请求队列一定不能对团队提出过度的要求并影响项目时间线。
If you were in a premade team with the player who queue dodged, your partner will receive a loss, a leave, and be subject to the standard time penalty for queue dodging.
如果你是5人开黑的情况下，你的队友离开了游戏，那么他会得到一次失败、一次离开的相应记录以及退出时间惩罚。
If you were in a premade team with the player who queue dodged, your partner will receive a loss, a leave, and be subject to the standard time penalty for queue dodging.
如果你是5人开黑的情况下，你的队友离开了游戏，那么他会得到一次失败、一次离开的相应记录以及退出时间惩罚。
应用推荐