Timeline for Separate QA v.s. Scrum Team Member - How should QA be involved?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2020 at 12:38 | history | edited | JAINAM | CC BY-SA 4.0 |
deleted 1 character in body
|
| Mar 10, 2017 at 17:48 | comment | added | Kate Paulk | @LouisT - it took me well over a year of doing this to convince my managers that they really did need to involve me earlier - I had to cause multiple big projects to be reworked before my managers really got that I had more skills than just checking things off boxes: a LOT of managers have the idea that testing is not a skilled career path, and they are usually the ones who don't see why testers should be involved early in the project life cycle. | |
| Mar 10, 2017 at 9:42 | comment | added | Ragnarsson | Thanks Kate, for the advice. I have actually tried above advice, even talked to CTO, but ... I don't know, the situation is strange here, this is all I could say. It is like, the upper management lets feedback from the teams (not only QA team) unheard and unnoticed. We can just keep trying to make things better, in some way :) | |
| Mar 9, 2017 at 15:58 | comment | added | jruberto | this is good advice. In summary, find ways to deliver value early and the PO/team will start to value QA. | |
| Mar 9, 2017 at 12:46 | history | answered | Kate Paulk | CC BY-SA 3.0 |