Post by account_disabled on Dec 7, 2023 9:35:23 GMT
In the Scrum framework the software tester does not wait until the end of development work with tests but cooperates with other members of the development team during specific iterations i.e. Sprints. This allows you to verify the work of the development team at every stageof product creation. Additionally in a Sprint limiting the tester's role to testing a given functionality after its development would mean not using its full potential and wasting his time between subsequent implementations.
The role of a tester in Scrum myths There are many myths surrounding the role of a tester in a scrum team. The most common one is that the role of a tester is unnecessary because each member of the development team already has all the necessary competences to create fullfledged functionality. This belief may result from a misinterpretation of the definition contained in the Scrum Guide which defines a development team as multitasking and having all the competencies necessary to create an Email Marketing List Increment but does not specify the competencies of individual team members. In Scrum everyone is a Developer i.e. a person cocreating the product. Therefore the software tester should take an active part in the team's work during the Sprint and be involved during meetings.
The role of a tester in Scrum is not only testing but also ensuring the quality of the resulting product and its creation process are maintained for example by improving the Product Backlog which I discuss in more detail later in the article. Another myth in my opinion harmful is that in agile processes such as Scrum there is no place for nonautomatic tests. In Scrum each Sprint is different so flexibility is necessary in the context of planning execution and analysis of tests and their results.
The role of a tester in Scrum myths There are many myths surrounding the role of a tester in a scrum team. The most common one is that the role of a tester is unnecessary because each member of the development team already has all the necessary competences to create fullfledged functionality. This belief may result from a misinterpretation of the definition contained in the Scrum Guide which defines a development team as multitasking and having all the competencies necessary to create an Email Marketing List Increment but does not specify the competencies of individual team members. In Scrum everyone is a Developer i.e. a person cocreating the product. Therefore the software tester should take an active part in the team's work during the Sprint and be involved during meetings.
The role of a tester in Scrum is not only testing but also ensuring the quality of the resulting product and its creation process are maintained for example by improving the Product Backlog which I discuss in more detail later in the article. Another myth in my opinion harmful is that in agile processes such as Scrum there is no place for nonautomatic tests. In Scrum each Sprint is different so flexibility is necessary in the context of planning execution and analysis of tests and their results.