迭代的最佳名称集?

时间:2023-01-16 17:02:05

I was curious what do you use as iteration names and how much iterations do you have? What is the best set of names for iterations which will also be simple enough to explain to the customer.

我很好奇你用什么作为迭代名称和你有多少次迭代?什么是迭代的最佳名称集合,也很简单,可以向客户解释。

EDIT: lets say that my iterations are 5 weeks long each.

编辑:让我说我的迭代每个5周。

4 个解决方案

#1


We keep technical version names, similar to earlier described, using the iteration number as the main digit.

我们保留技术版本名称,类似于之前描述的,使用迭代编号作为主要数字。

For customers, we apply project-specific release names, part of a consecutive set. For a recent gig we named the releases after the consecutive runners up of the (Dutch version of) the TV talent show America's Next Top Model. The first iteration released "Kathelijn" (ended in 10th place), next we released "Stefanie" (ended 9th).

对于客户,我们应用项目特定的版本名称,这是连续集的一部分。对于最近的一场演出,我们在电视选秀节目“美国的下一个*模特”(荷兰版)的连续亚军之后命名。第一次迭代发布了“Kathelijn”(以第10名结束),接下来我们发布了“Stefanie”(结束于第9位)。

We like to be creative at this, we maintain the natural order in the naming. You have to name all future iterations from day 1 to do this.

我们希望在这方面具有创造性,我们保持命名的自然顺序。您必须从第1天开始命名所有未来的迭代才能执行此操作。

Another option is to name the release after the most prominent feature it brings. E.g "One-click to order" and the "Basic reporting".

另一个选择是在它带来的最突出的功能之后命名该版本。例如“一键订购”和“基本报告”。

Naming is important, a catchy name is worth a lot, even for an iteration.

命名很重要,一个吸引人的名字值得很多,即使是迭代也是如此。

PS. Google Sets can help you think of the next...

PS。 Google Sets可以帮助您思考下一个......

#2


We have a release name that matches the typical release 5.1.0.0 numbering scheme.

我们的发行版名称与典型的5.1.0.0版本编号方案相匹配。

We have more fun with the iteration names choosing a fun theme. Comicbook characters, muscle cars, war plans, etc. Depends on your group.

选择一个有趣的主题的迭代名称我们有更多的乐趣。漫画人物,肌肉车,战争计划等取决于你的团队。

#3


It depends. If you use agile development and you want to name the in between iterations, use the date in the name like:

这取决于。如果您使用敏捷开发并且想要在迭代之间命名,请使用名称中的日期,如:

Projectname Releasedate

For normal public releases the good old numbers still work:

对于正常的公开发布,好的旧数字仍然有效:

Major release . Minor release . [Bugfix release].

#4


In a project for a customer (a website using GAE) I'm using a very simple scheme:

在一个客户项目(使用GAE的网站)中,我使用了一个非常简单的方案:

  • iteration1 as first week
  • iteration1作为第一周

  • iteration2 as second week
  • iteration2作为第二周

  • and so on
  • 等等

the customer likes this naming since it is simple and he can evaluates the progress I made.

客户喜欢这个命名,因为它很简单,他可以评估我所取得的进展。

EDIT

you can alias week as period, so each 5 weeks you got a new iteration label

你可以将周作为句点别名,所以每5周就有一个新的迭代标签

#1


We keep technical version names, similar to earlier described, using the iteration number as the main digit.

我们保留技术版本名称,类似于之前描述的,使用迭代编号作为主要数字。

For customers, we apply project-specific release names, part of a consecutive set. For a recent gig we named the releases after the consecutive runners up of the (Dutch version of) the TV talent show America's Next Top Model. The first iteration released "Kathelijn" (ended in 10th place), next we released "Stefanie" (ended 9th).

对于客户,我们应用项目特定的版本名称,这是连续集的一部分。对于最近的一场演出,我们在电视选秀节目“美国的下一个*模特”(荷兰版)的连续亚军之后命名。第一次迭代发布了“Kathelijn”(以第10名结束),接下来我们发布了“Stefanie”(结束于第9位)。

We like to be creative at this, we maintain the natural order in the naming. You have to name all future iterations from day 1 to do this.

我们希望在这方面具有创造性,我们保持命名的自然顺序。您必须从第1天开始命名所有未来的迭代才能执行此操作。

Another option is to name the release after the most prominent feature it brings. E.g "One-click to order" and the "Basic reporting".

另一个选择是在它带来的最突出的功能之后命名该版本。例如“一键订购”和“基本报告”。

Naming is important, a catchy name is worth a lot, even for an iteration.

命名很重要,一个吸引人的名字值得很多,即使是迭代也是如此。

PS. Google Sets can help you think of the next...

PS。 Google Sets可以帮助您思考下一个......

#2


We have a release name that matches the typical release 5.1.0.0 numbering scheme.

我们的发行版名称与典型的5.1.0.0版本编号方案相匹配。

We have more fun with the iteration names choosing a fun theme. Comicbook characters, muscle cars, war plans, etc. Depends on your group.

选择一个有趣的主题的迭代名称我们有更多的乐趣。漫画人物,肌肉车,战争计划等取决于你的团队。

#3


It depends. If you use agile development and you want to name the in between iterations, use the date in the name like:

这取决于。如果您使用敏捷开发并且想要在迭代之间命名,请使用名称中的日期,如:

Projectname Releasedate

For normal public releases the good old numbers still work:

对于正常的公开发布,好的旧数字仍然有效:

Major release . Minor release . [Bugfix release].

#4


In a project for a customer (a website using GAE) I'm using a very simple scheme:

在一个客户项目(使用GAE的网站)中,我使用了一个非常简单的方案:

  • iteration1 as first week
  • iteration1作为第一周

  • iteration2 as second week
  • iteration2作为第二周

  • and so on
  • 等等

the customer likes this naming since it is simple and he can evaluates the progress I made.

客户喜欢这个命名,因为它很简单,他可以评估我所取得的进展。

EDIT

you can alias week as period, so each 5 weeks you got a new iteration label

你可以将周作为句点别名,所以每5周就有一个新的迭代标签