SCRUM vs SAFe : What's the difference? How are they related?
A super quick video describing the relationship between Agile Scrum & the Scaled Agile Framework (SAFe) SAFe in the Real world example - • Scaled Agile Framework...
Жүктеу.....
Пікірлер: 35
@charliemathews85352 жыл бұрын
Short, clear and on point. Brilliant
@sadiej.22422 жыл бұрын
Excellently delivered. Thank you!👌🤗
@Ducky_logan2 жыл бұрын
I like the way you explain it without too much technical jargons. :)
@AngeloTheBA
2 жыл бұрын
That's always the goal! If you understood all the jargon, then chances are you don't need the explanation.
@23Hussam3 ай бұрын
This is amazingly explained. Thanks!
@Vishalforu Жыл бұрын
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 👍
@AngeloTheBA
Жыл бұрын
Thanks!
@ALifeofPeculiarity2 жыл бұрын
This is super helpful!
@SylOmope Жыл бұрын
Thanks buddy, you're the man!. This is an awesome video.
@lizardonastick Жыл бұрын
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.
@AngeloTheBA
Жыл бұрын
I'm glad it was helpful to you
@akanshababbar71333 жыл бұрын
So crisp and neat 👍👌👏🙏
@AngeloTheBA
3 жыл бұрын
😁
@FlowersgirlJ Жыл бұрын
Awesome video! Thank you!
@JuicyRussianMartini Жыл бұрын
Perfect and accurate
@AngeloTheBA
Жыл бұрын
Thanks.
@justynak.66862 жыл бұрын
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.
@AngeloTheBA
2 жыл бұрын
I'll keep that in mind for future videos.
@ggaccentc
2 ай бұрын
It was born from eXtreme Programming.
@kenpc102 жыл бұрын
🔥🔥🔥
@StaRRFeaK Жыл бұрын
thanks
@bennguyen1313Ай бұрын
Are most big aerospace, medical and nuclear companies using Agile or Scrum? And how does it affect the software development process? I'd like to move away from the rapid-prototype style to a more formal environment.. perhaps not for FAA/FDA/DOE approval, but to develop high quality/safe products containing embedded software.. for any industry.. aerospace (like Lockhead's SEAL Level X, Boeing , DDPMAS etc) , Medical, or Nuclear industries. I'd love to see a trivial example that shows all the steps and outputs. For example, assuming I document the process on how the code is generated, what constitutes proof that it's safe? Static Analysis? Code Coverage - Statement (Level C), Decision (Level B), MCDC (Level A)? Who defines the unit tests? I imagine there are differences between the industries.. FAA : DO-178X , DO 331 , ARP4754A , ED-12C FDA : 13485 , ISO14971 , IEC 62304 , SaMD and DOE : 414.1x, but what are the typical tools/software needed, and the typical document/artifacts in the various stages of the software life cycle? I saw a good video by CEMILAC Education Program "Airborne Software Development & Certification Process" and it's a bit overwhelming: Requirement Management - (IBM Ration) DOORS, JAMA, Xebrio, rmtoo florath , doorstop-dev / doorstop , reqview Static Source Code Analysis - Parasoft, PolySpace, CodeSonar, horusec , sonar cloud, veracode PREFast Dynamic Analysis / Modified Condition/Decision Coverage (MC/DC) - VectorCAST, RapiTest Configuration Management / Storage and Version Control System - Git, SourceSafe, Mercurial, MS TFS QA - Helix ALM (I)V&V / Test Automation - VectorCAST, LDRA Testbed , Mathworks Simulink DO Qualification Kit Continuous Integration / CD - Continuous Delivery/Deployment And what is the general attitude towards open source software (ex. FreeRTOS) and code-generation tools (ex. ST's Cube MX)? Also, how do CPLD and FPGAs fit in to the embedded software picture.. since not exactly software nor hardware, since they are programmable devices written in an programming language like VHDL , (system) verilog , Amaranth HDL ?
@AngeloTheBA
Ай бұрын
Scrum and SAFe are about how you develop, not what you develop. A waterfall team could develop the same thing as a SAFe or SCRUM team. It is not a "standard". The choice to use agile is more about the organizational culture, not any specific industry. You may find some aerospace organizations that embrace agile and some that don't (Google it). That is true for basically all the questions you asked. Open source might mean "easier to find people who understand how to develop on the platform" ... non-open source might mean you find people more specifically trained/certified on the platform which helps in hiring confidence. Some platforms might be better configured to recognize, administer, and facilitate following certain industry regulations or standards. Are you specifically hoping to go into these highly regulated industries?
@gregorrohde3146 Жыл бұрын
Thank you, this was very helpful. You SAFe'd me from misunderstanding. (B'dum tzzz!)
@AngeloTheBA
Жыл бұрын
😂
@tekperson7 ай бұрын
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.
@AngeloTheBA
7 ай бұрын
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.
@chezmaniac4912 Жыл бұрын
Bless .... really good video but SAFe is actually a framework as in the name and follows the Agile methodology. Same as Scrum.
@AngeloTheBA
Жыл бұрын
Cool, thanks
@AWayOfLiving843 ай бұрын
☯️🌏🕵🏻♂️♻️👣🌌
@BladBlad Жыл бұрын
scrum is a framework*
@AngeloTheBA
Жыл бұрын
Cool, thanks.
@RD-pz9sc2 ай бұрын
Wrong. SAFe breaks so many Agile/Scrum principles, for correct scaling check out LeSS (official Scaled Scrum framework).
@AngeloTheBA
2 ай бұрын
This video is to explain SAFe, not argue it's efficacy against LeSS. On that point, I don't believe this video is incorrect.
@RD-pz9sc
2 ай бұрын
@@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.
Пікірлер: 35
Short, clear and on point. Brilliant
Excellently delivered. Thank you!👌🤗
I like the way you explain it without too much technical jargons. :)
@AngeloTheBA
2 жыл бұрын
That's always the goal! If you understood all the jargon, then chances are you don't need the explanation.
This is amazingly explained. Thanks!
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 👍
@AngeloTheBA
Жыл бұрын
Thanks!
This is super helpful!
Thanks buddy, you're the man!. This is an awesome video.
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.
@AngeloTheBA
Жыл бұрын
I'm glad it was helpful to you
So crisp and neat 👍👌👏🙏
@AngeloTheBA
3 жыл бұрын
😁
Awesome video! Thank you!
Perfect and accurate
@AngeloTheBA
Жыл бұрын
Thanks.
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.
@AngeloTheBA
2 жыл бұрын
I'll keep that in mind for future videos.
@ggaccentc
2 ай бұрын
It was born from eXtreme Programming.
🔥🔥🔥
thanks
Are most big aerospace, medical and nuclear companies using Agile or Scrum? And how does it affect the software development process? I'd like to move away from the rapid-prototype style to a more formal environment.. perhaps not for FAA/FDA/DOE approval, but to develop high quality/safe products containing embedded software.. for any industry.. aerospace (like Lockhead's SEAL Level X, Boeing , DDPMAS etc) , Medical, or Nuclear industries. I'd love to see a trivial example that shows all the steps and outputs. For example, assuming I document the process on how the code is generated, what constitutes proof that it's safe? Static Analysis? Code Coverage - Statement (Level C), Decision (Level B), MCDC (Level A)? Who defines the unit tests? I imagine there are differences between the industries.. FAA : DO-178X , DO 331 , ARP4754A , ED-12C FDA : 13485 , ISO14971 , IEC 62304 , SaMD and DOE : 414.1x, but what are the typical tools/software needed, and the typical document/artifacts in the various stages of the software life cycle? I saw a good video by CEMILAC Education Program "Airborne Software Development & Certification Process" and it's a bit overwhelming: Requirement Management - (IBM Ration) DOORS, JAMA, Xebrio, rmtoo florath , doorstop-dev / doorstop , reqview Static Source Code Analysis - Parasoft, PolySpace, CodeSonar, horusec , sonar cloud, veracode PREFast Dynamic Analysis / Modified Condition/Decision Coverage (MC/DC) - VectorCAST, RapiTest Configuration Management / Storage and Version Control System - Git, SourceSafe, Mercurial, MS TFS QA - Helix ALM (I)V&V / Test Automation - VectorCAST, LDRA Testbed , Mathworks Simulink DO Qualification Kit Continuous Integration / CD - Continuous Delivery/Deployment And what is the general attitude towards open source software (ex. FreeRTOS) and code-generation tools (ex. ST's Cube MX)? Also, how do CPLD and FPGAs fit in to the embedded software picture.. since not exactly software nor hardware, since they are programmable devices written in an programming language like VHDL , (system) verilog , Amaranth HDL ?
@AngeloTheBA
Ай бұрын
Scrum and SAFe are about how you develop, not what you develop. A waterfall team could develop the same thing as a SAFe or SCRUM team. It is not a "standard". The choice to use agile is more about the organizational culture, not any specific industry. You may find some aerospace organizations that embrace agile and some that don't (Google it). That is true for basically all the questions you asked. Open source might mean "easier to find people who understand how to develop on the platform" ... non-open source might mean you find people more specifically trained/certified on the platform which helps in hiring confidence. Some platforms might be better configured to recognize, administer, and facilitate following certain industry regulations or standards. Are you specifically hoping to go into these highly regulated industries?
Thank you, this was very helpful. You SAFe'd me from misunderstanding. (B'dum tzzz!)
@AngeloTheBA
Жыл бұрын
😂
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.
@AngeloTheBA
7 ай бұрын
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.
Bless .... really good video but SAFe is actually a framework as in the name and follows the Agile methodology. Same as Scrum.
@AngeloTheBA
Жыл бұрын
Cool, thanks
☯️🌏🕵🏻♂️♻️👣🌌
scrum is a framework*
@AngeloTheBA
Жыл бұрын
Cool, thanks.
Wrong. SAFe breaks so many Agile/Scrum principles, for correct scaling check out LeSS (official Scaled Scrum framework).
@AngeloTheBA
2 ай бұрын
This video is to explain SAFe, not argue it's efficacy against LeSS. On that point, I don't believe this video is incorrect.
@RD-pz9sc
2 ай бұрын
@@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.