Bas Vodde, in the bay area. One of the founders of less.
Boss: How can we get the same fun dynamics of a single team but working with multiple teams?
Because often they add so much stuff and bureaucracy and distance between the teams and the actual users, that it’s no fun anymore.
Bas Vodde in the bay area, one of the founders of LeSS on “Why Scaling?”
I think you get the idea–there are a lot of different scaling Scrum frameworks. How to effectively scale Scrum from a single team to hundreds is the big question many in the industry are trying to solve.
假设你的工作是编写一个程序，在屏幕上输入单词“知道”。
Let’s say your job was to write a program that types to the screen the word: AWARE.
在过去的二十年中，敏捷革命曾经是很尖锐并且是可选择的，而现在是IT行业大多数团队使用SCRUM和看板的主流。您可能还没有意识到，尽管这两个流行的精简权重框架是有价值的更改。 它们根本不涉及如何构造支持频繁交付的代码。
Over the last twenty years the Agile revolution which used to be edgy and alternative is now mainstream with most teams in the IT industry using Scrum and Kanban. You may not have realized that although those two popular lite weight frameworks are valuable changes, they don’t at all address how to construct code that supports frequent delivery.
我们的今天也是未来[echo, jetsons sounds or future sounding music] 世界一直前进，但仍然没有飞行汽车[whawha wha..] 。嗯，的确有会飞的汽车但是却没有大规模生产。为什么不量产呢？我们的开发人员和经理是为什么仍然没有这么好的东西的部分原因吗？是lT低质量的跟踪记录的责任吗？我们必须使用补丁，然后安装，并且希望这个新版本不会使事情变得更糟？
Today is the future. [echo, jetsons sounds or future sounding music] The world has been marching forward but still there are no flying cars. [whawha wha..] Well, there are flying cars but none mass produced. Why not? Are We developers and we managers part of the reason why we still don’t have such nice things? Is the low quality track record of IT to blame? Must we be used getting patches, and upon installation, hoping this new version doesn’t make things worse?
连续集成坐标的测试金字塔的内容就像交响乐的指挥一样。
回顾金字塔一般有三层：阁楼里充满了UI宏观测试，中间有皮下宏观测试，底层是大量的微观测试。CI的目标是尽可能快地向团队提供有价值的反馈。
