敏捷开发有什么缺点和不足？
— 0 —
Agile might be everywhere these days, but for as much praise as the methodology gets, what are the disadvantages of Agile? As it turns out, Agile isn’t for everyone, for every situation. So before you embark on a big Agile revolution, be sure to keep in mind these disadvantages of Agile.
最近敏捷可以说是无处不在，这套方法得到了很多赞誉，但是敏捷有什么缺点和不足吗？事实证明，敏捷并不是适合所有人所有情况的“万能药”。所以当你信心满满地踏上开启敏捷变革之旅时，请确保你的确知道敏捷的缺点和不足的。
Before we discuss the disadvantages of Agile, let’s review what this methodology is all about. Originally developed for software delivery, Agile emphasizes delivering products in small increments, which allows teams to bring new products (or at least parts of them) to market faster, incorporate customer feedback along the way and easily experiment with new features.
在讨论敏捷的缺点之前，让我们简单回顾一下敏捷方法。最开始敏捷是用于软件开发的，它让新产品（起码一些部分）能够更快地投放市场，让客户在过程中参与并反馈，这让新的功能可以更容易得获得验证。
— 1 —
Despite the benefits that Agile can offer, it’s not for everyone and for every circumstance. As a result, it’s important to be aware of the disadvantages of Agile methodology. With that in mind, you can be mentally ready and make some tailered improvements in order to avoid or mitigate the negative impacts.
尽管敏捷带来了很多改善，但是再次重申它并不是适合所有人和所有情况的。因此，了解敏捷的不足显得特别重要。知道这点后，你心理上是准备好的并且会根据具体情况来做裁剪和优化来规避或减少负面影响。
— 2 —
Poor resource planning
Because Agile is based on the idea that teams won’t know what their end result (or even a few cycles of delivery down the line) will look like from day one (but to explore during the dev process), it’s challenging to predict efforts like cost, time and resources required at the beginning of a project (and this challenge becomes more pronounced as projects get bigger and more complex).
很难进行准确的资源规划
由于敏捷团队不是一开始就知道产品“最终的样子”，而是在过程中探索用户的需求逐渐知道产品真正的终局状态，这样一来就给前期的规划（成本，时间，资源）带来了很大的挑战（项目越大越复杂这一点变动更加明细）。
Limited documentation
In Agile, working sofware is over thorough documentations. Those documentations are throughout a project, and often “just in time” for building the output, not at the beginning. As a result, it becomes less detailed and often falls to the back burner (and this disadvantage becomes more pronounced when we need to do the handover or bug fixing).
很难准确的定义“轻量的“或必要的文档
敏捷倡导的是用工作的软件即文档（核心是代码即文档）。整个项目用于产品开发的文档不是一开始准备好的（甚至都没有RP原型设计），而是在过程中”及时的“ just-in-time准备出来的。因此，我们看到的是非常简单的且常常被放在最后处理的文档（在项目中涉及到移交或问题分析时这一点显得尤其突出）
Fragmented output
Incremental delivery may help bring products to market faster, but it’s also a big disadvantage of Agile methodology. That’s because when teams work on each component in different cycles, the complete output often becomes very fragmented rather than one c unit. (and this challenge becomes more pronounced as projects have higer requirements for UI and UX).
很难把握整体产品的一致性
增量交付可能有助于更快地将产品推向市场，但这也是敏捷方法论的一大缺点。因为当团队在不同的周期内对各个组件进行开发时，整体的输出往往会变得非常零散，而不是一个内部紧密集合的整体。（当项目对UI和UX有更高的要求时，这个挑战就变得更加明显）。
No finite end
The fact that Agile requires minimal planning at the beginning makes it easy to get sidetracked delivering new, unexpected functionality. Additionally, it means that projects have no finite end, as there is never a clear vision of what the “final product” looks like.
很难预测有限的终点
敏捷在一开始要求最低限度的规划，这使得交付新的、意想不到的功能时很容易偏离方向。此外，这意味着项目没有限定的终点，因为从来没有一个明确的 "最终的产品"样子。
Difficult measurement
Since Agile delivers in increments, tracking progress requires you to look across cycles. And the “see-as-you-go” nature means you can’t set many KPIs at the start of the project. That long game makes measuring progress difficult.
很难有效地进行度量
由于敏捷是以增量的方式交付的，所以跟踪进度需要你跨周期地看。而 "边走边看 "的特性意味着你不能在项目开始时设置很多KPI。这种长期的游戏使得衡量进度变得相对困难。
— 3 —
The disadvantages of Agile methodology make clear that it’s not for everyone. So what can you do?
Mitigating the disadvantages of Agile methodology requires taking more of a Lean approach by emphasizing the importance of:
Delivering value through a quality end product rather than simply delivering a working product
Managing a clear process for delivering that product, not an uncertain route determined along the way
Awared of and Armed with knowledge about the disadvantages of Agile methodology, it’s time to take a look at how Agile might affect your projects. And if you find the disadvantages of Agile outweigh the benefits, remember that there are alternative methodologies (scrum,Kanban, xp, SAFe,Less, DAD, waterfull, Lean...) for delivering better products efficiently.
Going back to what we mentioned at the beginning, we cannot be blind to any one methodology. Thus, Practice is the sole criterion of truth. We have to find out the talered and the best methodology via constant practices.
敏捷方法论的弊端表明，它并不适合所有人。那么你能做什么呢？
减轻敏捷方法论缺点带来的影响，需要更多地采取精益方法，强调以下几点的重要性：
通过交付有质量保证的产品来创造（客户/用户）价值，而不是简单地交付可用的产品。
管理一个清晰的产品交付流程，而不是在项目过程中确认一条不确定的路线。（业务路径图、产品路径图的重要性）
有了关于敏捷方法论缺点和不足的认知和基本知识后，是时候看看敏捷会如何影响到你的项目了。如果你发现它的缺点或产生的问题已经大于优点和带来的好处，请记住，还有其他方法可以有效地交付更好的产品 (scrum,Kanban, xp, SAFe, DAD,Lean...)。
回到我们最初提到的，任何优秀的的思想或理论都不能迷信。实践是检验真理的唯一标准！我们需要在不断的实践中找到最适合我们的方法。
— 4 —
活动邀请
那敏捷到底是适不适合你？到底能不能应用到你的工作中？
欢迎来参加“敏捷新常态” 学习分享会！
我们在最美阶梯教室等着你~
（还有敏捷英语沙龙哦）
亲，报名请注意🙋：
活动：“敏捷新常态” 学习与分享会
时间：8月16日周日上午 10:00-12:30 （9:30签到）
地点：苏州昆山登云路和院士路交叉口
名额：由于场地限制，仅8名小伙伴名额 （其余同学尽请期待~8月底第二期）
费用：培训免费，场地租用众筹费，需要大家分摊99元/人
偷偷剧透一下彩蛋~🤫
「敏捷实践讨论篇- SAFe在汽车行业的有效应用」
你想知道这页PPT背后的敏捷故事吗？
来吧！8月16日周日， 我们不见不散~
：）
......
◇◆◇
往期回顾
你值得拥有的“战略武器” | Impact Map !!!
————————————————
Santiago Yu | 一个有故事的PM
Original丨原创