We've updated our privacy policy. Click here to review the details. Tap here to review the details.
Activate your 30 day free trial to unlock unlimited reading.
Activate your 30 day free trial to continue reading.
Download to read offline
"An agile report compares agile scaling approaches in terms of their market penetration. In Section 6, NEXUS is mentioned at 1% first time this year, LeSS loses 1% to 3% and SAFe is the clear market leader with 28%. Between the frameworks, there are often bitter discussions in the appropriate forums on the Internet, who advocates the better scaling approach. This is in my opinion, but an unnecessary disgusting discussion, because
1. The differences in each implementation of a framework are strongly influenced by the corporate culture.
2. Frameworks are customizable by definition.
I therefore would like to deal with commonalities and the main emphasis of the three scaling methods.
It is e.g. an essential difference whether:
1. Three teams of seven developers working on one product - ,
or several 100 employees creating a solution with integration of hardware and software or the involvement of (agile) suppliers
2. The enterprise portfolio management should be agile.
3. The Scrum teams should be organized over a long-term budgeting along the Valuestreams.
4. The goal is to scale agile in a startup or in a young company. - or a classic enterprise like LEGO wants to be agile."
"An agile report compares agile scaling approaches in terms of their market penetration. In Section 6, NEXUS is mentioned at 1% first time this year, LeSS loses 1% to 3% and SAFe is the clear market leader with 28%. Between the frameworks, there are often bitter discussions in the appropriate forums on the Internet, who advocates the better scaling approach. This is in my opinion, but an unnecessary disgusting discussion, because
1. The differences in each implementation of a framework are strongly influenced by the corporate culture.
2. Frameworks are customizable by definition.
I therefore would like to deal with commonalities and the main emphasis of the three scaling methods.
It is e.g. an essential difference whether:
1. Three teams of seven developers working on one product - ,
or several 100 employees creating a solution with integration of hardware and software or the involvement of (agile) suppliers
2. The enterprise portfolio management should be agile.
3. The Scrum teams should be organized over a long-term budgeting along the Valuestreams.
4. The goal is to scale agile in a startup or in a young company. - or a classic enterprise like LEGO wants to be agile."
You just clipped your first slide!
Clipping is a handy way to collect important slides you want to go back to later. Now customize the name of a clipboard to store your clips.The SlideShare family just got bigger. Enjoy access to millions of ebooks, audiobooks, magazines, and more from Scribd.
Cancel anytime.Unlimited Reading
Learn faster and smarter from top experts
Unlimited Downloading
Download to take your learnings offline and on the go
You also get free access to Scribd!
Instant access to millions of ebooks, audiobooks, magazines, podcasts and more.
Read and listen offline with any device.
Free access to premium services like Tuneln, Mubi and more.
We’ve updated our privacy policy so that we are compliant with changing global privacy regulations and to provide you with insight into the limited ways in which we use your data.
You can read the details below. By accepting, you agree to the updated privacy policy.
Thank you!