As a former SPC 5.1 and trainer my compliments on the great video! It's always nice to see motivated colleagues (working in knowledge transfer) at work!
I think the new core value of "Respect for People" is a good addition, since this is one area I think these days we are struggling with (as a society). I quite like the pentagon idea of yours too.
Agree. Program Execution I think matters more towards immature organizations, but Respect for People matters to everyone equally. As noted in the video, Program Execution is implied already...
Wow, what a dense amount of information explained clearly and concisely. Very well organized and you make this very accessible even for people who are aware of SAFe but may not have been practicing it directly. Well done!
I suspect SAFe is a money making game hiding inside the chameleon skin of change and improvement. Bottom line. The engine underneath SAFe is Scrum. Scrum takes User Stories and ensures that these are built in sprint. But does it? Unless tightly managed (Approved by PO Demo Deck + ability to get value out into live via DevOps / ITIL). All the stuff above this in SAFe, if the focus is on SAFe means that SAFe can make Scrum (Agile) unsafe.
Of course, SAFe is a for profit business. I suppose the question is whether you find any of the patterns, principles and guidance useful in reality, as most information is available for free. Thanks for sharing 😀.
If application A follows SAFe PI planning and application B follows waterfall. How should a Safe Product Manager work to get the delivery of both applications in same iteration release?
They are not really out of alignment. Scrum is simply rapid integration waterfall when you think about it. It's a matter of defining the dependencies and releases. Scrum, waterfall, etc. are execution models. What you care about as the PM is what gets delivered when, in what sequence, to ensure there are no missed dependencies.
Very good. Enjoyed this immensely. Thank you.
As a former SPC 5.1 and trainer my compliments on the great video! It's always nice to see motivated colleagues (working in knowledge transfer) at work!
Simply brilliant summary for my ears as SPC. I applaud your preparedness.
Thanks very much. Glad you found it useful.
T - Transparency
A - Alignment
R - Relentless Improvement (Includes quality)
R - Respect for people
I would go with ARRT (kind of sounds like ART) 🤔
Great stuff, really like that
Respect for people couldn't that be seen as "Friendliness", based on that you can figure out the acronyms by your self...
I think the new core value of "Respect for People" is a good addition, since this is one area I think these days we are struggling with (as a society). I quite like the pentagon idea of yours too.
Hi AirKevlon, I think you do make a valid point, thanks for sharing.
Agree. Program Execution I think matters more towards immature organizations, but Respect for People matters to everyone equally. As noted in the video, Program Execution is implied already...
Wow, what a dense amount of information explained clearly and concisely. Very well organized and you make this very accessible even for people who are aware of SAFe but may not have been practicing it directly. Well done!
Thanks a lot
Thanks for the comprehensive review! I enjoyed your sense of humor!
Glad you enjoyed it!
Thanks for making this fun to watch!
Glad you enjoyed it!
I suspect SAFe is a money making game hiding inside the chameleon skin of change and improvement. Bottom line. The engine underneath SAFe is Scrum. Scrum takes User Stories and ensures that these are built in sprint. But does it? Unless tightly managed (Approved by PO Demo Deck + ability to get value out into live via DevOps / ITIL). All the stuff above this in SAFe, if the focus is on SAFe means that SAFe can make Scrum (Agile) unsafe.
Of course, SAFe is a for profit business. I suppose the question is whether you find any of the patterns, principles and guidance useful in reality, as most information is available for free. Thanks for sharing 😀.
If application A follows SAFe PI planning and application B follows waterfall. How should a Safe Product Manager work to get the delivery of both applications in same iteration release?
They are not really out of alignment. Scrum is simply rapid integration waterfall when you think about it. It's a matter of defining the dependencies and releases. Scrum, waterfall, etc. are execution models. What you care about as the PM is what gets delivered when, in what sequence, to ensure there are no missed dependencies.
that's a nice video sir
Great explanations! You make it look effortless but it's absoltly not!
Thanks. You can do it!
Core values acronym TARR
I like to better then RRAT 😂
@@SAFeintheRealWorld ARRT sounds better (ART)