SCRUM vs SAFe : What's the difference? How are they related?
Vložit
- čas přidán 19. 05. 2021
- A super quick video describing the relationship between Agile Scrum & the Scaled Agile Framework (SAFe)
SAFe in the Real world example - • Scaled Agile Framework...
Short, clear and on point. Brilliant
I like the way you explain it without too much technical jargons. :)
That's always the goal! If you understood all the jargon, then chances are you don't need the explanation.
Excellently delivered. Thank you!👌🤗
The best and the shortest video to explain both Scrum n Safe. I like when you say: Safe is using the principles of Agile so Organization as a whole can become Agile and not just one small team.
Awesome presentation 👍
Thanks!
So crisp and neat 👍👌👏🙏
😁
This is super helpful!
This is amazingly explained.
Thanks!
Awesome video! Thank you!
Great description, Angelo. This gave me a different high level view of the difference. I recently watched a 45 minute video that didn't make it this clear.
I'm glad it was helpful to you
On the contrary to what you said in your first sentence - Scrum is not a methodology, it's a framework. It states so on the very first page of the Scrum Guide. And it wasn't born from the Agile manifesto, it was officially announced in 1995 while Agile manifesto was published in 2001.
I'll keep that in mind for future videos.
It was born from eXtreme Programming.
Thanks buddy, you're the man!. This is an awesome video.
Perfect and accurate
Thanks.
🔥🔥🔥
thanks
This is a nice concise summary of the theory and goals of SAFE. However, having seen SAFE in practice, the assumption that this will help management be more agile seems less true than management expecting Agile processes to be more waterfall. So, in practice, it doesn't necessarily drive Agile up the organizational ladder. I understand that your mileage will vary and every organization is different, but having met more than a few senior managers in my day, do you really think they expect to change when a new process is adopted? Just asking.
I think that teams/organizations that truly embrace agile at its core don't need a defined methodology. Each level of required definition speaks to the fact that the layer hasn't embraced an agile mindset. In my own experience, the willingness to embrace the mindset (true buy-in) is what determines its effectiveness. This is true even for Scrum, but at a team level it's easier to get buy-in. When you go up the rungs, you're basically dealing with people who've had years of experience/success without agile so every layer up presents more unagile indoctrination that needs to be overcome. If they were already of an agile mindset, they wouldn't need SAFe to begin with. Still, I think teams can benefit from management attempting to be agile with SAFe vs operating purely waterfall.
Thank you, this was very helpful. You SAFe'd me from misunderstanding. (B'dum tzzz!)
😂
Bless .... really good video but SAFe is actually a framework as in the name and follows the Agile methodology. Same as Scrum.
Cool, thanks
Wrong. SAFe breaks so many Agile/Scrum principles, for correct scaling check out LeSS (official Scaled Scrum framework).
This video is to explain SAFe, not argue it's efficacy against LeSS. On that point, I don't believe this video is incorrect.
@@AngeloTheBASure. I understand you are doing it from a SAFe perspective, which is fine, they can have any perspective they want. Agile/scrum founders would disagree on that scaling and relationship perspective though. There are so many misunderstandings on what Agile/Scrum is, and not going to the sources just makes it worse.
scrum is a framework*
Cool, thanks.
☯️🌏🕵🏻♂️♻️👣🌌