Tonight we had Marcus Merrell for an Ask Me Anything about âShift Left, Shift Rightâ.
Itâs a topic Iâve seen discussed a lot but never delved very deep into it during my testing career. If we didnât get to your question or youâre catching up on the Dojo and have thought of questions youâd like to ask Marcus, please share them here.
Equally, if youâd like to continue the discussions from the chat, why not do so here?
Shift right can be used to improve testing process. Can shift left exist without shift right?
I think it can, for sure. What youâll end up with will be respectable: youâll be efficient at your testing, youâll have the developers involved, youâll release with confidence, and youâll probably achieve some measure of stability. It can be rewarding enough in and of itself.
What âshifting rightâ gives you is âwisdomâ: are you testing the right thing? Are you spending too much energy on things the users donât care about? Are you testing your software the way your users test it? Are there some insights you can gain by taking the post-release analytics traffic into account?
Shift left can exist without shift right, but in my opinion youâll be left with a missing puzzle piece: one that you may not even realize has been missing until you inquire about it.
Shifting right gives you a virtual guarantee that your testing is guided by what the business (i.e. the CEO) cares about.
Hi all, Really enjoyed this Ask Me Anything. It was so informative, especially regarding what shift right is (turns out I didnât really know what it was before). Iâve already arranged a meeting next week with my colleagues where we will discuss these ideas.
I recall you mentioning that different people/disciplines might be required for shift right compared to shift left. Who would you go to to get the different information required to shift right? And how would that information be used?