什么时候一个功能被认为是“完成"的? [英] When is a feature considered "DONE"?

问题描述

作为软件开发人员，我们创建了许多……嗯……代码.我们生成的大部分代码都可以用于新功能或对现有功能的增强.在这种情况下，我们如何知道此功能何时完成?

As software developers we create lots of... well... code. Much of the code we produce can go towards a new feature or an enhancement to an existing feature. When this is the case, how do we know when this feature is done?

done 在功能上下文中是什么意思?例如，对于 A 公司来说，这可能意味着许多不同的事情，例如，

What does done mean in the context of a feature? For example, to Company A this may mean many different things like,

1. 满足客户要求(这本身就很棘手)
2. 没有已知的错误
3. 文档已编写
4. 等
5. 等

为了更好地帮助理解done对不同的开发者和团队意味着什么，请列出最多五个(但不超过 10 个)项目.此列表将是您作为开发人员或您的团队可能会经历的事情，一旦所有项目都被选中，该功能就被视为完成.

To better help understand what done means to different developers and teams please list up to five (but no more than 10) items. This list would be something you as a developer, or your team, might go through and once all items are checked off, the feature is considered done.

这些是一些很好的答案.我想弄清楚如何确定最好的，因为我猜这个问题有点主观.我想我还在寻找更完整的图片.

These are some great answers. I'm trying to figure out how to determine the best one as I guess this question is somewhat subjective. I guess I'm still looking for a more complete picture.

推荐答案

当客户/用户在测试之后签署 UAT(用户验收测试)时.这是我们的官方衡量标准.

When the client/user signs off on the UAT (User Acceptance Test) after testing it. That's our official measuring stick.

当然，这并不意味着什么，因为总会在几周后要求提供该功能的 2.0 版，但这对他们来说比我们的要多.

Of course that doesn't mean anything because invariably there's a version 2.0 of the feature requested a few weeks later, but that's more on their end than ours.

编辑 - 如果您想详细了解它，我们可以这样做:

edit - If you want to be really detailed about it, here's how we do it:

1. 要求由系统分析师和客户批准
2. 设计由首席程序员批准
3. 代码审查由同行程序员批准
4. 代码在 QA 部门的单元测试中被标记为已测试.
5. UAT 由客户亲自测试后签名.
6. 代码在系统测试中被 QA 部门标记为已测试.
7. 代码已发布.

这篇关于什么时候一个功能被认为是“完成"的?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！