Folks, I need some kind of confirmation of the below facts r
Folks, I need some kind of confirmation of the below facts regarding RQM 2.0.0.2 Project process templates
Folks, I need some kind of confirmation of the below facts.
RQM 2.0.0.2 is the version.
From my experience with the tool I have seen that RQM allows you to select various available and custom (if created) process templates and create project areas. But what I have also seen is that if you want to add or remove a field for a project that has ALREADY been created you want to do it in the Project configuration rather than the process template of the process the project is base out of. If you change the process template the project is initially made out of this wont affect any changes in the actual project that is already related but will only take into effect for any new projects created on this changed template.
So basically if you have 10 projects already created using one default template lets say, to bring about a common change to the already created 10 projects you have to update the 10 project configurations individually. Can some one tell me if I am wrong and either ways pull some documented text that clarifies my dilemma? Some folks at y organization are anticipating they could standardize one process template for all projects and also update a field across all created projects at once
Folks, I need some kind of confirmation of the below facts.
RQM 2.0.0.2 is the version.
From my experience with the tool I have seen that RQM allows you to select various available and custom (if created) process templates and create project areas. But what I have also seen is that if you want to add or remove a field for a project that has ALREADY been created you want to do it in the Project configuration rather than the process template of the process the project is base out of. If you change the process template the project is initially made out of this wont affect any changes in the actual project that is already related but will only take into effect for any new projects created on this changed template.
So basically if you have 10 projects already created using one default template lets say, to bring about a common change to the already created 10 projects you have to update the 10 project configurations individually. Can some one tell me if I am wrong and either ways pull some documented text that clarifies my dilemma? Some folks at y organization are anticipating they could standardize one process template for all projects and also update a field across all created projects at once
Accepted answer
Folks, I need some kind of confirmation of the below facts regarding RQM 2.0.0.2 Project process templates
Folks, I need some kind of confirmation of the below facts.
RQM 2.0.0.2 is the version.
From my experience with the tool I have seen that RQM allows you to select various available and custom (if created) process templates and create project areas. But what I have also seen is that if you want to add or remove a field for a project that has ALREADY been created you want to do it in the Project configuration rather than the process template of the process the project is base out of. If you change the process template the project is initially made out of this wont affect any changes in the actual project that is already related but will only take into effect for any new projects created on this changed template.
So basically if you have 10 projects already created using one default template lets say, to bring about a common change to the already created 10 projects you have to update the 10 project configurations individually. Can some one tell me if I am wrong and either ways pull some documented text that clarifies my dilemma? Some folks at y organization are anticipating they could standardize one process template for all projects and also update a field across all created projects at once
Yes, this is correct. You have to update each project area.
In RQM 3.0.1, the Jazz Foundation has added support for sharing process between multiple project areas. This means that you can create one project area that has your process configuration and any number of other project areas which use (inherit) this configuration. By changing this single shared project area, the process of all child project areas will be updated.
- Jared