在Scrum过程中的哪个地方讨论了编程体系结构？ [英] Where in the scrum process is programming architecture discussed?

问题描述

假设我有远见，现在我的产品积压项目。该部分是书面形式，随时可以使用。我即将创建我的冲刺。我好奇。编程团队什么时候坐下来说让我们使用这个平台，这个框架和语言以及诸如我们在这里需要一个类或我看到一种可以在其中使用接口的方法之类的东西。这种谈话什么时候进行？

Let's say I have my vision and now my product backlog of items. That part is in writing and ready to be used. I am about to create my sprint(s). I am curious. When does a programming team sit down and say "let's use this platform, this framework, and language" and things like "We need a class here," or "I see a way we can use an Interface with that" and so on. When is that kind of talk going on?

在sprint之前是否有会议，有人会决定所有团队-我们将使用Linux，MySQL，PHP和CodeIgniter，然后其中一个团队有一个冲刺来实现该基础架构，而其他团队则等待完成以启动其他冲刺（团队A2建立了ui或安全性模型，以及产品积压中的功能）？

Are there meetings that come before the sprint where someone decides for all teams - "We are going to use Linux, MySQL, PHP and CodeIgniter" and then one of the teams has a sprint to implement that infrastructure, while other teams wait for completion to start the other sprints (team A2 build a ui or security model and the features of it from the product backlog)?

当冲刺第一次开始时，这也是团队级别的工具吗？

Is this also where tools like trac would be used at the team level, when the sprints first begin?

抱歉如果我到处都是这个。我只是从未见过它完成，只是当我认为自己理解时，我想到了一个新问题。

Sorry if I'm all over the place with this. I've just never seen it done and just when I think I understand it I think of a new question.

这也很重要，但是您如何命名球队？鲍勃的团队，史密斯的团队，还有更丰富多彩的东西吗？

Also it's beside the point but what do you name your teams? Bob's team, Smith's team, something more colorful?

谢谢。

推荐答案

简短的回答是取决于，因为在第一部分中可能会有其他团队在某种程度上规定这些术语。例如，在我当前的项目中，有些事情几乎是既定的，例如IDE = Visual Studio，错误跟踪= HP质量中心，版本控制= Subversion，面向开发人员XP Professional的操作系统等。

Short answer is "It depends" as for the first part there could be other teams that dictate those kinds of terms to some extent. For example, on my current project some things are almost a given,e.g. IDE=Visual Studio, Bug tracking=HP Quality Center, Version Control=Subversion, O/S for developers XP Professional,etc.

可以有一个Sprint 0，其中一些基础结构元素的处理方式类似于CI服务器，团队的Wiki，确保每个人都在SVN中拥有帐户以及要处理的其他管理事项。

There can be a Sprint 0 where some infrastructural elements are handled like a CI server, wiki for the team, making sure everyone has accounts in SVN, and other administrative things to get handled.

团队名称（如代码名称）可以随时出现，尽管它们可能具有不同的含义，因为某人可以在一个地方使用的团队名称可能在其他地方不太好，例如对于完全不熟悉该术语的人，Voltron团队可能做得不好。

Team names like code names can come up at anytime though they can have different meanings as what someone can use for a team name in one place may not be so good somewhere else,e.g. Team Voltron may not go over well for those completely unfamiliar with the term.

这篇关于在Scrum过程中的哪个地方讨论了编程体系结构？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！