6

Could anybody share whether SAFe has helped practically scale agile development in bigger organizations.

Is there any other similar methodology or best practices document that could help with agile in bigger organization - projects with 100+ members.

6

I'm really not convinced by SAFe at all - I think it's too prescriptive and not nearly agile enough. It also encourages focus on vanity metrics that really don't mean much.

I think the best way to scale Agile in an enterprise is to allow teams to evolve independently and create a culture of sharing learning.

To solve the problem of portfolio management/dependency management or programme delivery across a large organsiation assign the responsibility to a strong programme manager who will cover the breadth of the organisation; Establish them as the defacto 'transient' PMO. close this PMO when the programme has completed.

All you need to present to senior leaders is a weekly one-line status for each workstream including Red, Yellow, Green; progress against stated milestones and any blockers (Top Risks and Issues).

This is the method I used at a large online global US based retailer and am using at a large global UK based physical/online retailer.

This paper also alludes to a similar method used by Spotify to implement agile at scale: this model on scaling agile at Spotify: http://ucvox.files.wordpress.com/2012/11/113617905-scaling-agile-spotify-11.pdf

4

Ken Schwaber, one of the initial signers of the Agile Manifesto, in his blog post recommends to Unsafe at Any Speed and states that SAFe is a "reincarnation" of RUP or even Waterfall.

0

I found Ken Rubin's Keynote at this year's Global Scrum Gathering in New Orleans to be a useful and thought-provoking presentation on scrum at scale https://www.youtube.com/watch?v=PcePFHD_p70

His presentation is available here http://www.innolution.com/uploads/presentations/Economically-Sensible-Scrum-2014-Scrum-Gathering-Ken-Rubin-Innolution.pdf

But I'd recommend listening to him while you follow along with the deck - he has a lot of useful things to say that are not sufficiently captured in his slides

0

There are 10s of Scaling frameworks available. I personally have only seen SAFe, LeSS, and Spotify in action. SAFe is the most popular agile scaling framework. and works particularly well in organisations with lower risk appetite for their agile transformation. Usually, in agile transformations, more pain means more gain. And little pain means little gain. I have seen fantastic SAFe implementations with great results.

By saying this, I'll be offending some anti-SAFe people. Well I'm myself both a Certified LeSS practitioner and a SAFe program consultant. I keep my emotions out and evaluate the advantages and disadvantages of frameworks objectively.

Now we must also consider that all frameworks are the starting point and organisations need to evolve beyond frameworks. For more information on this, please read on the Shu-Ha-Ri model and how to start with a framework and move to the right approach for your entire enterprise.

I do publish a lot of articles. If you are interested to know more about Agile and Scaling please see my blog here: https://sprintagile.com.au/blog/.

-1

SAFe is the most popular scaling framework by far and probably the one I would consider investigating further. We have used it at a handful of clients and all have been happy with the results. It really helps with alignment of various teams so they can work together better and deliver consistently.

It is good for multiple teams working on the same Program, or if you have lots of competing business requirements for the same development team.

The website has a ton of free resources. I'd also be happy to talk off-line about my experiences in more detail.

  • What's your basis for saying it's "the most popular scaling framework"? – Todd A. Jacobs Jul 5 '14 at 22:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.