While there is an ever increasing movement for Quality Engineering organizations to “Shift Left” there needs to be more attention placed on “Shift Right”. Here are some reasons why Quality Engineering must pay close attention:
- This is especially needed in more traditional industries where there are smaller and smaller UAT teams. There is increasing pressure on the UAT teams to test more and more with fewer and fewer resources.
- UAT resources usually have full-time demanding business jobs. UAT is typically given very little attention and focus. If there is a priority, UAT usually loses.
- Quality Engineering has access to software testing tools that can be extensively leveraged to accelerate the testing process.
- Quality Engineering should work closely with UAT to understand how the business works and create scenarios based upon day in the life scenarios. Those scenarios can then be automated and will greatly improve the quality of the applications before they hit UAT.
- While more and more demands are placed on Quality Engineering organizations, they usually are dedicated resources who can focus all their efforts on software quality.
- I agree that it is necessary to “Shift Left” but I believe you should actually start by “Shifting Right” in order to cover the backside of the SDLC.
- Agile will place greater demands and significantly compress the historically long UAT cycles, the time that used to be available will no longer be available.
- “Shift Right” will require interaction with UAT teams. This is often difficult for QE to interact and understand how the business really works. Let’s face it, we are geeks. Once QE has engaged and understood the real world challenges that the business faces, they will be able to identify potential issues before testing gets to UAT.
While this is not an exhaustive list, it will help support the thought that “Shift Right” first is the right way to go.