Thank you for the series with Bank example. I have few questions and appreciate your thoughts/inputs: 1. Strategic Theme to Solution Vision to Solution Roadmap Stage / Pre-EPIC: While SAFe encourages collaboration across roles, would you please shed some light on which roles are accountable/contributes/informed for those artifacts/stages in your view/what matured org's do. Epic Owner vs Enterprise Architect within Portfolio; Solution Management vs Solution Architect for Large Solution, Product Manager vs System Architect, etc. Let's keep LPM, RTE & STE roles aside for now. 2. I noticed that there are no Capabilities in your example and the discussion was around Epic & Features. Is the assumption that the Portfolio-level is implemented, and the features are directly linked to Epics without Capabilities? If that's the case, would each Epic have Solution Vision & Solution Intent details/artifacts maintained for DVS/Agile Teams to consume? 3. If an Organization matures to FULL-Level, is it common to have both portfolio & large solution-levels adopted within single portfolio? Epic to Features (Portfolio-level feeding to DVS's for "Not Complex" Epics) & Epic to Capability to Features (Portfolio-level feeding to Large Solution-Level to DVS's for "Very Complex" Epics)? Or will it be either or? (Portfolio-1 following Portfolio-level & Portfolio-2 following Large Solution-level always)
It may need larger discussion and I explain at level, hopefully it works 1. Epic Owner is not a dedicated role in SAFe, so all your listed roles can be epic owner, Solution Vision is maintained by Product Manager , SAFe PO-PM class gets into more details 2. Yes in example, we are not considering Large Solution, and Solution Vision can include multiple Epics, not just single. 3. This all depend on context, even org has full SAFe but it is not necessary that each ART has large solution so some ARTs will directly disaggregate epic into features
Hi Saket sir.. thanks again for this wonderful series to explain how exactly things move. I have few queries: 1) for epic hypothesis testing or MVP testing..what is the desired timeframe kept like here we need atleast 1-2 months data to tell what student loan page is viable 2) is the ART team already be established at Epic Hypothesis phase as even to test the hypothesis, MVP needs to be built and we need ART team. Now if ART team is built and MVP is launched and wait time is let's say 2 months...what does the ART team do in this wait period?
Thank you for checking the video, here I try to explain. Yes it can take time may be month or more in some cases even 3 months, ARTs are not created for Epic, ART are more on business like, so its possible an existing ART may allocate 10% of their capacity to new Epic MVP This video on Epic Kanban May help to understand the flow: th-cam.com/video/gVXVK9ifyRA/w-d-xo.html
enjoyed this series with a live example. Thank you for this valuable information
Glad you liked it!
Saket, you have incredible talent to breakdown concepts in very simpler way. Great job👌
Thank you
Thank you for the series with Bank example. I have few questions and appreciate your thoughts/inputs:
1. Strategic Theme to Solution Vision to Solution Roadmap Stage / Pre-EPIC: While SAFe encourages collaboration across roles, would you please shed some light on which roles are accountable/contributes/informed for those artifacts/stages in your view/what matured org's do. Epic Owner vs Enterprise Architect within Portfolio; Solution Management vs Solution Architect for Large Solution, Product Manager vs System Architect, etc. Let's keep LPM, RTE & STE roles aside for now.
2. I noticed that there are no Capabilities in your example and the discussion was around Epic & Features. Is the assumption that the Portfolio-level is implemented, and the features are directly linked to Epics without Capabilities? If that's the case, would each Epic have Solution Vision & Solution Intent details/artifacts maintained for DVS/Agile Teams to consume?
3. If an Organization matures to FULL-Level, is it common to have both portfolio & large solution-levels adopted within single portfolio? Epic to Features (Portfolio-level feeding to DVS's for "Not Complex" Epics) & Epic to Capability to Features (Portfolio-level feeding to Large Solution-Level to DVS's for "Very Complex" Epics)? Or will it be either or? (Portfolio-1 following Portfolio-level & Portfolio-2 following Large Solution-level always)
It may need larger discussion and I explain at level, hopefully it works
1. Epic Owner is not a dedicated role in SAFe, so all your listed roles can be epic owner, Solution Vision is maintained by Product Manager , SAFe PO-PM class gets into more details
2. Yes in example, we are not considering Large Solution, and Solution Vision can include multiple Epics, not just single.
3. This all depend on context, even org has full SAFe but it is not necessary that each ART has large solution so some ARTs will directly disaggregate epic into features
Excellent
Thank you so much 😀
Hi Saket sir.. thanks again for this wonderful series to explain how exactly things move. I have few queries:
1) for epic hypothesis testing or MVP testing..what is the desired timeframe kept like here we need atleast 1-2 months data to tell what student loan page is viable
2) is the ART team already be established at Epic Hypothesis phase as even to test the hypothesis, MVP needs to be built and we need ART team. Now if ART team is built and MVP is launched and wait time is let's say 2 months...what does the ART team do in this wait period?
Thank you for checking the video, here I try to explain.
Yes it can take time may be month or more in some cases even 3 months, ARTs are not created for Epic, ART are more on business like, so its possible an existing ART may allocate 10% of their capacity to new Epic MVP
This video on Epic Kanban May help to understand the flow:
th-cam.com/video/gVXVK9ifyRA/w-d-xo.html