Try to get rid of the unnecessary and constantly optimise by innovating on methods
Scarcity of resources tends to generate deleterious situations, especially if these situations are not managed, especially when time is short.
The feeling of deprivation thus diverts our cognitive capacity from urgent things to things that are certainly important but less essential [Deloitte 2016].
Conversely, the overflow of available resources, if poorly controlled, leads to misuse of resources and induces waste and neglect [Morgan 2015].
It turns out that deprivation of resources is actually a source of innovation [Neren 2011] and the mindset in which deprivation or abundance of available resources makes all the difference with a few tricks like [Castrillon 2020] :
It is in this state of mind that a team will be able to innovate with fewer resources.
We find the desire for fewer things to be done as proposed by the LeSS agile framework by proclaiming "More with LeSS" as the subtitle of one of its books [Larman 2016] and by putting this principle at the heart of the framework, notably by avoiding the proliferation [LeSS 2021] of :
To which we can also add, for example :
When there is less to manage, deprivation then changes into a context of controlled abundance with its benefits such as [Andersen 2017] :
A large pool of tests can be reassuring and even a source of pride. But when it comes to updating this asset following a major change in the domain, the amount of work can become greater. This introduces technical debt into the backlog [Moustier 2020] and is thus a brake on the product delivery cycle.
To achieve this, it is necessary to :
One can also, for example :
○ preventing bugs from appearing rather than looking for them
○ understanding what to test rather than checking functionality
○ designing a better system rather than trying to break it
○ unit tests
○ code production
○ knowledge sharing
○ on-the-fly code review
○ obtain better quality code than if it were developed alone
○ improve the "First Pass Yield"
Thus, the knowledge of lean, agile and testing practices allows us to find and even imagine ways to do more with less work.
As a tool for automating scripted tests, agility allows for executable specifications if the organisation decides to practice ATDD.
Furthermore, Agilitest is part of the "more with less" practice as the tool uses a #nocode approach [Forsyth 2021]. The lack of possibility of algorithms seems at first sight, especially for developers, to be a limitation, especially on the desire to make a script generic.
This is actually an advantage because the generation of scripts is then direct. Thus, there is less chance of introducing false positives into the possibilities of the script.