我们的博客

10 Key Principles of 敏捷 Development

敏捷原则10:狙击手无处可去!

敏捷 development relies on close cooperation and collaboration between all team members and stakeholders. 敏捷 development principles include keeping requirements and documentation lightweight, and acknowledging that change is a normal and acceptable reality in software development. This makes close collaboration particularly important to clarify requirements just-in-time and to keep all team members (including the product owner) ‘on the same page’

Read More »

Agile Principle 9: 敏捷 Testing Is Not For Dummies!

在敏捷开发中,testing is integrated throughout the lifecycle; testing the software continuously throughout its development. 敏捷 development does not have a separate test phase as such. Developers are much more heavily engaged in testing, writing automated repeatable unit tests to validate their code. Apart from being geared towards better quality software, this is also important to support the principle

Read More »

敏捷原则8:足够就够了!

帕累托’s law is more commonly known as the 80/20 rule. The theory is about the law of distribution and how many things have a similar distribution curve. This means that *typically* 80% of your results may actually come from only 20% of your efforts! 帕累托’可以在许多情况下看到法律–不是字面上的80/20,而是原理

Read More »

Agile Principle 7: Done 我 ans 完成!

在敏捷开发中,“done” should really mean “DONE!”。在迭代中开发的功能(Scrum中的Sprint)应在Sprint结束时100%完成。在软件开发中太频繁了“done” doesn’t really mean “DONE!”. It doesn’不是指经过测试。它没有’它不一定意味着风格。当然不会’通常是指产品所有者接受的产品。它只是意味着发达。

Read More »

敏捷原则6:快速但不那么生气

敏捷 development is all about frequent delivery of products. In a truly agile world, gone are the days of the 12 month project. In an agile world, a 3-6 month project is strategic! Nowhere is this more true than on the web. The web is a fast moving place. And with the luxury of centrally hosted solutions, there’s every opportunity

Read More »

敏捷原则5:如何吃大象?

你怎么吃大象?一次咬一口!同样,敏捷开发项目以小块形式交付,交付小规模的增量发布和迭代。在更传统的软件开发项目中,(简化的)生命周期是分析,开发,测试–首先收集整个产品的所有已知需求,然后开发软件的所有元素,然后进行测试

Read More »

Agile Principle 4: 敏捷 Requirements Are Barely Sufficient

敏捷 development teams capture requirements at a high level and on a piecemeal basis, just-in-time for each feature to be developed. 敏捷 requirements are ideally visual and should be barely sufficient, i.e. the absolute minimum required to enable development and testing to proceed with reasonable efficiency. The rationale for this is to minimise the time spent on anything that doesn’t

Read More »

敏捷原则3:时间在等待无人!

在敏捷开发中,requirements evolve, but timescales are fixed. This is in stark contrast to a traditional development project, where one of the earliest goals is to capture all known requirements and baseline the scope so that any other changes are subject to change control. Traditionally, users are educated that it’s much more expensive to change or add requirements during

Read More »

Agile Principle 2: 敏捷 Development Teams Must Be Empowered

敏捷开发团队必须包括所有必要的团队成员,以制定决策并及时做出决策。积极的用户参与是实现这一目标的关键原则之一,因此,业务的用户或用户代表必须每天密切参与。必须授权项目团队在以下方面做出决策

Read More »

敏捷原则1:积极参与用户势在必行

在我看来,积极参与用户是敏捷开发的首要原则。它’让用户直接参与开发项目并非总是可能的,尤其是在敏捷开发项目是要构建产品的地方,真正的最终用户将是外部客户或消费者的情况下。在这种情况下,必须有资深和经验丰富的用户

Read More »

搜索博客

敏捷 Management Made Easy!

All About 敏捷

凯利·沃特斯(Kelly Waters)

“’Agile’ is one of the biggest buzzwords of the last decade. 敏捷 methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”

凯利·沃特斯

敏捷 101 is available to purchase. GAME ON!

敏捷 101

艾玛·霍普金森火花

“尽管有很多方法可以根据您拥有的团队和想要的学习成果来改变游戏,但是游戏的基本流程是所有人共有的。”
艾玛·霍普金森火花

我们为什么制作游戏?

怎么玩游戏?

联系我们

如果您想与101 Ways的团队之一联系,请填写以下表格或给我们发送电子邮件: contact-us@101ways.com.