我尝试在敏捷SDLC中搜索Sprint 0的正确过程但不知怎的，我无法找到令人信服的答案，想到在这个论坛上提问。
我有点困惑它是否应该在项目生命周期内发生一次，或者它应该在每个版本中。即每个版本都应该（不是强制性地）从sprint 0开始，然后是我需要的多个sprint，最后是硬化，评论，演示，复古等等。
sprint 0中有一些活动在项目生命周期中需要一次，例如团队建设，定义DOD等，但有活动，例如计划，POC，技术故事等需要在每个版本中完成。
所以，我仍然相信，所有这些都取决于产品/发布积压，它定义了我们是否真的需要在每个版本中使用SPRINT。
答案 0 :(得分：-1)
Well, depends on how you would define Sprint 0. There are different ways teams think about it. This is how I would see it..
The basic premise behind a sprint is that you can get to a potentially shippable product increment (customer value) at the end of every sprint.
If you take that into account and then think about starting up a brand new project, then sprint 0 is where you can get a pass on not meeting that criteria - so, you can focus more on the "needed", but not really providing customer value aspects, like CI/CD, DoD, team building, code repos, etc. That is sprint 0.
You typically don't need to do sprint 0 kind of activities in the follow-on sprints, unless you find something in retrospective that you want to bring in as improvements to how you are building software, like you might want to do some improvements to CI/CD etc. But, try to balance the work in each sprint between "customer value" and "non customer value" stories. You want to more of the former.
Hope that helps.