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.
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.
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?
Recall the pyramid generally has three floors: the penthouse filled with UI macro tests, the middle is inhabited by subcutaneous macro tests, and the ground floor–a plethora of micro tests. The goal of CI is to give valuable feedback to a team as fast as possible.
At this point, I hope you got the ideas of why overdoing the upper floors of the pyramid will cause it to tumble. In the previous episode I mentioned you can get a test pyramid worksheet. This worksheet can be used to plan out how to build your project’s mighty pyramid of test.