I have heard that overlapping of Phases are not allowed in RUP,PLS Could any one tell me where can I get a evidence for this in any of the Rational Site where it states explicitly that Phases In RUP cannot Overlap. Rgds Deepak
Why would you *want* them to overlap? In my understanding, the phases just indicate the rough ratio of activities in an interation. It's not the case that some activities must not be done in some phases. So it really doesn't matter that much wether an iteration is said to be at the end of a phase, or at the beginning of the next phase, does it?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
RUP can read like pure phases - finish design, start coding, finish coding, start testing. But read deeper and the Lump Chart clearly shows activities ramping up and down with overlap, even on a fairly waterfall-ish project. Iterative development repeats activities like design, test, code in each iteration. An Iteration Plan may show some overlap. Test first coding does design, test, code pretty much all at once. "phases" may not be a real useful concept in the bulk of the project life cycle. Inception or pre-sales is still pretty distinct in my world, but the rest can get thoroughly mixed up.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by Ilja Preuss: Why would you *want* them to overlap?
I think that the underlying assumption is that RUP rather than XP processes are being used. In this case towards the end of an iteration the testers run the system tests and then the user performs the UAT tests. The outcome of the UAT tests are used to develop the iteration plan for the next iteration.
What this could potentially mean is that developers are idly twiddling their thumbs waiting for test, UAT and the iteration plan for the next iteration (potentially they could also be waiting for the requirements phase for this iteration to be complete). This would be the justification for 'overlapping' the phases in any iterative processes.
The only way that I know of to combat this is to have the developers involved in all phases of the project, instead of having requirements specialists, design specialists, etc. as it is very hard to coordinate what people can do whilst they are waiting for "their" phase to start in one project.
I know automated testing can reduce the test & UAT phases, but in my experience you will always have some time delay as the user tests the last iteration. The only other way is to tackle this delay is to consider an iteration 'complete' when it has been passed to the user for UAT, and start planning the next iteration immediately. This means not including any feedback from the UAT until 2 iterations after the code they are acceptance testing.
These are just ideas as they come to my head. Do you guys have any other suggestions?
Have the XPers ever encountered any lag like this between iterations? Are there ways to overcome this gap?
Throw some outsourcing related execution to the project; all the processes will go haywhire. The people on the other side of the pond will know about UML, RUP etc; they have no freaking clue about Test driven development, agile approach etc.