on 04-07-2010 1:48 AM
We want to use only one project for all normal change requests(CR).
But some CRs are very quickly moved into the PRD while some others are slower.
Should we create 2 projects : one for fast moving corrections and another for slower ones?
Above is for normal corrections only. The shortcoming of above plan is that it hard to know the CR is going to be fast or not.
U r gent correction: We have a dedicated project for u r gent corrections which are usually moving very fast.
Could you tell us your practice on this?
Thanks and regards.
Hi,
Do you have a planned release strategy? For the CRs which are moving very quickly into Production, that means, they are moving off cycle, without waiting for all the normal corrections to be imported at a stretch. You can certainly create another project for such corrections.
Regards,
Sneha Vyas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See,its purely depends on your release stratergy. If you have a category of changes which moves to PRD very fast, say in a day itself, assign them to one one project. If required, you can create one for meduim fast one, and one for slow one also. And you dont really require a seperate project for u'gent correction. They are independent of your release strategy.
Rajeev
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.