blocks|key|505095|text|你构建客户想要的东西，而不是你收集需求时客户认为他们想要的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|505096|编辑：这是敏捷方法的一般属性，强调早期和经常交付--与瀑布(延迟交付和一次性交付)正好相反。|offset|length|style|BOLD|505097|entityMap^0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You build what the customer wants as opposed to what the customer thought they wanted when you gathered requirements.

EDIT: This is a general property of Agile methods with the emphasis on delivery early and often -- the exact opposite of waterfall (delivery late and once).

blocks|key|3604785|text|它为您提供了一个尽早并经常交付可用的业务功能的流程，这增加了客户对您的结果感到满意的可能性。它还以相对较低的成本做到了这一点，并降低了失败的风险。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3604786|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It gives you a process that delivers useable business function early and often, which increases the likelihood that the customer will be satisfied with your results. It also does so at a relatively low cost, and reduces the risk of failure.

blocks|key|514391|text|瀑布假设你事先知道所有的事情，这是不可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|514392|一个好的scrum流程的开始方式与瀑布一样，列出了您想要构建的所有内容。然而，scrum的优势在于，您可以在每次迭代后对列表进行重新排序，您始终可以构建客户想要的内容。|514393|当我们构建我们的一个产品的测试版时，我们允许测试版客户帮助推动下一个周期的堆栈排名。最终的结果是客户想要的产品，而不是我们口述给他们的产品。|514394|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Waterfall assumes you know everything in advance, which just isn't possible.

A good scrum process starts the same way waterfall does, listing out everything you want to build. The advantage of scrum, though, is that you re-rank that list after every iteration, you're always building exactly what the customers want.

When we were building a beta of one of our products we allowed the beta customers to help drive the stack rank for the next cycle. The end result was a product that the customers wanted, not one we dictated to them.

blocks|key|3604840|text|快速交付可用的软件部分，以便在项目脱轨之前发现自己是否在正确的轨道上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3604841|当然，这适用于任何敏捷过程，而不是瀑布，而不仅仅是Scrum。|3604842|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

That you deliver usable bits of software rapidly so that you find out whether or not you are on the right track before the project goes off the rails. 

Of course, this applies to any agile process as opposed to waterfall, not just Scrum.

blocks|key|3604750|text|可能有一些软件开发实现使用了瀑布框架中的大部分Scrum，因此您的部分问题可能是基于错误信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3604751|我在Scrum中看到的主要优势是它提供的日常沟通和责任，这样团队中的每个人都可以知道其他每个人都在做什么，并分享他或她在哪里。这提供的可见性，以及告诉你正在做什么的责任，可以使Scrum成为开发软件的一个非常好的部分，假设你正在与那些可以在某种程度上友好相处并乐于制定自己的规则的人一起工作。|3604752|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

There can be some implementations of software development that use most of Scrum within a waterfall framework so part of your question may be based on mis-information.

The main advantage I see in Scrum is the daily communication and accountability it provides so that everyone on the team can know what everyone else is doing plus share where he or she is. The visibility this gives to see what is going on along with the accountability of telling what you are doing is what can make Scrum a very nice part of developing software assuming you are working with people that can get along and are comfortable making their own rules to some extent.

blocks|key|2424373|text|快乐的开发者|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2424374|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|505161|text|我喜欢SCRUM的第一个原因是它的烧毁概念。没有人关心你花了多少时间，他们只需要知道你还剩下多少时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|505162|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The number one reason I like SCRUM is the burn-down concept. No one cares how much time you have spent, all they need to know is how much time you have left.

blocks|key|2418265|text|我发现这是一个很好的激励因素，整个团队都参与了计划过程，而不仅仅是几个人(这是以前的情况)。通常，根据我的经验，这也相当于更精确的估计，这对于保持项目的正确方向是必不可少的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2418266|此外，很好地了解团队当前的实际情况，在某种程度上了解每个人都在做什么，而不是让项目负责人单独分配任务。|2418267|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I find that it is a great motivator, that the team as a whole is involved in the planning process, and not just a couple of people (which was the case previously). Usally this also amounts to more precise estimates, in my experience, which is essential in keeping the project on the right course.

Also, it is great to have a good overview of, what is actually going on on the team currently, knowing what everyone is working on to some extent, instead of just having the project leader giving out assignments individually.

blocks|key|3605208|text|我认为真正的瀑布时代已经过去了。螺旋接管了瀑布，许多团队甚至在不知情的情况下也在螺旋地运作。在我之前的一个标签中，我提到了敏捷是从螺旋进化而来的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3605209|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think true waterfall days are gone. Spiral took over waterfall and lot of teams operate in spiral even without knowing it. In one of my previous tags I mentioned that Agile is evolved from spiral.

blocks|key|5719736|text|首先，如果我们一致认为正确的问题更像是“敏捷”与“瀑布”……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719737|作为一名前开发经理，我对此的主要观点实际上有所不同。我喜欢敏捷方法的“工程实践”好处，如burndows、JIT设计等。然而，研究表明，流程选择和成功率之间的相关性比许多人可能预期的要小(one+example)。当然，敏捷在某种程度上被证明是更好的，但目前还不清楚研究是否调整了这样一个事实，即你倾向于在敏捷项目中拥有更好的开发人员-要么是因为更好的开发人员倾向于推动敏捷，要么是因为敏捷往往吸引更好的开发人员。|offset|length|5719738|如果你看一下Cockburn的一些东西，就会很清楚地看到，软件项目的主要成功驱动因素是项目上的人员的质量，而不是过程。|5719739|​|5719740|📷|atomic|5719741|有关这一点的一些非常好的基本解释，请参阅Cockburn's+book+(它不是一本如何操作的书，而是一些解释基本概念和为什么你应该做敏捷的书)。|5719742|在我看来，敏捷方法帮助创建了一个优秀的程序员想要使用的环境。因为他们是这个过程的一部分，因为他们被允许使用他们的大脑，等等。|style|BOLD|5719743|因此，作为一家企业，你更有可能吸引和留住顶尖的人，这意味着你是，更有可能拥有一个成功的项目。|5719744|在业务层面上，这才是真正的理由-其他一切都很好，但这是对底线很重要的一件事，也是你可以在链上销售的一件事。众所周知，真正优秀的开发人员比普通开发人员的工作效率高出许多倍，但他们的成本并不会高出许多倍。因此，如果你能吸引和留住真正优秀的开发人员，你就可以用同样的钱获得更多的产出。哦，在这个过程中你会有更多的乐趣。|5719745|更好的环境和更好的开发人员=>更成功的项目|5719746|一句警告；如果你碰巧有一个普通的开发人员团队，没有明显的闪光点，我会担心实现敏捷。至少，不要指望它能解决你的问题--你可能会得到同样的结果(在卧床期之后)，尽管有烧毁的好处。但敏捷依赖于拥有真正优秀的开发人员，他们真正知道自己在做什么，并不断更新自己的技能-或者至少是一个包括一些这样的人的团队。敏捷是由一群传奇的程序员和非常非常聪明的人发明的。|5719747|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ambysoft.com/surveys/success2007.html|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6fb054fdaef03309a34f1560fad87815.jpeg|imageAlt|2|https://rads.stackoverflow.com/amzn/click/com/0321482751^0|0|2M|B|0|0|0|0|0|1|1|0|K|F|2|0|B|F|0|V|E|0|0|0|0|4|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|F|3|G|5|6|7|1L|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1M|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1N|8|@]|9|@$D|1O|E|1P|1|1Q]]|A|$]]|$1|M|3|N|5|6|7|1R|8|@]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|O|3|P|5|6|7|1V|8|@$D|1W|E|1X|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Y|8|@$D|1Z|E|20|Q|R]]|9|@]|A|$]]|$1|U|3|V|5|6|7|21|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|22|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|23|8|@$D|24|E|25|Q|R]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|19|14|1A|A|$1B|1C|1D|-4]]|1E|$5|13|14|15|A|$16|1F]]]]

Firstly, if we just agree that the right question is more like "agile" vs "waterfall"... 

As a former development manager, my primary view of this is actually somewhat different. I love the "engineering practices" benefits of agile methods, such as burndows, JIT design etc. 
However, studies show that the correlation between process choice and success rate is less than many might expect (<a href="http://www.ambysoft.com/surveys/success2007.html" rel="nofollow noreferrer">one example</a>). Sure, Agile is fairly consistently shown to be somewhat better, but it is not clear if the studies adjust for the fact that you tend to have better developers on agile projects - either because better developers tend to push for Agile or because Agile tends to attract better developers. 
If you look at some of Cockburn's stuff, it is quite clear that the main success driver for software projects is the quality of the people on the project - not the process. 

<a href="https://i.stack.imgur.com/fUMBZ.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/fUMBZ.jpg" alt="Agile Software Development"></a>
 
See <a href="https://rads.stackoverflow.com/amzn/click/com/0321482751" rel="nofollow noreferrer" rel="nofollow noreferrer">Cockburn's book</a> for some really good fundamental explanations of this (it is not a how-to book, rather something that explains the underlying concepts and why you should do agile).

In my opinion, Agile methods help create an environment in which excellent programmers want to work. Because they are part of the process, because they are allowed to use their brains, etc. 
As a business you are therefore more likely to attract and retain top-notch people which means you are more likely to have a successful project. 

At a business level, that is really the justification - everything else is all very well and good, but this is the one thing that matters to the bottom line and the one thing you can sell up the chain. It is well known that really good developers are many times more productive than average developers, but they don't cost many times more. So, if you can attract and retain really good developers you get more output for the same money. Oh, and you'll have a lot more fun in the process. 

Better environment => Better Developers => More successful projects

One word of caution; If you happen to have a team of average developers with no obvious bright sparks, I would be concerned about implementing Agile. At least, don't expect it to solve your problems - you are likely to get the same kind of results (after the bedding-in period), though with the benefits of the burndown. But Agile depends on having really good developers who really know what they are doing and who are constantly updating their skills - or at least a team that includes some people like that. Agile was invented by a bunch of guys who are legendary programmers and very, very smart people.

blocks|key|2418240|text|没有死亡行军。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2418241|定义您可以在每次冲刺中交付的内容。|2418242|如果你不能做到这一点，这会通过将特性(遗憾的故事)推出后续的sprint来立即反映出来。|2418243|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

No Death Marches.

Define what you can deliver every sprint. 
If you don't make it that is immediately reflected by pushing features (sorry stories) out of subsequent sprints.

blocks|key|5719494|text|用户(产品负责人)参与决定下一步需要什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719495|因此，您可以立即从用户处购买。|5719496|当一个故事与他们的预期不符时，立即提供反馈。|5719497|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

User (Product Owner) is involved with deciding what is needed next.

So you have immediate buy in from the users. 
And immediate feedback when a story does not match what they expected.

blocks|key|2418306|text|我经常看到这种混淆，所以让我们具体一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2418307|2418308|Scrum是一种项目管理方法，|ordered-list-item|offset|length|2418309|‘瀑布’是|2418310|的软件开发方法|2418311|这两者是不等价的。|2418312|之所以会产生混淆，是因为Scrum通常被作为敏捷开发过程的项目管理部分来实践，但Scrum和敏捷并不是一回事|2418313|因此，从技术上讲，你的问题是一个糟糕的假设！也许你想换个说法？|2418314|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Scrum_%2528development%2529^0|0|0|0|5|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|H|3|I|5|E|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|18|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|19|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

i see this confusion a lot, so let's be specific:

<ol>
<li><a href="http://en.wikipedia.org/wiki/Scrum_%28development%29" rel="nofollow noreferrer">Scrum</a> is a project-management method,</li>
<li>'waterfall' is a software-development methodology</li>
</ol>

The two are not equivalent.

the confusion arises because Scrum is often practiced as the project-management part of an Agile development process, but Scrum and Agile are not the same thing

so to be technically accurate, your question makes a bad assumption! Perhaps you'd like to rephrase it?

blocks|key|514382|text|瀑布是使用常见的工程方法解决软件开发的第一次尝试。换句话说，这对每个人来说都是可怕的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|514383|SCRUM的主要优势是什么？它实际上是计划用于软件开发的。|514384|主要是带有新信息的代码“增长”，只有在有人说你拥有的信息足够后才会被“组装”(这是永远不会的)。|514385|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Waterfall is the first attempt to tackle software development using the common engineering aproach. In other words, It's HORRIBLE for everybody. 

Main advantage of SCRUM? It was actually planned to be used for software development.

Mainly the code "growth" with new information, is not "assembled" only after somebody says the information you have is enough (which never is).

blocks|key|2424490|text|SCRUM+(以及遵循敏捷宣言的所有敏捷方法)承认软件开发人员也是人。瀑布从业者更有可能相信软件是由可互换的人工月机器人开发的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2424491|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

SCRUM (and all agile methodologies that follow the agile manifesto) acknowledge that software developers are human. Waterfall practitioners are more likely to believe that software is developed by interchangeable man-month robots.

blocks|key|5719629|text|它促进了紧急设计/紧急架构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719630|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It facilitates emergent design / emergent architecture.

blocks|key|5719635|text|能够在不显著影响进度、成本或性能的情况下更改方向或处理路线修正。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719636|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The ability to change directions or process course corrections without impacting the schedule, cost, or performance dramatically.

blocks|key|5719654|text|您将看到的最大好处之一是您拥有迭代周期。客户会改变他们的想法、预算等。灵活一点是有帮助的，而不是得到这样的反应：“这不是我所要求的，所以我不会为此买单。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719655|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One of the biggest benefits you'll see is that you have iterative cycles. The customer is going to change their mind, budget, etc. It helps to be flexible, instead of getting the reaction, "that isn't what I asked for, so I'm not paying for it"

blocks|key|3605243|text|‘'Late’。在敏捷方法中，推迟决策。当您实际拥有相关知识时，可以在项目周期的后期进行调用，而不是在早期没有相关知识的情况下进行调用。这将提高您的决策质量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3605244|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

'Late binding'.
In agile methodologies, defer decisions. You make calls later in the project cycle when you actually have relevant knowledge, as opposed to earlier when you do not. That improves the quality of your decisions.

blocks|key|5719819|text|其他人说Scrum给了我们“快乐的开发人员”和“有动力的开发人员”。对我来说，这是最引人注目的观察结果。我不同意Scrum仅仅是放大了(精英/糟糕)程序员的表现的观点:根据我的经验，它一直在提高开发人员的表现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719820|为什么，好吧：|5719821|5719822|感觉自己是团队中的一员，这让人充满活力。他们会支持你的。你有他们的，|unordered-list-item|5719823|，|5719824|，你能感觉到你的作品有意义。|5719825|你致力于实现触手可及的目标，你感觉自己掌控了一切，你不会被困很久，你不会感到孤单|5719826|你看到了劳动的果实，你会感到自豪，|5719827|5719828|请注意，这些不是“技术性”的，而是非常“情绪化”的。我认为这就是“快乐”。在经历了这一切之后，提高幸福感的唯一途径就是努力成为一名更好的程序员……我看到了一次又一次的发生。|5719829|总结一下：|5719830|Scrum让开发人员达到更高的境界，执行得更好，享受到内在的乐趣。|offset|length|style|BOLD|5719831|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|6|R|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|19|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1D|8|@$W|1E|X|1F|Y|Z]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|11|$]]

Others said that Scrum gives us "Happy developers", and "Motivated developers". To me that is the most striking observation. I disagree with the opinion that Scrum merely amplifies the (elite/bad) programmers' performances: In my experience it consistently improves developer performance. 

Why, well:

<ul>
<li>It's energizing to feel part of a team. They've got your back. You've got theirs.</li>
<li>You can feel your work has a sense of meaning. POs will make sure.</li>
<li>You committed to goals within reach, you feel in control</li>
<li>You won't get stuck very long, you do not feel alone</li>
<li>You see the fruits of your labour, you can feel proud, immediately</li>
</ul>

Notice that these are not 'technical' but very 'emotional'. I think this is "happy". After all this, the only route toward increasing your happiness even more is to try and become a better programmer... which I see happening again and again. 

To summarize:

Scrum makes developers reach higher, perform better, with intrinsic enjoyment.

blocks|key|2424625|text|我喜欢敏捷的一个原因是，它可以让你更快、更快、更便宜地发现失败()(意思是，如果项目要失败，你会更快地发现它)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2424626|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One reason I like Agile is that it allows you to fail faster, sooner, cheaper (meaning, if the project is going to blow up, you'll find out about it a lot faster).

blocks|key|3605435|text|瀑布上最大的Scrum例子是什么？几乎每天都能看到项目的状态/进度，或者缺少这些信息。大多数瀑布项目都被愉快地陈述为在非常接近检查点/相位门之前都在轨道上……然后，他们被发现迟到了一些未知的数量。使用Scrum，您总是知道自己所处的位置，并且可以及早了解问题，以便可以实际采取行动。最棒的是，Scrum项目状态跟踪比瀑布项目状态跟踪容易得多，而且本质上更准确，因为度量单位是剩余功能而不是工作时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3605436|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The biggest example of Scrum over waterfall? Near-daily visibility into project status/progress, or the lack thereof. Most waterfall projects are cheerfully stated to be on track until very close to a checkpoint/phase gate... and then they're discovered to be late by some unknown amount. With Scrum you always know where you stand, and you get visibility into problems early enough so that you can actually do something about it. Best of all, Scrum project status tracking is much easier than waterfall project status tracking, and inherently more accurate since the unit of measure is remaining functionality instead of hours worked.

blocks|key|5719905|text|团队在没有与瀑布中的变更控制过程相关的所有创伤的情况下拥抱变更。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719906|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

That the team embraces change without all the trauma associated with change control processes in Waterfall.

blocks|key|5719934|text|与瀑布方法相比，敏捷方法有一个明显的优势。对我来说，敏捷和瀑布方法是两种不同的软件开发方法。在敏捷方法中，整个模块被分成小的子模块，并以快速和模块化的方式进行开发，而不是像瀑布模型那样整个大模块。在敏捷方法中，对设计和需求的更改可以很容易地适应瀑布情况下的困难。与瀑布模型不同的是，敏捷的上市时间也非常快。敏捷方法缩短了测试周期。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5719935|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There is a clear advantage of Agile approach over Waterfall methodology. to me Agile and Waterfall approach are the two different methodologies of software development.
In agile method, the entire module is divided into small sub module and the developemnt is done in a quick and modular manner rather than the entire big module as in case of Waterfall model.
In Agile method, Changes to the design and the requirement can be accomodated easily where as its difficult in case of Waterfall.
The time to market is also very quick in Agile unlike of Waterfall model.
Agile methodology reduces the testing cycle.

If you had to choose one advantage that Scrum gives over a waterfall process, what would it be?

One advantage an agile approach using Scrum has over waterfall approaches

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如果让您选择Scrum相对于瀑布流程的一个优势，您会选择哪一个优势？

问与瀑布方法相比，使用Scrum的敏捷方法有一个优势
EN

回答 24

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与瀑布方法相比，使用Scrum的敏捷方法有一个优势EN

回答 24

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与瀑布方法相比，使用Scrum的敏捷方法有一个优势
EN