If we're talking about the benefits only they are pretty much obvious.
Using a proper methodology you work better, i.e. you have higher rate of successful projects. If your projects are already 100% successful you probably do not need to change anything.
For us using Agile helps to:
Increase the quality of the deliverables (because of the strict iteration rules, when you expect everything to be working by the end of the iteration instead of 'coding being complete' it works wonders)
Cope better with the changes (and expect the changes. It's mostly psychological issue but it really helps when your developers expect that a requirement will change at some point)
Provide better estimates and spend less time doing them
Be more in control of the project schedule and state (short iterations, clear, unambiguous ways of calculating the velocity etc.)
As a result we achieve higher customers satisfaction rate in general
In my experience, the main benefit is that your manager gets to say you are doing Scrum, and you get to waste more time going to daily meetings instead of getting work done.
... it's possible they weren't doing it right ;-).
For the team you describe I see these main benefits:
Visibility into what's happening and accountability. During the SHORT daily meeting you get a better idea of what's happening, what was finished and what was not. After some time you start to see trends: who's good estimating, who is not, who is telling you they are working when they really are not. You have a better picture of when you are going to be done.
Self organization. The team members are the ones that pick what to do and when for the given iteration. This takes time when people are not used to it, but ends up making team members happier because nobody is dictating who gets to do what. They decide.
Improved ability to rapidly react to requirements changes. The concepts of time boxing , daily status checks and user involvement will make it easier to both capture feedback and change your priorities.
我认为 XP 和 Scrum 之间没有太大区别。 如果您已经拥有 XP，则可能不需要切换。 也许采用一些 Scrum 特定实践来获得更好的可扩展性，例如 Scrum-of-Scrums。 几乎所有其他实践都存在于 XP 中，例如每日会议、迭代、角色分离、回顾等。
事实上，我不确定这种分离是否有好处。 最好在回顾会议期间确定您做错了什么，并将任何流程中的实践（或创建自己的解决方案）应用于您的具体问题。 XP 和 Scrum 为您提供了一个有助于提高适应性和创造力的框架。 虽然传统流程为您提供了一套阻碍任何创造性行为的规则。
您的团队和您的项目很特别。 思考和沟通可以提高您的开发过程。
I don't see much differences between XP and Scrum. If you already have XP, you likely don't need to switch. Maybe adopt some Scrum specific practices for better scalability like Scrum-of-Scrums. Almost all the other practices exist in XP like daily meetings, iterations, roles separation, retrospectives, etc.
In fact I am not sure that such separation have benefits. It is bette to decide what you are doing bad during retrospective meetings and apply practices from any process (or create own solutions) to your specific problems. XP and Scrum give you a framework that will help to be adaptive and creative. While traditional processes gives you a set of rules that impedance any creative behavior.
Your team and your project IS special. Think and communicate to sharpen your development process.
First of all Scrum is a methodology for project management not for development...it can be combined with XP or RUP...
Scrum is good for you if you have a project that changes...when your requierements changes you need to keep up with these changes... Scrum has short iterations (2-4 weeks) and this provides more response to the changes... and the client can have a early release of his product and you can have all that feedback you need... maybe this is the first benefit...
Another benefit: your team will be always working syncronized specially when they depend on each other...
As I understand it, daily Scrum meetings are for the team to discuss progress and blocking issues. The Scrum master facilitates. The product owner can be invited if the team decides to do so, but the meeting is not intended to provide any progress status to a boss or a manager.
When you say "Scrum" I don't know if you mean agile, or just the daily meeting. Assuming you just mean what is the advantage of the daily meeting I see 3
1 - You have an opportunity to expose any issues you are having to the entire team and can get help an advice from people you might not have thought to ask. It's more efficient that having to interrupt coworkers throughout the day to try to get help for some problems you're having.
2 - Group teams get a better picture of what the entire group is doing and you have an opportunity to influence development you're not immediately involved in.
3 - You generally get to spend less time writing progress reports because everyone, including your boss, hears everyday what you're working on and what progress you've made.
I've been "Scruming" for two years and my experience tells me that it's much easier to know "where we are" at any point because the development process is in fixed length periods (Sprints) that allows to evaluate what's been done. And in the middle of those periods having the Daily Scrum (those meetings Dmitriy was talking about) and the Burndown Chart (the graphic of the remaining work) allows the team and the manager to always know what's already done and what's the team is working on.
In your case you'll probably need to have several smaller Scrums, instead of a large one, because Scrum works best with smaller teams. This book has some insights about that: http://www.infoq.com/minibooks/scrum-xp-from-the-trenches
I think scrum is more of a habit than a method or practice. There are lot of teams operating in scrum without knowing that they are doing agile and there could be lot of teams claiming that they are agile and not following the basic principles of scrum.
I have worked with kanban, waterfall, agile scrum and others while development software products and with my experience, I am more comfortable with scrum. It gives you sense of achievement and keep you awake in the light of what needs to be achieved further and how to do it.
Scrum product development methodology is based on incremental and iterative product development process where solutions grow due to collaboration between cross-functional and self-organizing teams. Here are the major benefits of scrum
Simplicity and transparency of processes
Adaptive planning
Quick adaptability to change
Evolutionary development and delivery model
Iterative approach
Quick learning cycles
Automated testing offers a stable platform
Rapid market release
Integrated and flexible teams which can change requirements anytime based on user feedback
Team Spirit High visibility of progress. Frequent demonstration and early feedback from stakeholders Problems are identified early Quality of product and Improved productivity Higher customer satisfaction
发布评论
评论（13）
根据我的经验，我认为 Scrum 的主要特点是：
这些功能带来了以下好处：
Based on my experience, I would say the key features of Scrum are:
And these features lead to the following benefits:
如果我们谈论好处，只是它们非常明显。
使用正确的方法，您可以更好地工作，即您的项目成功率更高。 如果您的项目已经 100% 成功，您可能不需要进行任何更改。
对于我们来说，使用敏捷有助于：
更好地控制项目进度和状态（短迭代、清晰、明确的计算速度的方法等）
因此，我们总体上实现了更高的客户满意度
If we're talking about the benefits only they are pretty much obvious.
Using a proper methodology you work better, i.e. you have higher rate of successful projects. If your projects are already 100% successful you probably do not need to change anything.
For us using Agile helps to:
Be more in control of the project schedule and state (short iterations, clear, unambiguous ways of calculating the velocity etc.)
As a result we achieve higher customers satisfaction rate in general
根据我的经验，主要的好处是你的经理会说你正在做 Scrum，你会浪费更多的时间去参加日常会议而不是完成工作。
...他们可能没有做得正确;-)。
In my experience, the main benefit is that your manager gets to say you are doing Scrum, and you get to waste more time going to daily meetings instead of getting work done.
... it's possible they weren't doing it right ;-).
对于您描述的团队，我看到了以下主要好处：
对正在发生的事情的可见性和问责制。 在简短的日常会议中，您可以更好地了解正在发生的事情、已完成的事情和尚未完成的事情。 一段时间后，您开始看到趋势：谁的估计准确，谁的估计不准确，谁告诉您他们在工作，而实际上却没有。 您可以更好地了解何时完成。
自组织。 团队成员是选择在给定迭代中做什么和何时做的人。 当人们不习惯时，这需要时间，但最终会让团队成员更快乐，因为没有人规定谁可以做什么。 他们决定。
提高对需求变化快速反应的能力。 时间限制、每日状态检查和用户参与的概念将使捕获反馈和改变优先级变得更容易。
For the team you describe I see these main benefits:
Visibility into what's happening and accountability. During the SHORT daily meeting you get a better idea of what's happening, what was finished and what was not. After some time you start to see trends: who's good estimating, who is not, who is telling you they are working when they really are not. You have a better picture of when you are going to be done.
Self organization. The team members are the ones that pick what to do and when for the given iteration. This takes time when people are not used to it, but ends up making team members happier because nobody is dictating who gets to do what. They decide.
Improved ability to rapidly react to requirements changes. The concepts of time boxing , daily status checks and user involvement will make it easier to both capture feedback and change your priorities.
我认为 XP 和 Scrum 之间没有太大区别。 如果您已经拥有 XP，则可能不需要切换。 也许采用一些 Scrum 特定实践来获得更好的可扩展性，例如 Scrum-of-Scrums。 几乎所有其他实践都存在于 XP 中，例如每日会议、迭代、角色分离、回顾等。
事实上，我不确定这种分离是否有好处。 最好在回顾会议期间确定您做错了什么，并将任何流程中的实践（或创建自己的解决方案）应用于您的具体问题。 XP 和 Scrum 为您提供了一个有助于提高适应性和创造力的框架。 虽然传统流程为您提供了一套阻碍任何创造性行为的规则。
您的团队和您的项目很特别。 思考和沟通可以提高您的开发过程。
I don't see much differences between XP and Scrum. If you already have XP, you likely don't need to switch. Maybe adopt some Scrum specific practices for better scalability like Scrum-of-Scrums. Almost all the other practices exist in XP like daily meetings, iterations, roles separation, retrospectives, etc.
In fact I am not sure that such separation have benefits. It is bette to decide what you are doing bad during retrospective meetings and apply practices from any process (or create own solutions) to your specific problems. XP and Scrum give you a framework that will help to be adaptive and creative. While traditional processes gives you a set of rules that impedance any creative behavior.
Your team and your project IS special. Think and communicate to sharpen your development process.
首先，Scrum 是一种项目管理方法，而不是开发方法...它可以与 XP 或 RUP 结合...
如果您的项目发生变化，Scrum 对您有好处...当您的需求发生变化时，您需要保留适应这些变化...Scrum 的迭代很短（2-4 周），这提供了对变化的更多响应...并且客户可以提前发布他的产品，并且您可以获得所需的所有反馈...也许这是第一个好处...
另一个好处：您的团队将始终同步工作，特别是当他们相互依赖时...
First of all Scrum is a methodology for project management not for development...it can be combined with XP or RUP...
Scrum is good for you if you have a project that changes...when your requierements changes you need to keep up with these changes... Scrum has short iterations (2-4 weeks) and this provides more response to the changes... and the client can have a early release of his product and you can have all that feedback you need... maybe this is the first benefit...
Another benefit: your team will be always working syncronized specially when they depend on each other...
据我了解，每天的 Scrum 会议是让团队讨论进度和阻塞问题。 Scrum master 提供便利。 如果团队决定这样做，可以邀请产品负责人，但会议的目的不是向老板或经理提供任何进度状态。
我希望我是对的。
As I understand it, daily Scrum meetings are for the team to discuss progress and blocking issues. The Scrum master facilitates. The product owner can be invited if the team decides to do so, but the meeting is not intended to provide any progress status to a boss or a manager.
I hope I am correct.
当你说“Scrum”时，我不知道你指的是敏捷，还是只是日常会议。 假设您只是指每日会议的优势是什么，我认为 3
1 - 您有机会向整个团队揭露您遇到的任何问题，并且可以从您可能没有想到要询问的人那里获得帮助和建议。 这比整天打断同事去寻求帮助来解决你遇到的一些问题要更有效率。
2 - 小组团队可以更好地了解整个小组正在做什么，并且您有机会影响您没有立即参与的开发。
3 - 您通常可以花更少的时间编写进度报告，因为每个人，包括您的老板，每天都会听到您正在做什么以及取得了哪些进展。
这就是我的 scrum 经验
When you say "Scrum" I don't know if you mean agile, or just the daily meeting. Assuming you just mean what is the advantage of the daily meeting I see 3
1 - You have an opportunity to expose any issues you are having to the entire team and can get help an advice from people you might not have thought to ask. It's more efficient that having to interrupt coworkers throughout the day to try to get help for some problems you're having.
2 - Group teams get a better picture of what the entire group is doing and you have an opportunity to influence development you're not immediately involved in.
3 - You generally get to spend less time writing progress reports because everyone, including your boss, hears everyday what you're working on and what progress you've made.
That's my experience with scrum
我已经“摸索”了两年，我的经验告诉我，在任何时候都更容易知道“我们在哪里”，因为开发过程是固定长度的周期（冲刺），可以评估已完成的工作。 在这些期间的中间，每日 Scrum（德米特里正在谈论的那些会议）和燃尽图（剩余工作的图形）可以让团队和经理始终了解已经完成的工作以及团队正在做什么。
在您的情况下，您可能需要几个较小的 Scrum，而不是一个大的 Scrum，因为 Scrum 最适合较小的团队。 这本书对此有一些见解：
http://www.infoq.com/minibooks/scrum-xp-战壕里的
I've been "Scruming" for two years and my experience tells me that it's much easier to know "where we are" at any point because the development process is in fixed length periods (Sprints) that allows to evaluate what's been done. And in the middle of those periods having the Daily Scrum (those meetings Dmitriy was talking about) and the Burndown Chart (the graphic of the remaining work) allows the team and the manager to always know what's already done and what's the team is working on.
In your case you'll probably need to have several smaller Scrums, instead of a large one, because Scrum works best with smaller teams. This book has some insights about that:
http://www.infoq.com/minibooks/scrum-xp-from-the-trenches
你不会迟到的最后期限:)
You won't get deadlines getting late :)
我认为 Scrum 与其说是一种方法或实践，不如说是一种习惯。 有很多团队在 Scrum 中运作，但并不知道他们正在实施敏捷，并且可能有很多团队声称他们是敏捷的，但并不遵循 Scrum 的基本原则。
I think scrum is more of a habit than a method or practice. There are lot of teams operating in scrum without knowing that they are doing agile and there could be lot of teams claiming that they are agile and not following the basic principles of scrum.
我在开发软件产品时曾使用过看板、瀑布、敏捷 Scrum 等，根据我的经验，我对 Scrum 更熟悉。 它会给你成就感，让你清醒地知道需要进一步实现什么以及如何实现。
Scrum 产品开发方法基于增量和迭代的产品开发过程，其中解决方案由于跨职能和自组织团队之间的协作而不断增长。 以下是 Scrum 的主要优点
我觉得我已经对答案做出了足够的公正。
您可以在这里了解更多我的经验：http ://www.cygnet-infotech.com/blog/agile-scrum-methodology-for-product-engineering
I have worked with kanban, waterfall, agile scrum and others while development software products and with my experience, I am more comfortable with scrum. It gives you sense of achievement and keep you awake in the light of what needs to be achieved further and how to do it.
Scrum product development methodology is based on incremental and iterative product development process where solutions grow due to collaboration between cross-functional and self-organizing teams. Here are the major benefits of scrum
I feel I have made enough justice to the answer.
Here is where you can learn more on my experience: http://www.cygnet-infotech.com/blog/agile-scrum-methodology-for-product-engineering
团队精神
进展的高度可见性。
利益相关者的频繁演示和早期反馈
及早发现问题
产品质量和生产力提高
更高的客户满意度
Team Spirit
High visibility of progress.
Frequent demonstration and early feedback from stakeholders
Problems are identified early
Quality of product and Improved productivity
Higher customer satisfaction