Can we use ARIS for creating Project based Glossary?

Hi Deepti

You can use the ARIS Technical Terms model for capturing the glossary of terms. There are a number of different relationships that you can map between the technical terms that would establish the taxonomy.

Rob

Thanx Rob, I will work and this and update you if it worked for me. I was wondering have you done something like his in the past. Would you share it with me?

I have done things like that, but unfortunately I don't have copies. Maybe someone else on the community has some examples?

Rob

Hey Rob,

I had posted this query today, but didn't get any reply. Need your help.

Project Management Life Cycle is widely used in many companies. It covers 4 major steps: Initiation, Planning, Execution & Closure. What could be better than the Project Management Team driving the ARIS initiative through PMLC!! This is where i need your help.

How can we involve the Project Management team to drive the initiative of ARIS. How do we make them our evangelists. How can ARIS be used in every phase and WHY?

I hope you get my point. If a certain project has to be deployed using ARIS,  what are the things a Project Managers needs to drive to the team?

Regards,

Deepti Lad

Deepti,

We've used ARIS in the context of a large ERP rollout. The best way to get the PMO on your side is to cater to all their operational needs (reporting - e.g. risk mgmt, schedule tracking etc). There are many project management model types in ARIS that can be used. So referring to your 4 step process this will usually overlap between all four of them. Usually projects use a range of tools to fit their needs, if you can deliver on their requirements within ARIS. You've won half the battle.

In addition to this, we used ARIS to map out our business processes in a manner that assisted the functional teams report and identify integration points between modules. Integrations mapping and analysis is by far the most critical compontent of an ERP project. Integration testing usually reveals gaps in this, however by the time you get to the testing phase its too late and teams rush to fill gaps. By using ARIS to map integrations, these gaps can be addressed during design meetings rather than testing. Facilitating this in a timely and efficient manner using ARIS definitely won the ARIS team some brownie points. Identifying customisation (RICEFW) and its impact on processes was also a crucial part of the part. To cater to this, we defined custome attributes and objects to track customisations that impacted the process.  So referring to your 4 step process this will usually overlap between planning and execution phases.

In my humble opinon, to get the PMO and the project functional team onboard its best to firstly gather their requirements (just one pass at requirements gathering should suffice for demo) and research through the tool to see how you can meet those. 

I hope this helped.

Cheers

Ganesh