T-ShapeState of mind
Although they are specialists in their team, they must be able to match the skills of other team members in simple actions
The term "T-Shape" visually describes the competences expected on a T-Shape profile [van Veenendaal 2020] :
- The vertical bar of the T represents the expertise of the person who has a level of competence that allows him or her to get to the bottom of the issue
- The horizontal bar of the T represents all the other competences that a team needs to function, which is expressed by the width of this bar; at the same time, this bar also indicates that all these other competences have a low level.
Thus, in a team with T-Shapes, each member is capable of performing simple tasks. This diversity of skills allows each team member to collaborate fully on each activity, as long as it remains simple.
In a Scrum team, the plurality of skills is very important in order to facilitate the collaborative value ("[...] before contractual negotiation") of the agile manifesto [Beck 2001]. This diversity is even more critical when it comes to a DevOps team where Ops issues are adopted by Devs [Beyer 2016].
Finally, it should be noted that this mindset grows with the increasing maturity of the team and encourages both the decentralisation of leadership and the confidence that the organisation can have in such a team as it becomes able to organise itself around value.
Application to test maturity
Some teams do not have professional testers and in a "3 Amigos" workshop, the T-Shape mindset ensures at least the endorsement of the tester role.
In addition, it also allows the team to :
- take responsibility for the quality of the product [Moustier 2019-1] because the writing of tests and their execution remains possible, even without a tester
- to facilitate the transparency that is particularly sought after with Scrum [Schwaber 2020].
Agilitest's position on this practice
Agilitest offers a test automation platform in #nocode [Forsyth 2021], which requires very few technical skills and thus allows for a very rapid learning curve.
The scripts are purposely loop-free to avoid algorithmic errors and endless loops. Furthermore, the tool encapsulates all the technological difficulties by deploying all the required components to run tests on all technologies, including mobility.
To discover the whole set of practices, click here.
To go further
- [Beck 2001] : Kent Beck et al. - « Manifeste pour le développement Agile de logiciels » - 2001 - http://agilemanifesto.org/iso/fr/manifesto.html
- [Beyer 2016] : Betsy Beyer, Chris Jones, Jennifer Petoff et Niall Richard Murphy - « Site Reliability Engineering: How Google Runs Production Systems » - O’Reilly Media - 2016 - ISBN-13 : 978-1491929124 - https://landing.google.com/sre/sre-book/toc/index.html
- [Forsyth 2021] : Alexander Forsyth – JAN 2021 - « Low-Code and No-Code: What’s the Difference and When to Use What? » - https://www.outsystems.com/blog/posts/low-code-vs-no-code/
- [Moustier 2019-1] : Christophe Moustier – JUN 2019 – « Le test en mode agile » - ISBN 978-2-409-01943-2
- [Schwaber 2020] : Ken Schwaber et Jeff Sutherland - « Le Guide Définitif de Scrum : Les Règles de Jeu » - NOV 2020 - https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-French.pdf
- [van Veenendaal 2020] : Erik van Veenendaal - « The T-Shaped Tester » - Quality matters #10 - MAR 2020 - et http://www.erikvanveenendaal.nl/site/wp-content/uploads/T-shaped-tester-QM10.pdfhttp://www.erikvanveenendaal.nl/site/wp-content/uploads/Erik-van-Veenendaal-The-T-Shaped-Tester-eBook-2.pdf