I've run short projects of around 5-6 weeks using 1 week sprints - I found it useful to have each sprint run from Wednesday->Tuesday - the team was fresher for the final two days of the sprint, and carried through the rest of the week by new stories!
One thing we struggled with in 1 week sprints was getting stories tested - we would sometimes start a new iteration with some stories not formally tested. Here we had to "tweak" the process a little to perform tests over 2 week cycles.
In short, it's doable, and you can still reap the benefits of iterative development. You just might find yourself making a few compromises in the process.
We do Scrum for short projects all the time, I find it it is much more productive for short term stuff than the waterfall approach or similar phasing.
Just one word of warning: start bugfixing from day 2, keep testing intensely. Our first Scrum tries led into truckloads of bugs to fix (for free) after the delivery of the product.
Nowadays we maintain a stringent "not done until free of bugs" policy, per story, which works wonders, without hurting productivity! If it's broken it's not in the release.
I think the point of scrum is that it delivers business value throughout rather than just at the end, I guess you have to decide whether your project can do that and whether it needs to do that.
Depends on your velocity. Usually a sprint is around 2 weeks. Using a formal process for just 3 sprints seems a bit overkill to me. I would still recommend using it, but not be so rigid about sticking to the process too much.
发布评论
评论（4）
我使用 1 周的冲刺运行了大约 5-6 周的短期项目 - 我发现从周三到周二运行每个冲刺很有用 - 团队在冲刺的最后两天更加新鲜，并完成了本周剩下的时间有新故事！
我们在 1 周的冲刺中遇到的一件事是测试故事 - 有时我们会用一些未经正式测试的故事开始新的迭代。在这里，我们必须稍微“调整”流程，以在两周的周期内执行测试。
简而言之，这是可行的，并且您仍然可以获得迭代开发的好处。您可能会发现自己在此过程中做出了一些妥协。
I've run short projects of around 5-6 weeks using 1 week sprints - I found it useful to have each sprint run from Wednesday->Tuesday - the team was fresher for the final two days of the sprint, and carried through the rest of the week by new stories!
One thing we struggled with in 1 week sprints was getting stories tested - we would sometimes start a new iteration with some stories not formally tested. Here we had to "tweak" the process a little to perform tests over 2 week cycles.
In short, it's doable, and you can still reap the benefits of iterative development. You just might find yourself making a few compromises in the process.
我们一直为短期项目使用 Scrum，我发现它对于短期项目比瀑布方法或类似的分阶段更有成效。
只是警告一句：从第 2 天开始修复错误，继续严格测试。我们的第一次 Scrum 尝试导致了在产品交付后（免费）修复大量错误。
如今，我们对每个故事都实行严格的“只有没有错误才完成”的政策，这在不影响生产力的情况下创造了奇迹！如果它被破坏了，它就不会出现在发行版中。
享受 Scrumming 的乐趣！
We do Scrum for short projects all the time, I find it it is much more productive for short term stuff than the waterfall approach or similar phasing.
Just one word of warning: start bugfixing from day 2, keep testing intensely. Our first Scrum tries led into truckloads of bugs to fix (for free) after the delivery of the product.
Nowadays we maintain a stringent "not done until free of bugs" policy, per story, which works wonders, without hurting productivity! If it's broken it's not in the release.
Have fun at Scrumming!
我认为 Scrum 的重点在于它在整个过程中提供商业价值，而不仅仅是在最后，我想你必须决定你的项目是否可以做到这一点以及是否需要这样做。
另请阅读这篇关于 Scrum 如何工作的非常简单的解释，您将能够在阅读时思考它将如何影响您的项目。 http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf
I think the point of scrum is that it delivers business value throughout rather than just at the end, I guess you have to decide whether your project can do that and whether it needs to do that.
Also read this, very simple explanation of how scrum works, you will be able to think about how it will affect your project while reading. http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf
取决于你的速度。通常一个 Sprint 大约需要 2 周。对我来说，仅使用 3 个冲刺的正式流程似乎有些过分了。我仍然建议使用它，但不要过于严格地坚持这个过程。
Depends on your velocity. Usually a sprint is around 2 weeks. Using a formal process for just 3 sprints seems a bit overkill to me. I would still recommend using it, but not be so rigid about sticking to the process too much.