Deployment Planning: Waterfall?
Hello,
We have a couple of "decade-old" groups who require baby steps to migrate to RTC. They use a "waterfall" type process. Has anyone bothered migrating their waterfall to RTC or was it easier to implement one of the available processes. We (support) see some similarities on their process and OpenUp, but we would like to know from the experienced. thanks... |
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 12 '09, 1:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd need to know the details of their "waterfall" model to say anything
specific, but in general, you can usually use an agile process for a waterfall team ... they just have fewer/longer iterations. Cheers, Geoff itengtools wrote: Hello, |
|
Well,
We have the typical phases of waterfall: Requirements(R) -> Design(D) -> Implementation(I) -> Verification(V) -> Maintenance(M) We have 4 "gates" MPR1->MPR4 which have certain criteria (no 1-Critical records after MPR3. I "guess" I could just use MPRs "gates" as just dates.) Parallel development of Releases. The "iterations" are "features" which go (R)->(V) which build upon until the main release. Releases are about 18months. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 14 '09, 11:03 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A few questions:
Does each feature use the same dates for when it transitions from R->D, D->I, and I->V, or does each feature have its own custom timeline for these transitions? Do the MPR1, MPR2, MPR3, and MPR4 gates occur during Implementation, or are they the gates that define the required conditions for transitioning from R->D, D->I, I->V, and then V->M? I assume there is a "release" at the end of the Verification phase? Cheers, Geoff itengtools wrote: Well, |
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.