Timeline for Separate QA v.s. Scrum Team Member - How should QA be involved?
Current License: CC BY-SA 4.0
18 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 19, 2020 at 12:38 | history | edited | JAINAM | CC BY-SA 4.0 |
added 16 characters in body
|
Mar 14, 2017 at 11:09 | history | tweeted | twitter.com/StackSQA/status/841607315757400064 | ||
Mar 10, 2017 at 18:46 | comment | added | corsiKa♦ | Don't get me wrong - I want you to achieve success. But posts on Stack Exchange have to be a question. A request for feedback is definitely out of scope. Sharing experience to hope someone else has had the same experience is also out of scope. The question is quite broad as it stands. | |
Mar 10, 2017 at 9:34 | comment | added | Ragnarsson | @corsiKa, I'm sorry if it sounds like a rant to you. I just tried to ask a question with as much details as I could. Now if I could tell loads of details, it would be a rant ;), but of course I couldn't. Thing is, I wanted to share my experience, which is so different from my previous companies, to see if anyone has the same one so that I can learn one or two things to adapt myself to this new experience :) | |
Mar 10, 2017 at 6:56 | comment | added | Sebastiaan van den Broek | Your company may think they're doing scrum, but like many others, they're not. | |
Mar 9, 2017 at 23:14 | history | edited | Michael Durrant | CC BY-SA 3.0 |
edited title
|
Mar 9, 2017 at 21:49 | answer | added | mutt | timeline score: 3 | |
Mar 9, 2017 at 20:55 | answer | added | Phil Hannent | timeline score: 0 | |
Mar 9, 2017 at 19:17 | comment | added | corsiKa♦ | Forgive me, but this looks more of a rant than a question. The background will undoubtedly be useful for the eventual question, but as it stands I don't see one. | |
Mar 9, 2017 at 15:28 | comment | added | Peter M. - stands for Monica | Note to closing mafia: This question is not trivial to answer, but is obviously relevant to QA life, which makes it interesting. Upvoted. | |
Mar 9, 2017 at 13:26 | comment | added | George | Yes, i think question should be 'What will changes i propose actually improve?'. I think its company, product, team specific. No one wants to change things around 'just because', however if clear benefits can be seen, its a lot different. | |
Mar 9, 2017 at 12:46 | answer | added | Kate Paulk | timeline score: 8 | |
Mar 9, 2017 at 11:15 | review | Close votes | |||
Mar 9, 2017 at 12:29 | |||||
Mar 9, 2017 at 10:56 | comment | added | Bharat Mane♦ | It depends upon company to company; See In every Meetings and discussion there is no need to include QA team. But while Sprint planning at least single QA (QA lead) should be present so that he/she will drive his team as per the decided plan. | |
Mar 9, 2017 at 10:51 | answer | added | dvniel♦ | timeline score: 10 | |
Mar 9, 2017 at 10:50 | answer | added | Niels van Reijmersdal | timeline score: 5 | |
Mar 9, 2017 at 10:39 | comment | added | George | What do you think including QA in all those meetings will accomplish ? Who is the 'boss' of QA and why doesnt he fight about the testing process ? | |
Mar 9, 2017 at 10:14 | history | asked | Ragnarsson | CC BY-SA 3.0 |