NO SIT and only UAT
Can someone please guide me as to what precautions or points should I take as a participant team if the end to end team decides to only perform UAT and no SIT? The reason for this being that the requirement is very simple hence there is no need of UAT.
I think at the end there you mean "no need of SIT"?
Originally Posted by MedhaN
In waterfall / v-model testing it gets drilled into us so often that testing follows unit - system - user acceptance that we often forget that simplifying things for a quicker release is sometimes a good thing. So the first thing to say is that going straight into UAT is not uncommon for small changes even in a highly structured delivery, so don't worry about the procedural aspect of it. The second thing is that Agile sits business people in the development team for this reason, to get things released quicker, so it's certainly not uncommon in the wider SDLC.
For the release to be successful you'll need your business testers to be on board. If they're used to a formal unit - system - user acceptance cycle then they may fret initially at being given the testing straight from dev. If this is their/your first time doing this, then a quick onboarding and support from the delivery team before release would be beneficial. If this is a new way of working going forward in your deliveries (e.g. all changes less than x hours of work go straight to UAT, or something similar) then an hour or so presenting to them the process change and any related technical info (which system they will be testing in, how long each month they will be expected to test outside their day job, where to find test scripts if they are used, any knowledge transfer sessions for the changes, how to report successful testing, how to raise defects for unsuccessful testing, etc) would give them clarity.
Although they are "business" and not development, keep them in the loop on delivery times and knowledge transfer so they can plan their testing around their day jobs.