UAT dilemma
-
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it :-) In Enhancement kind of project, we often encountered situation where more than one tasks are deployed and sent for UAT. And for some reason one or more task either rejected or put on hold. I am sure many of us may have encountered this situation. My question was: What is general practice? Do we go ahead to production with approved tasks? If yes, do we go through the whole cycle of Deploy to QA (after removing the rejected task), Functional testing and UAT? Or any other route? Any further guidance on right articles/discussions would help
Thanks, Milind
-
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it :-) In Enhancement kind of project, we often encountered situation where more than one tasks are deployed and sent for UAT. And for some reason one or more task either rejected or put on hold. I am sure many of us may have encountered this situation. My question was: What is general practice? Do we go ahead to production with approved tasks? If yes, do we go through the whole cycle of Deploy to QA (after removing the rejected task), Functional testing and UAT? Or any other route? Any further guidance on right articles/discussions would help
Thanks, Milind
IMO: This is the correct forum for this type questions. OK, so my answer is - It depends. - If this tasks are related to individual modules of a larger project, then Yes you should move the tasks/parts to production that are approved in the UAT environment (We have followed this same practice when we were customizing an Oracle ERP). i.e. if CRM Module is ready then we will push it and not wait for the HR Module to get approved. - But if the project is smaller and the modules are very tightly integrated. You should wait for every module for that particular Version number to get approved in the UAT. (We are currently following this practice for our cloud based software) i.e. If we are going to launch Version 1.5, everything related to 1.5 must be approved in the Test Environment. So again, it depends whether you are maintaining a single version for the application or separate version for separate modules/parts. Also one more thing I mostly do not follow "best practice", I just follow whatever is suitable for my current scenario. :)
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud
-
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it :-) In Enhancement kind of project, we often encountered situation where more than one tasks are deployed and sent for UAT. And for some reason one or more task either rejected or put on hold. I am sure many of us may have encountered this situation. My question was: What is general practice? Do we go ahead to production with approved tasks? If yes, do we go through the whole cycle of Deploy to QA (after removing the rejected task), Functional testing and UAT? Or any other route? Any further guidance on right articles/discussions would help
Thanks, Milind
MT_ wrote:
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it
Look where the Lounge wrath has brought us : now you have to write a disclaimer not to be flamed... :sigh: I miss the time when you simply could post in the wrong forum, and your post would be moved in minutes without anyone making a fuss about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
-
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it :-) In Enhancement kind of project, we often encountered situation where more than one tasks are deployed and sent for UAT. And for some reason one or more task either rejected or put on hold. I am sure many of us may have encountered this situation. My question was: What is general practice? Do we go ahead to production with approved tasks? If yes, do we go through the whole cycle of Deploy to QA (after removing the rejected task), Functional testing and UAT? Or any other route? Any further guidance on right articles/discussions would help
Thanks, Milind
UAT is done by user base NOT the the developers / delivery team. The question arises when a piece is pulled, for whatever reason from a build. If it is in isolated components and there are no other changes there, then it can be done simply by not including it. Sometimes the code goes in, but the function is hidden or disabled [done this more than once]. Once you've got your build, it should go through QA who should not just check that the deliverables are there and working but that the pulled changes are not accessible. The hard part for the delivery is then do you say anything about the pulled changes. If the code is delivered but disabled, I would have a note in the release document stating that changes have been made to component X, but these are not available and are waiting for the release of component/change Y. It is then the clients call if it should be part of UAT. Sign off of UAT is rarely without caveats for large systems. Another side of pulling is that the delivered component does not work. Can you patch before going to production or should you pull it. If it's pulled then we go back to the isolation issue. If you can, disable the function, if you can't then a rebuild or at least a patch is required to take it out. Never allow the client to hack a change, deliver it to them in an agreed format that they can apply.
-
MT_ wrote:
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it
Look where the Lounge wrath has brought us : now you have to write a disclaimer not to be flamed... :sigh: I miss the time when you simply could post in the wrong forum, and your post would be moved in minutes without anyone making a fuss about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
Those were the days. Not anymore. :)
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
MT_ wrote:
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it
Look where the Lounge wrath has brought us : now you have to write a disclaimer not to be flamed... :sigh: I miss the time when you simply could post in the wrong forum, and your post would be moved in minutes without anyone making a fuss about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
Rage wrote:
Look where the Lounge 'wrath' has brought us :
Rage wrote:
not to be 'flamed'...
I guess, I have seen this kind of disclaimer earlier in this week. This is the second instance. Even, The bunch of people in lounge is more than the specific subject of forum. I must say this is fine however somewhere somehow it may have gone very hard(wrath) to someone to get this kind of disclaimers popping each day.
You can have all the tools in the world but if you don't genuinely believe in yourself, it's useless.
-
Those were the days. Not anymore. :)
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
Those were the days. Not anymore. :)
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
When were those days? :doh:
Wrong is evil and must be defeated. - Jeff Ello[^]
-
IMO: This is the correct forum for this type questions. OK, so my answer is - It depends. - If this tasks are related to individual modules of a larger project, then Yes you should move the tasks/parts to production that are approved in the UAT environment (We have followed this same practice when we were customizing an Oracle ERP). i.e. if CRM Module is ready then we will push it and not wait for the HR Module to get approved. - But if the project is smaller and the modules are very tightly integrated. You should wait for every module for that particular Version number to get approved in the UAT. (We are currently following this practice for our cloud based software) i.e. If we are going to launch Version 1.5, everything related to 1.5 must be approved in the Test Environment. So again, it depends whether you are maintaining a single version for the application or separate version for separate modules/parts. Also one more thing I mostly do not follow "best practice", I just follow whatever is suitable for my current scenario. :)
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud
Thanks Rutvik. I am leading both project and support group and we encounter this scenario quite often. So, We have staging code-base which is in sync with staging version control and then we are forced to go live sans one task :-( . Sometimes the code is from different component and sometimes from one service for example and we are in fix. Normally, we try to hold back the release but at times we have to bow to customer's wish and re-build/re-test hastily and VSS 2005 is not very supportive in such case.
Thanks, Milind
-
MT_ wrote:
This is not Programming question. Though wasn't sure which forum to asks this question. Tried Google too, but probably couldn't formulate search keywords correctly and couldn't find anything in particular. If this forum is not appropriate, I would appreciate if someone can direct to right forum rather than having a go on it
Look where the Lounge wrath has brought us : now you have to write a disclaimer not to be flamed... :sigh: I miss the time when you simply could post in the wrong forum, and your post would be moved in minutes without anyone making a fuss about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
You got me exactly right ! I have been observer of lounge for more than a year and reads many threads if not all. I have seen people getting offended on trivial stuff, having a go on newbie and defaulters (to the unwritten rules set in). It tool quite a while to form the sentence above to make sure I am not at the receiving end. Thanks once again and hope the patience and tolerance level restores :-)
Thanks, Milind
-
UAT is done by user base NOT the the developers / delivery team. The question arises when a piece is pulled, for whatever reason from a build. If it is in isolated components and there are no other changes there, then it can be done simply by not including it. Sometimes the code goes in, but the function is hidden or disabled [done this more than once]. Once you've got your build, it should go through QA who should not just check that the deliverables are there and working but that the pulled changes are not accessible. The hard part for the delivery is then do you say anything about the pulled changes. If the code is delivered but disabled, I would have a note in the release document stating that changes have been made to component X, but these are not available and are waiting for the release of component/change Y. It is then the clients call if it should be part of UAT. Sign off of UAT is rarely without caveats for large systems. Another side of pulling is that the delivered component does not work. Can you patch before going to production or should you pull it. If it's pulled then we go back to the isolation issue. If you can, disable the function, if you can't then a rebuild or at least a patch is required to take it out. Never allow the client to hack a change, deliver it to them in an agreed format that they can apply.
Thanks for the response Nagy. I have just replied back to Rutvik above. At times, the push is heavy and we scramble around hastily to comment/pin the pervious version, rebuild, deploy and test.. Just wanted to know how others handle this situation.
Thanks, Milind
-
UAT is done by user base NOT the the developers / delivery team. The question arises when a piece is pulled, for whatever reason from a build. If it is in isolated components and there are no other changes there, then it can be done simply by not including it. Sometimes the code goes in, but the function is hidden or disabled [done this more than once]. Once you've got your build, it should go through QA who should not just check that the deliverables are there and working but that the pulled changes are not accessible. The hard part for the delivery is then do you say anything about the pulled changes. If the code is delivered but disabled, I would have a note in the release document stating that changes have been made to component X, but these are not available and are waiting for the release of component/change Y. It is then the clients call if it should be part of UAT. Sign off of UAT is rarely without caveats for large systems. Another side of pulling is that the delivered component does not work. Can you patch before going to production or should you pull it. If it's pulled then we go back to the isolation issue. If you can, disable the function, if you can't then a rebuild or at least a patch is required to take it out. Never allow the client to hack a change, deliver it to them in an agreed format that they can apply.
Nagy Vilmos wrote:
UAT is done by user base NOT the the developers / delivery team.
That assumes that developers and delivery team are not part of the user base. In many case, they are an integral part of the user base.
-
Nagy Vilmos wrote:
UAT is done by user base NOT the the developers / delivery team.
That assumes that developers and delivery team are not part of the user base. In many case, they are an integral part of the user base.
You are confusing the logical with the physical. UAT, as the name suggests, must be done by users. When the dev is the user, then he gets to where two hats.
-
You are confusing the logical with the physical. UAT, as the name suggests, must be done by users. When the dev is the user, then he gets to where two hats.
I'm not confusing anything. Your statement was: UAT is done by user base NOT the the developers / delivery team. I merely pointed out that developers CAN be users; they are not mutually exclusive.
-
When were those days? :doh:
Wrong is evil and must be defeated. - Jeff Ello[^]
-
2002 -> 2005. There were no Lounge rules back then.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
Ok, I arrived in 2006, and the forum police was doing fine already then. Then the voting came and a lot of people complained. I didn't notice a real difference. Then the reporting came. Ok, no big problem. Then the downvoting disappeared and I noticed a rise in reports. :|
Wrong is evil and must be defeated. - Jeff Ello[^]