Dear Community, especially those who LOVE testing!
We currently don't have the role of Quality Assurance filled and so - as a project manager, who is not a classic Software guy - I struggle with governing the testing myself.
Our company is still really young and testing isn't quite mature. Lots of testing is going, lots of good software and solutions are being produce, issues in current apps resolved, etc. however NONE of it is documented :'''o(
Devs by nature aren't drawn to documenting and so I am looking for simple ways to help document what's happened.
[Example of my daily struggle: ^in the stride room^ Tech Lead: "Did you test?" Dev: "Yes. Some issues found." Tech lead: "OK"
Any advice? How do you document? What questions are asked? Is it successful with dev teams?
(Yes, I do realise that culture change is needed badly... but a little bit of governance is a nice starting point)
Appreciate any input what so ever :)
Thanks everyone for answering last week’s question. The winner of the random drawing from those who commented is: @LarryBrock I’ll contact you separately with your prize details. This wee...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events