I agree with S.Lott. There are lots of Agile methods, not the one Agile method per se. Likewise I wouldn't know any central guide which covers All You Ever Wanted to Know About Agile.
I would actually recommend a book here. The one I found gave a pretty good introduction into how to go agile was O'Reilly's "The Art of Agile Development". Mind you, yeah, it is a book and therefore costs money, but not so much that it wouldn't be worth it if you really want to learn something.
There's nothing like specifically carrying out Agile. It's a bunch of methods and ways that you can adapt (or choose not to adapt). Some of them are more important than others, specific methods (like Scrum) define a couple of must-follow rules, whereas you can just as well pick what you think works best for you and see how it turns out.
I would actually recommend starting at one point with a good definition of Agile (the one at Wikipedia seems fine, along with a list of Agile methods and practices) and reading up on all the methods and practices from there. There will be googling involved.
Here's a downloadable book by Henrik Kniberg on Scrum and XP from the Trenches which describes in detail how his team did Scrum. When we implemented Scrum it was useful to have an in-depth look at what another team had found effective.
也许在您使用 scrum 一段时间后，您可以开始逐步采用更多 XP 实践。无论如何，scrum 没有任何关于代码、测试或重构等技术问题的内容 - 因此一旦您掌握了 scrum 基础知识，您就可以开始滚动一些 XP 实践。我认为测试驱动开发是第一个开始的。
There is no definitive resource for all agile methods - as there is so much diversity in the methods.
The people that came up with the word "agile" didn't actually have that much in common - so it's not as though there's an "international headquarters of agile"... ;-)
It depends which one you want to know about: Scrum or XP or Crystal or one of the other methods... some of them are quite different from each other...
Don't start out by reading a bunch of different methods you haven't tried out and mixing together the bits you like - a mistake that's far too common. That results in random chaos.
Best way to start:
Look at some agile methods
Pick the one you think is most practical to adopt in your circumstances.
Try doing it by the book for a while - say for at least a month.
After you've been doing it for a while, you can get the team together to run a retrospective to decide what to improve - or what to try instead.
Recommendation (assuming you don't have experienced help on hand)
Scrum is pretty easy to get going. You can set it up in about 2 days if you're familiar with the basics.
Maybe after you've done scrum for a while you can start phasing in more of the XP practices. In any case, scrum doesn't have anything to say about technical things like the code, testing or refactoring - so once you've got the scrum basics down, you could start rolling in some XP practices. I think Test-Driven Development is the first one to start with.
发布评论
评论（5）
敏捷方法有很多种。
没有一个。对于“敏捷”之类的东西，没有任何明确的说法。这就像“诚实”的权威指南。
阅读本文，了解一些人喜欢的一种敏捷方法：http://www.controlchaos.com /old-site/Scrumo.htm
另外，还有许多非敏捷方法。它们都有类似于以下的形式： http://en.wikipedia.org/wiki/Waterfall_model
There are numerous Agile methods.
Not one. And nothing definitive on something like "Agile". That's like a definitive guide to "Honesty".
Read this for one Agile method that some folks like: http://www.controlchaos.com/old-site/Scrumo.htm
Alos, there are numerous non-Agile methods. They'll all have a form similar to this: http://en.wikipedia.org/wiki/Waterfall_model
我同意 S.Lott 的观点。敏捷方法有很多种，但敏捷方法本身并不只有一种。同样，我也不知道任何涵盖您想了解的关于敏捷的所有中心指南。
我实际上会在这里推荐一本书。我发现，O'Reilly 的“敏捷开发的艺术”< /a>.请注意，是的，这是一本书，因此要花钱，但如果你真的想学点东西的话，也不会贵到不值得。
没有什么比专门实施敏捷更有效的了。这是一系列你可以适应（或选择不适应）的方法和方式。其中一些比其他更重要，特定方法（例如 Scrum）定义了一些必须遵循的规则，而您也可以选择您认为最适合您的方法，然后看看结果如何。
我实际上建议从一个好的敏捷定义开始（维基百科的定义似乎很好，以及敏捷方法和实践的列表）并阅读其中的所有方法和实践。将会涉及到谷歌搜索。
I agree with S.Lott. There are lots of Agile methods, not the one Agile method per se. Likewise I wouldn't know any central guide which covers All You Ever Wanted to Know About Agile.
I would actually recommend a book here. The one I found gave a pretty good introduction into how to go agile was O'Reilly's "The Art of Agile Development". Mind you, yeah, it is a book and therefore costs money, but not so much that it wouldn't be worth it if you really want to learn something.
There's nothing like specifically carrying out Agile. It's a bunch of methods and ways that you can adapt (or choose not to adapt). Some of them are more important than others, specific methods (like Scrum) define a couple of must-follow rules, whereas you can just as well pick what you think works best for you and see how it turns out.
I would actually recommend starting at one point with a good definition of Agile (the one at Wikipedia seems fine, along with a list of Agile methods and practices) and reading up on all the methods and practices from there. There will be googling involved.
这里是了解极限编程的好资源，极限编程是另一种敏捷方法。
Here is a good resource to learn about Extreme Programming which is another agile methodology.
这是 Henrik Kniberg 撰写的一本可下载的书，内容是 Scrum 和 XP from the Trenches 详细描述了他的团队如何进行 Scrum。当我们实施 Scrum 时，深入了解其他团队发现的有效方法很有用。
Here's a downloadable book by Henrik Kniberg on Scrum and XP from the Trenches which describes in detail how his team did Scrum. When we implemented Scrum it was useful to have an in-depth look at what another team had found effective.
没有适用于所有敏捷方法的权威资源 - 因为方法有如此多的多样性。
提出“敏捷”这个词的人实际上并没有那么多共同点 - 所以并不像是有一个“敏捷国际总部”...... ;-)
这取决于你想要哪个了解：Scrum 或 XP 或 Crystal 或其他方法之一...其中一些方法彼此之间有很大不同...
不要从阅读一堆你还没有尝试过的不同方法开始，然后将你喜欢的部分混合在一起 - 这是一个太常见的错误。这会导致随机混乱。
最佳开始方式：
建议（假设您手头没有经验丰富的帮助）
Scrum 非常容易上手。如果您熟悉基础知识，大约 2 天即可完成设置。
也许在您使用 scrum 一段时间后，您可以开始逐步采用更多 XP 实践。无论如何，scrum 没有任何关于代码、测试或重构等技术问题的内容 - 因此一旦您掌握了 scrum 基础知识，您就可以开始滚动一些 XP 实践。我认为测试驱动开发是第一个开始的。
There is no definitive resource for all agile methods - as there is so much diversity in the methods.
The people that came up with the word "agile" didn't actually have that much in common - so it's not as though there's an "international headquarters of agile"... ;-)
It depends which one you want to know about: Scrum or XP or Crystal or one of the other methods... some of them are quite different from each other...
Don't start out by reading a bunch of different methods you haven't tried out and mixing together the bits you like - a mistake that's far too common. That results in random chaos.
Best way to start:
Recommendation (assuming you don't have experienced help on hand)
Scrum is pretty easy to get going. You can set it up in about 2 days if you're familiar with the basics.
Maybe after you've done scrum for a while you can start phasing in more of the XP practices. In any case, scrum doesn't have anything to say about technical things like the code, testing or refactoring - so once you've got the scrum basics down, you could start rolling in some XP practices. I think Test-Driven Development is the first one to start with.