I suspect as it’s a relatively new phrase ( although non concept), many don’t thibk of it in these terms, but I know penty of testers/QAs that push for a seat at the table in early discussions on new solution developments and technology purchases. This us one of the steps that eables them to learn/develop the skills to see the bigger picture.
Knowing what is driving the need for change helps us see the problem that us being solved.
Yes, or maybe they do analyze holistically. But do not know it is called as such. For those folks who have difficulty understanding Gerald Weinberg’s book an “Introduction to General Systems on Thinking” as a first timer, should actually start with Donella Meadows’An Introduction to Systems Thinking. General Systems Thinking has many uses other than just Software Testing.
Side note to self, as I cannot go back and edit, and can’t believe how many errors are in my response. Do not use my phone to answer in The Club. The pedant in me cannot walk on by. Am sure you all understand.
I might have heard this topic before but haven’t explored this ever. And after searching this topic online I found list of articles and websites on it, specifically some website completely dedicated to it for e.g.
My testing has always been based in systems thinking but also systems theory, I feel like systems thinking doesn’t necessarily give you the richness that thinking and theory give you together. This is mainly because my degree was Systems Analysis (BA)!
Google AI gives the following when asked the relationship between the two:
“Systems thinking is the act of analysing and understanding complex systems by considering the interconnectedness of its parts, while systems theory is the body of knowledge that explains how systems function and interact, providing the foundation for systems thinking to be applied in various situations.”
So worth considering Systems Theory if you want to dive into Systems Thinking.
Systems Theory gives you ideas like:
Every system has boundaries and the boundaries are essentially where you choose to draw them
The Boundaries offer an insight into what interacts with you system. Inputs, Outputs and influences
Almost every system is more than just the sum of it’s parts; an aeroplane isn’t just a load of metal, plastic, etc. it flies! Systems Theory calls this Emergent Properties
Once you get the hang of defining what a system is you can then see how your system is more than a software programme or app, the users are part of the systems, the support team are part of the system, etc.
You can also ask questions like what would the worst version of my system be like, what properties would it have? e.g. an app that crashes when you submit data and loses it all, emergent property no-one tries again and they tell their friends not to bother.
Am looking forward to seeing what everyone thinks about Systems Thinking!
What is a great system for bringing testing professionals together and helping them grow? Probably MoT . . .