什么是变更请求管理工具？
谁能告诉我什么是变更请求管理工具以及向此工具提交变更请求时涉及什么？
Can anyone please tell what is change request management tool and what is involved when a change request is submitted to this tool?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
变更请求管理工具供用户请求对软件进行变更。
当软件开发过程开始时，开发团队和用户（或其部门）之间就软件的功能达成一致。 这称为要求。 一旦每个人都同意需求（最好是书面形式），开发就开始了。
如果用户发现他们在开发过程中的任何时候需要更改需求，他们就会提出更改请求。 这些请求被记录到变更请求管理工具中。 开发团队审查请求并与用户就更改进行协商（需要多少额外的时间或金钱），直到达成协议。
软件部署后，用户可能会发现其他更改。 他们将请求记录在变更请求管理工具中。 开发团队定期审查新的变更请求，并与用户就哪些请求将包含在软件的下一个版本中达成协议。
使用变更请求管理工具有助于管理“范围蔓延”。 它有助于双方评估软件所需的额外工作，并使整个过程井井有条。
如果操作正确，将会记录所请求的更改、所做的更改以及当前正在进行的更改。 软件改进将被优先考虑。
A change request management tool is for users to request changes in the software.
When the software development process begins, there is an agreement between the development team and the users (or their department) about what the software will do. This is called the requirements. Once everybody agrees on the requirements, preferably in writing, development begins.
If the users discover that they need to change the requirements at any point during development, they make a change request. Those requests are logged into the change request management tool. The development team reviews the request and negotiates with the users over the change -- how much additional time or money it will take -- until they reach an agreement.
Once the software has been deployed, there may be additional changes identified by the users. They record their requests in the change request management tool. Periodically, the development team reviews the new change requests and makes an agreement with the users about which of those requests will be included in the next release of the software.
Using the change request management tool help to manage "scope creep". It helps both sides to assess the additional work needed on the software, and keeps the whole process organized.
If done correctly, there will be a record of the changes requested, the changes made, and the changes currently in process. Software improvements will be prioritized.
它与错误跟踪工具相似或相同。 可能发生的事情包括：
有人查看请求（“某人”可能是产品经理、项目经理和/或开发团队领导）并决定是否进一步考虑
如果请求没有立即被拒绝，那么它会被传递给某人（可能是架构师或开发团队负责人），谁将评估其可行性并说明实现它所需的工作/时间表/资源
如果预期收益超过预期成本等，那么它将被批准并添加到开发计划中，最终分配给可用的开发人员
当它经历这些不同的阶段并被考虑时由不同的人添加他们的意见和/或其他细节和文档：例如，当它最终到达测试所请求变更的开发实施的 QA 人员时，QA 人员不仅会看到原始请求，还有来自项目经理、架构师、开发人员等的评论。
It's similar or identical to a bug-tracking tool. Things that might happen include:
Someone looks at the request (the "someone" might be a product manager, project manager, and/or development team leader) and decides whether to consider it further
If the request isn't immediately rejected then it's passed to someone (maybe the architect or the development team lead), who will assess its feasability and say what the effort/schedule/resources required to implement it would be
If the expected benefit exceeds the expected cost etc then it will be approved and added to the development schedule, and eventually assigned to an available developer
As it goes through these various stages and is considered by various people, the people will add their opinions, and/or additional details and documentation: for example by the time it finally reaches the QA person who tests the developed implementation of the requested change, the QA erson will see not only the original request, but also comments from the project manager, the architect, the developer, etc.
它基本上是一个数据库，可以帮助您防止所有“待办事项”项目从桌子上掉下来。
作为一项附加福利，它提供了一种评估您的开发团队执行流程的情况的方法。
It's basically a database that helps keep all your 'todo' items from falling off the table.
And also as a fringe benefit, provides a means of assessing how well your development team is executing their process.
您可以使用问题管理工具（错误跟踪器）作为更改请求工具
，或者您可以使用低保真协议并使用协议（即只是在 Word 文档中写下的过程），
我与客户一起使用的是以下内容的组合： sla（服务级别协议）和变更请求协议：'维护块 - 管理变更请求
--LM
you can use an issue management tool (bug tracker) as a change request tool
or you can go lo-fi and use a protocol instead (i.e. just a procedure written down in a word document)
what i use with my clients is a combination of sla (service level agreement) and change request protocol: 'Maintenance Blocks' - Managing Change Requests
--LM