Why use Lifecyle Projects?
We've been using Jazz (RTC, RQM, and RDNG) for a while now. We've implemented it using Lifecycle Projects with templates, etc. I see only 2 benefits of that:
1. automates creation of 3 project areas (RTC, RQM, and RDNG) (could be more than 3...) 2. automates their linking After the lifecycle project creates the children project areas, what benefit does it provide? Sure, you can go look at a list of them, but the list is so slow to load it is not useful. If you look at one lifecycle project, you can see the projects created from it or added to it. Is that it? Even in the new SAFe implementation in Jazz 6.0.1, the portfolio is a lifecycle project, what what benefit is there for the portfolio from the function of the lifecycle project, over what I've written already? The only benefit is in the project areas in the tools, that I can see. So, I'm just wondering - why bother? It's a small time-saver during creation, but does it do more? Thank you for any information you can provide, because I've been looking for more benefits and can't find them. |
Accepted answer
That's pretty much what you summed up. If you don't see the small benefits as benefits in your case, then don't use it - you don't have to.
https://jazz.net/forum/questions/92657/difference-between-lifecycle-project-area-and-standalone-project-area https://jazz.net/help-dev/clm/topic/com.ibm.jazz.platform.doc/topics/c_getting_started_project_areas_and_lifecycle_projects.html https://jazz.net/help-dev/clm/topic/com.ibm.jazz.platform.doc/topics/c_creating_managing_cross_application_projects.html Donna Thomas selected this answer as the correct answer
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.