You need to earn a living; the client needs a computing solution: the client has the right to make sure that the solution you will supply fits his needs. Changes and additions after and agreement has been reached, reflects on your ability to analyze the user's requirements into a system design, in that failed to investigate those requirements to sufficient depth and detail: you need to do this meticulously and obtain a written sign-off agreement on your system design from the client.
Legal perspective:
You should pin the scope of the project down, and get the client to sign an agreement of that scope. Once you have that agreement, anything not covered by it constitutes a new project.
Business perspective:
Do you want to continue doing business (with the current as well as future clients)? You need to do an evaluation of the impact adding the new required functionality will have on the current project: if the impact is small, then do it, but tell the client - in writing - that you are doing him a favor; if the impact is larger then you must negotiate with the client, outlining the issues, and either adapt your current agreement, or make a new one. What you do not want to do is to antagonize your client.
Lastly: "The client is always right." - (up to the point where you have to give up and just go away.)
This question cannot be given a blanket answer. It depends project to project.
Examples:
Client has money to burn, long timeline, no other projects on the go, I am very flexible.
Client is tight with $$, short timeline, other projects on the go, I am hardly flexible at all.
Other factors come into play as well, such as the process that has been chosen for the project. For example, you will be more flexible in an agile process, less flexible in a waterfall approach.
I think the answer to your question comes down to how flexible your client is with time and cost because you can not change the scope of a project with out having an affect of these two things.
Scope creep can be a good thing if it allows the project to evolve and has an overall positive affect on the outcome of a project. You really need a formal change process in place to manage scope changes.
If it's a fixed-bid project, then I am open to negotiation and will agree to expanding the scope in one area in exchange for reducing it somewhere else, or for an increase in budget, or in exchange for some other consideration.
If it's for a client that I'm billing hourly, then they can expand the scope all they want, since I'll be charging them for the time I spend on it regardless of whether it's within the original definition of the project or not.
发布评论
评论（5）
总体观点：
你需要谋生； 客户需要一个计算解决方案：客户有权确保您提供的解决方案适合他的需求。 达成协议后的更改和添加反映了您将用户需求分析到系统设计中的能力，因为未能足够深入和详细地调查这些需求：您需要一丝不苟地做到这一点并获得书面签字与客户就您的系统设计达成一致。
法律角度：
您应该确定项目的范围，并让客户签署该范围的协议。 一旦达成该协议，该协议中未涵盖的任何内容都将构成新项目。
业务角度：
您想继续（与当前和未来的客户）开展业务吗？ 您需要评估添加新的所需功能对当前项目的影响：如果影响很小，那就这样做，但以书面形式告诉客户，您是在帮他一个忙；如果影响很小，那就这样做，但要以书面形式告诉客户，您是在帮他一个忙； 如果影响较大，那么您必须与客户进行谈判，概述问题，并调整当前协议或制定新协议。 您不想做的就是与您的客户对抗。
最后：“客户永远是对的。” -（直到你不得不放弃并走开。）
General perspective:
You need to earn a living; the client needs a computing solution: the client has the right to make sure that the solution you will supply fits his needs. Changes and additions after and agreement has been reached, reflects on your ability to analyze the user's requirements into a system design, in that failed to investigate those requirements to sufficient depth and detail: you need to do this meticulously and obtain a written sign-off agreement on your system design from the client.
Legal perspective:
You should pin the scope of the project down, and get the client to sign an agreement of that scope. Once you have that agreement, anything not covered by it constitutes a new project.
Business perspective:
Do you want to continue doing business (with the current as well as future clients)? You need to do an evaluation of the impact adding the new required functionality will have on the current project: if the impact is small, then do it, but tell the client - in writing - that you are doing him a favor; if the impact is larger then you must negotiate with the client, outlining the issues, and either adapt your current agreement, or make a new one. What you do not want to do is to antagonize your client.
Lastly: "The client is always right." - (up to the point where you have to give up and just go away.)
这个问题不能一概而论。 这取决于项目。
例子：
客户有钱要烧，时间长，没有其他项目在进行，我非常灵活。
客户资金紧张，时间短，其他项目正在进行中，我一点也不灵活。
其他因素也会发挥作用，例如为项目选择的流程。 例如，您在敏捷流程中会更加灵活，而在瀑布方法中则不太灵活。
This question cannot be given a blanket answer. It depends project to project.
Examples:
Client has money to burn, long timeline, no other projects on the go, I am very flexible.
Client is tight with $$, short timeline, other projects on the go, I am hardly flexible at all.
Other factors come into play as well, such as the process that has been chosen for the project. For example, you will be more flexible in an agile process, less flexible in a waterfall approach.
我认为你的问题的答案取决于你的客户在时间和成本方面的灵活性，因为你无法在不影响这两件事的情况下改变项目的范围。
如果范围蔓延允许项目不断发展并对项目的结果产生总体积极影响，那么它可能是一件好事。 您确实需要一个正式的变更流程来管理范围变更。
I think the answer to your question comes down to how flexible your client is with time and cost because you can not change the scope of a project with out having an affect of these two things.
Scope creep can be a good thing if it allows the project to evolve and has an overall positive affect on the outcome of a project. You really need a formal change process in place to manage scope changes.
如果是固定投标项目，那么我愿意进行谈判，并同意扩大某个领域的范围，以换取其他地方的缩小，或者增加预算，或者换取其他一些考虑。
如果我是按小时计费的客户，那么他们可以扩展他们想要的范围，因为我将根据我在其上花费的时间向他们收费，无论它是否在项目的原始定义范围内。
If it's a fixed-bid project, then I am open to negotiation and will agree to expanding the scope in one area in exchange for reducing it somewhere else, or for an increase in budget, or in exchange for some other consideration.
If it's for a client that I'm billing hourly, then they can expand the scope all they want, since I'll be charging them for the time I spend on it regardless of whether it's within the original definition of the project or not.
提前定义系统将执行的功能列表。
如果客户添加新功能，则相应增加成本和时间。
如果客户决定将某个功能排除在范围之外，那么如果您尚未实现该功能，则可以减少成本和时间。
Define in advance a list of functions that the system will perform.
If the client adds a new function then increment the cost and time accordingly.
If the client decides to leave a function out of the scope then decrement the cost and time if you have not implemented it yet.