mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
Xingyu.Wang
GitHub
commit
7423b32e87
@ -1,65 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (algzjh)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (The best resources for agile software development)
|
||||
[#]: via: (https://opensource.com/article/19/12/agile-resources)
|
||||
[#]: author: (Leigh Griffin https://opensource.com/users/lgriffin)
|
||||
|
||||
The best resources for agile software development
|
||||
======
|
||||
Read our top articles that highlight the discussion around agile's past,
|
||||
present, and what it may look like in the future.
|
||||
![Women programming][1]
|
||||
|
||||
It has been a great year for agile topics on Opensource.com. As we approach the end of 2019, reviewed our top agile-related articles, as read by you, our readers!
|
||||
|
||||
### Small Scale Scrum guide
|
||||
|
||||
Opensource.com's six-part guide to [Small Scale Scrum][2] (which I helped co-author) advises smaller teams on how to bring agile into their work. The traditional scrum framework outlined in the official [Scrum Guide][3] recommends a minimum of three people for the framework to realize its full potential. However, it provides no guidance for how teams of one or two people can follow scrum successfully. Our six-part series aims to formalize Small Scale Scrum and examines our experience with it in the real world. The series was received very warmly by our readers—so much such that the six individual articles comprise 60% of our Top 10 list. So, if you haven't already, make sure to download them from our [_Introduction to Small Scale Scrum_ page][2].
|
||||
|
||||
### A comprehensive guide to agile project management
|
||||
|
||||
Teams following traditional project management approaches, initially skeptical about agile, have warmed up to the agile way of working. Now agile has reached acceptance, and a more flexible, hybrid style has found a home. [_A comprehensive guide to agile project management_][4] by Matt Shealy covers 12 guiding principles of agile project management and is perfect for traditional project managers looking to bring some agility to their projects.
|
||||
|
||||
### 4 steps to becoming an awesome agile developer
|
||||
|
||||
A DevOps culture has emerged in many modern software teams that embrace agile software development principles that leverage cutting-edge tooling and automation. But this mechanically agile approach does not guarantee that developers are following agile practices in their day-to-day work. In [_4 steps to becoming an awesome agile developer_][5], Daniel Oh gives great tips for increasing your agility by focusing on design thinking, using predictable approaches, putting quality at the center, and continuously learning and exploring. Complementing these methods with your agile tooling will create very flexible and strong agile developers.
|
||||
|
||||
### Scrum vs. kanban: Which agile framework is better?
|
||||
|
||||
Scrum and kanban are two of the most popular approaches for teams running in an agile manner, and in [_Scrum vs. kanban: Which agile framework is better?_][6] Taz Brown explores the history and purpose of both. While reading this article, a great saying came to my mind: "If the only tool in your toolbox is a hammer, every problem looks like a nail." Knowing when to use kanban and when to use scrum is important, and this article helps show that both have a place, depending on your team, your challenge, and your goals.
|
||||
|
||||
### 4 ways developers can have a say in what agile looks like
|
||||
|
||||
Developers often have a fear of having a workstyle imposed upon them when the topic of adopting agile comes up. In [_4 ways developers can have a say in what agile looks like_][7], [Clément Verna][8] looks at ways that developers can flip that narrative by helping to determine what agile looks like on their team. Examining the origins and the basics of agile is a great starting point, but the real value is in having metrics to help guide your journey. Knowing what challenges you can expect to have will give you a firm ground to move forward. And making decisions empirically not only empowers teams but gives them a sense of ownership of the journey. Verna's article also examines the importance of putting people over processes and working as a team to achieve your goals.
|
||||
|
||||
### Agile now and later
|
||||
|
||||
This year, Opensource.com authors created a lot of discussion around agile's past, present, and what it may look like in the future. Thank you to all of them, and be sure to [share your own agile story][9] here in 2020.
|
||||
|
||||
A look back at the tools Opensource.com covered in 2014 and 2015 , with updates on new releases,...
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/agile-resources
|
||||
|
||||
作者：[Leigh Griffin][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/lgriffin
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/collab-team-pair-programming-code-keyboard2.png?itok=WnKfsl-G (Women programming)
|
||||
[2]: https://opensource.com/downloads/small-scale-scrum
|
||||
[3]: https://scrumguides.org/scrum-guide.html
|
||||
[4]: https://opensource.com/article/19/8/guide-agile-project-management
|
||||
[5]: https://opensource.com/article/19/2/steps-agile-developer
|
||||
[6]: https://opensource.com/article/19/8/scrum-vs-kanban
|
||||
[7]: https://opensource.com/article/19/10/ways-developers-what-agile
|
||||
[8]: https://twitter.com/clemsverna
|
||||
[9]: https://opensource.com/how-submit-article
|
||||
@ -0,0 +1,64 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (algzjh)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (The best resources for agile software development)
|
||||
[#]: via: (https://opensource.com/article/19/12/agile-resources)
|
||||
[#]: author: (Leigh Griffin https://opensource.com/users/lgriffin)
|
||||
|
||||
敏捷软件开发的最佳资源
|
||||
======
|
||||
请阅读我们的热门文章，这些文章着重讨论了敏捷的过去、现在和未来。
|
||||
![Women programming][1]
|
||||
|
||||
对于 Opensource.com 上的敏捷主题来说，今年是非常棒的一年。随着 2019 年的临近，我们回顾了我们读者所读的与敏捷相关的热门文章。
|
||||
|
||||
### 小规模 Scrum 指南
|
||||
|
||||
Opensource.com 关于[小规模 Scrum][2] 的指南（我曾参与合著）由六部分组成，为小型团队提供了关于如何将敏捷引入到他们的工作中的建议。在官方的 [Scrum 指南][3] 的概述中，传统的 Scrum 框架推荐至少三个人来实现，以充分发挥其潜力。但是，它并没有为一两个人的团队如何成功遵循 Scrum 提供指导。我们的六部分系列旨在规范化小规模的 Scrum，并检验我们在现实世界中使用它的经验。该系列受到了读者的热烈欢迎，以至于这六篇文章占据了前 10 名文章的 60%。因此，如果你还没有阅读的话，一定要从我们的[小规模 Scrum 介绍页面][2]下载。
|
||||
|
||||
### 全面的敏捷项目管理指南
|
||||
|
||||
遵循传统项目管理方法的团队最初对敏捷持怀疑态度，现在已经热衷于敏捷的工作方式。目前，敏捷已被接受，并且一种更加灵活的混合风格已经找到了归宿。Matt Shealy 撰写的[有关敏捷项目管理的综合指南][4]涵盖了敏捷项目管理的 12 条指导原则，对于希望为其项目带来敏捷性的传统项目经理而言，它是完美的选择。
|
||||
|
||||
### 成为出色的敏捷开发人员的 4 个步骤
|
||||
|
||||
DevOps 文化已经出现在许多现代软件团队中，这些团队采用了敏捷软件开发原则，利用了最先进的工具和自动化技术。但是，这种机械的敏捷方法并不能保证开发人员在日常工作中遵循敏捷实践。Daniel Oh 在[《成为出色的敏捷开发人员的 4 个步骤》][5]中给出了一些很棒的技巧，通过关注设计思维，使用可预测的方法，以质量为中心并不断学习和探索来提高你的敏捷性。用你的敏捷工具补充这些方法将形成非常灵活和强大的敏捷开发人员。
|
||||
|
||||
### Scrum 和 kanban：哪种敏捷框架更好？
|
||||
|
||||
对于以敏捷方式运行的团队来说，Scrum 和 kanban 是两种最流行的方法。在 “[Scrum 与 kanban：哪种敏捷框架更好？][6]” 中，Taz Brown 探索了两者的历史和目的。在阅读本文时，我想起一句名言：“如果你的工具箱里只有锤子，那么所有问题看起来都像钉子。”知道何时使用 kanban 以及何时使用 Scrum 非常重要，本文有助于说明两者都有一席之地，这取决于你的团队、挑战和目标。
|
||||
|
||||
### 开发人员对敏捷发表意见的 4 种方式
|
||||
|
||||
当采用敏捷的话题出现时，开发人员常常会担心自己会被强加上一种工作风格。在“[开发人员对敏捷发表意见的 4 种方式][7]”中，[Clément Verna][8] 着眼于开发人员通过帮助确定敏捷在其团队中的表现形式来颠覆这种说法的方法。检查敏捷的起源和基础是一个很好的起点，但是真正的价值在于拥有可帮助指导你的过程的指标。知道你将面临什么样的挑战会给你的前进提供坚实的基础。根据经验进行决策不仅可以增强团队的能力，还可以使他们对整个过程有一种主人翁意识。Verna 的文章还探讨了将人置于过程之上并作为一个团队来实现目标的重要性。
|
||||
|
||||
### 敏捷的现在和未来
|
||||
|
||||
今年，Opensource.com 的作者围绕敏捷的过去、现在以及未来可能会是什么样子进行了大量的讨论。感谢他们所有人，请一定于 2020 年在这里分享[你自己的敏捷故事][9]。
|
||||
|
||||
回顾一下 Opensource.com 在 2014 年和 2015 年报道的工具，以及新版本的更新，……
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/agile-resources
|
||||
|
||||
作者：[Leigh Griffin][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[algzjh](https://github.com/algzjh)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/lgriffin
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/collab-team-pair-programming-code-keyboard2.png?itok=WnKfsl-G "Women programming"
|
||||
[2]: https://opensource.com/downloads/small-scale-scrum
|
||||
[3]: https://scrumguides.org/scrum-guide.html
|
||||
[4]: https://opensource.com/article/19/8/guide-agile-project-management
|
||||
[5]: https://opensource.com/article/19/2/steps-agile-developer
|
||||
[6]: https://opensource.com/article/19/8/scrum-vs-kanban
|
||||
[7]: https://opensource.com/article/19/10/ways-developers-what-agile
|
||||
[8]: https://twitter.com/clemsverna
|
||||
[9]: https://opensource.com/how-submit-article
|
||||
Loading…
Reference in New Issue
Block a user