SAFe Value Streams | Large Product or Solution SAFe Vs Portfolio SAFe Configuration Vs Full SAFe.
ฝัง
- เผยแพร่เมื่อ 1 ต.ค. 2024
- This video is about Scaled Agile Framework : Value Streams, Large Product or Solution, Portfolio Configuration and Full SAFe model. In this video, we will cover fundamental meaning of Value stream, difference between Large Product Vs Portfolio configuration Vs Full SAFe. Also we will talk about who are key players at each level and what is work hierarchy at each level.
Good summary with examples. Thank you. Only part that I found a bit unclear was examples of Large Solution / Portfolio / Full SAFe with Bharti and Airtel. I think the confusion was mainly with the terms 'portfolio / large solution' and 'value stream' used interchangeably.
thank you this is SAFe Agile 6.0 beautifully explained at every level
Pls post videos on PI planning
Where are you Sir ?
Paji last video ka link
This is Excellent Video and explanation Samrath. Looking forward to more on SAFe. After seeing this video absolutely no confusion at all on the 4 levels of Safe..Examples are too good. Keep it up . Thanks
@Training Horizons, awesome and simple explanation. Can you please give the link to your PI planning video?
Absolutely lovely ! Really liked Airtel example for understanding portfolio vs large solution. Thank You !!
Excellent Presentation ! Thank you so much ❤
very nice video. easy to understand with examples. will are looking for more videos in similar in nature. best of luck
From where I can find next videos. Very well explained.
I have been trying to understand this since long time. This is very well explained
Thank you
very good summary, thank for this helpful video
I am only able to find 3 videos. Please let me know if you have more. Thank you
Value stream.. misleading??
very informative video
You are doing really awesome. Good job
Very good explanation with relevant examples. Pls provide more videos
Sure I will
Very good information
Very informative...👍
Simply Perfect.
greaaaaat job
SAFe recommends 2 weeks sprints, why only 2 weeks, can i have 1 week sprint, also please share real example of epic, portfolio etc from your experience , it will help all, thanks
Hello Anil, We generally recommends 2weeks (min) and 4 weeks (max). 2 weeks is ideal. it is an iterative cycle you need to see the user story, develop/code, discuss with PO, peer review, configure environment, test, PO acceptance. The intent is get value which can consumed by consumer or product owner. 1 week is too short.
you can consider any product like a multi story building as epic. Within the building you have capabilities like Lift, AC, flooring, Networking etc. Now each capabilities can have features for example list have features of anti skid flooring, air supply, voice system, button to select floor, ample light, recovery backup etc .. Each feature can be split into user stories or tasks. For ample lighting, you need space to fit lights, get electricity connection, check illumination, switches etc. I hope it clarifies. you can apply same hierarchy to any software or product
@@traininghorizons269 thanks for response , then as asked in other vlog , SAFe cannot be applied for maintenance projects ie where there are multiple checkins daily or in days. Then SAfe is not agile, any thoughts?
@@traininghorizons269 thanks will wait for the next vlog on PI planning and how this will be addressed but of-course i the expectation was some software project which you have worked on (maybe in banking domain) , this example seems more of an example rather from a software project. Anyway thanks for sharing details
@jeyton thanks for your expert reply, i understand i can use kanban etc but looks like you are integrating your code every 2 weeks, is that agile?. Or they integrate daily so that any conflicts can be resolved ( within teams yes we do but should we not integrate across teams too on a daily basis). Merging can be hell if we do in 2 weeks and also cherry picking could not be an easy task. As we involve more and more teams , the branching strategy could become complex so what is the best way to achieve frequent integration and testing in SAFe, any thoughts?