Sure I will

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?