The Scaled Agile Framework (SAFe) is one of the best know approach for scaling Agile practices. In a recent article, Al Shalloway proposes his own assessment of this framework, explaining which parts are good and which parts could be counter-productive or difficult to implement.
There are now several frameworks designed for scaling agile. This talk explains the flaws in such frameworks, why they so often fail to produce the desired effects, and what we should do instead. It also addresses some common organizational obstacles to moving fast at scale: governance, budgeting, and the project paradigm – and discusses how to address them. Warning: this talk includes liberal use of real, statistically sound data.
Using an Agile approach for software development does not necessarily guarantee success. As Henrik Kniberg wrote at the beginning of his blog post ” Even if the entire organization is neatly organized into scrum teams, you can still end up with an unaligned mess!”. Having an Agile leader can help preventing the unaligned mess.
The Scaled Agile Framework (SAFe) is controversial. At first glance SAFe looks a bit like a big scary heavy-weight top-down RUP-zombie. But what about in real life?
If the basic principles of the Agile Manifesto and the Scrum framework are simple managing global Agile software development projects in the corporate world is sometimes more complex and complicated. This article lists some approaches that have been created to answers the specific questions raised by scaling Agile practices in large organizations.
Spotify have been growing quickly as a company and it is continuously experimenting with ways of making the company work as effective as possible. Creating strong team autonomy and making sure everybody is aligned requires effective and strong servant leadership.
Scaling and implementing an Agile approach in large projects is one of the hot topic in the Agile community, a natural consequences of the adoption of Agile by larger corporation. In this blog post, Ritika Nanwani shares some of her observations as a member of a large Scrum project.
Copyright © 2009-2019 Martinig & Associates