Confirmed users
14,525
edits
User:Ashughes/PI Requests v2: Difference between revisions
Jump to navigation
Jump to search
→Documenting Key Criteria
| Line 308: | Line 308: | ||
* Important to have continuity of tester, have them participate in meetings, etc. The system should track a testers previous work so requests can be assigned according to not just skills but developed experience/relationships. | * Important to have continuity of tester, have them participate in meetings, etc. The system should track a testers previous work so requests can be assigned according to not just skills but developed experience/relationships. | ||
* Testers need to be able to ask questions and make suggestions of things the requestor may not anticipate | * Testers need to be able to ask questions and make suggestions of things the requestor may not anticipate | ||
* Need to provide a value proposition over simply need-info flagging a tester on a bug, the key is to have someone assigned quickly | |||
=== Pain Points === | === Pain Points === | ||
| Line 328: | Line 329: | ||
* Not all requests are features; some are requests for automation, regression testing, A/B testing, etc; asking for information not relevant to the request wastes time | * Not all requests are features; some are requests for automation, regression testing, A/B testing, etc; asking for information not relevant to the request wastes time | ||
* "Timeline" is really confusing and poorly defined | * "Timeline" is really confusing and poorly defined | ||
* Testplans are not immediately discoverable unless requested | |||
* Need to improve clarity and transparency around where my request is in queue, priority and prioritization process, and current status | |||
=== Roles === | === Roles === | ||