本文对比了瀑布式开发与Scrum敏捷开发方法。瀑布模型通过长时间规划，然后逐步开发、测试和部署，可能导致产品滞后市场。而Scrum通过短期迭代，即Sprint，实现快速响应变化，降低规划至开发的延迟。Scrum包含产品负责人、Scrum主管和团队三个角色，以及产品待办事项列表、用户故事和燃尽图等关键元素。
Introduction to Scrum [Scrum vs Waterfall]
Waterfall
Planà Buid àTestà Review àDeploy
瀑布式开发通常会花几个月时间来规划产品
Waterfall typically goes through a lengthy planning process, which could take several months，
然后再发几个月时间研发产品
fallowed by building the product which again could take many months.
接着进行产品测试，评审，最终发布产品.
and then testing the product, reviewing, and eventually deploying the product.
重点是，如果市场需求或技术环境发生变化，你此时研发出的产品很可能无法满足市场需求
At this point, you may end up bringing the wrong product market if market demand or technology has changed since the original plan was developed.
瀑布式开发在遇到这种变化会出现很多问题。
There are several problems with this method.
首先，产品规划师必须早余后续工作之前完成,
First of all, the planning must be completed before any work begins,
绝大部分案例中，规划环节结束时并没有完全理解项目，但研发工作已经完成了。
and in most cases, the planning has done without entirely understanding the project, once development is being done.
通常情况下，整个项目必须送回规划阶段，然后从头再来，【没理解需求，返回plan】
否则，研发人员就会因为不明白产品规划而受到批评. 【测试不过打回给研发】
Oftentimes things get sent back to the planning phase, and the project either needs starts over, or the developers are just criticized for not understand the plan.
这种情况会反复出现，比如研发完成了，进行产品测试，发现问题就得重新开发,
【测试不过打回给研发】
This cycle can happen many times when development is done building the product, it gets thrown over the fence to test,
有时甚至要重新规划产品
where, when problems are encountered, it bounces back to development and sometimes back to planning.
再接下来的及格步骤中，也会出现同样的问题，
The same issues occur in the next few steps with lots of back st
最低0.47元/天 解锁文章
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
