EAP+CWM / only CWM - how do you support both scenarios

[Tom Sienkiewicz]

Hi,

I'm curious if anyone is using both of above scenarios in their setup of new Agile products and can share some "gotchas" or things to consider.

We have a requirement where most people will only use CWM, and only selected few teams would be using EAP+CWM.

If you've already gone through a similar setup, would be great if you could share your take on the below:

- How to identify "EAP+CWM" or "CWM only" path if the process starts from Demand or Product Idea. My current concept involves checking the affected Business Apps or assigned Groups to identify for which EAP would be used. E.g. there is "Create EAP Epic" UI Action on Demand - should this be used only for EAP scenario or for both etc.

- Showing "EAP Team" and "EAP Config" fields on records like Demand, Epic, Story etc. - what drives this, I'm thinking to again make this dependent on Assignment Group, if it has EAP Team configured, show those fields, if not, hide

- Methodology (Scrum/SAFe) on Epic - when to pick which one, should this be manual or automated. My idea is to automate/use Scrum for CWM path and SAFe for EAP path (considering "full" EAP Config of 4 levels)

- Story-level fields/settings - is there anything to be aware of to avoid issues down the line. As an example, I noticed that recent CWM release added "CWM Epic" reference on Story, this is synchronized to "Parent Work Item" - I believe first one should be used in CWM scenario and other one in EAP scenario?

- Should EAP team use CWM as story-level solution (linked in EAP config) or stay with only EAP for story-level, any pros/cons for either option?

If anyone has some useful remarks/tips or warnings form experience, or can point me to some resources discussing similar setup, highly appreciated.

Thanks!

Tom