PE
Hi folks... our bank wide program is working in multiple projects and each of the projects is modelling processes in ARIS. It is absolutely normal that some processes from Project A are the same in Project B. But due to silo thinking and totally different team setups, Project B is not aware that Project A already has a similar process to piggy back onto.
How do you make people aware that there is already a process doing similar things? In case you identify a process as a candidate for being used across different projects - do you keep them where they are (project group) and flag them with an attribute or do you move them into another group which is a pool for cross project processes?
Secondly, let's say you find a process in Project A which you from Project B would like to leverage. But any Business Analysts, Stakeholders etc. have no clue that they have to look into Project A groups. Can you place a link in your Project B group which points to Project A so that your own documentation is complete? (I do not want to make copies - I'd prefer a Windows file system approach where you can simply create a link to another file.)
Thanks in advance
Peter
