...
(4/19) Too many gaps in documentation of requirements, and detailed product behaviour
Diarmid hoping to drive something here, but anyone else who could take this on would be amazing.
(Diarmid making slow progress with PM here, on varous threads)
(4/19) No available domain expert for Contact Tracing
Kyle is working on a contact through Alina
Is one enough? Or do we need more?
(4/19) No signatory to make a contract with Applause
Du Tri will take it forward for Partnership to action - have pushed again to try to make this happen
(4/19) No clear path for escalation of very high-level issues identified in Test - e.g. Privacy / Security concerns
Diarmid now has a comms channel established with Sam, when needed, and improved organization of the PM team means it’s much clearer where to go with specific issues.
(4/19) PractiTest not yet embedded as a tool.
Limited test cases documented in PractiTest
No clear patterns for using PractiTest for more exploratory forms of testing and for overall Requirements Tracing - not clear whether or not we want to invest in this, much of this is happening in Confluence today, and that may be good enough.
(4/19) No current process for raising reqs/spec issues uncovered in Test
We’ve been asked not to file these in GitHub issues.
We believe we’ll be moving to Jira, but not quite ready yet
We need to update guidance for testers.
(4/19) Broad set of resources now available in Confluence, but it’s It’s still proving difficult for even experienced testers to engage with this project, when they first arrive, despite us now having a broad set of resources now available in Confluence. We are tryng to get a better understanding of what else can we do. Are further resources neeed? What? Do we need to run in a much more explicitly directed manner? May Moorefield outreach + Lean Coffee session will hopefully provide some answers.
??? what else - please add your impediments here
...