War stories about Scaled Agile Framework by Tomasz Pająk
War stories about Scaled Agile Framework
Ken Schwaber and Dean Leffingwell argue what Scaled Agile Framework (SAFe) is and what is not. For sure the conflict isn't purely technical and one can smell politics behind it. But, who am I to state the ultimate truth?
Nevertheless, I will tell you war stories when a company (Seamless Payments) with its product (mobile payments system - SEQR) crosses the chasm between early adopters and early majority as defined by Geoffrey A. Moore in his book. When Sales and Marketing departments (and therefore a product) scale faster than Software Engineering department - it is definitely not funny for the latter. 'Ah, you should do Scrum of Scrums to solve your problems' was a piece of advice given to us by theorists. I would like to show you mistakes we had to make, evolution we had to undergo to achieve a state when our work is structured, it scales but there is no bureaucracy. We still do Scrum, we still take advantage of concepts from Lean world (eg. visualisation + optimization, A3s for requirements and documentation), we still have room for innovation but we gained a framework which helps us comprehensively define strategy for the product including business epics and architectural epics which focus on delivering business value as fast as possible.
Our conclusion is that Scrum and SAFe are not in conflict but are rather complementary which may be unacceptable to some :).
Scaled Agile Framework, Scrum, Lean
|Last Updated||30 Aug 20:05|