Open justincc opened 4 years ago
@morrisonnorman @justincc I understand from @brianraymor 's PM meeting notes that this can be scoped and delivered by Q4M3. However, I'm having difficulty parsing the work towards this roadmap objective, and i need help understanding a few things so that I can resolve the prioritization questions that Brian elevated to PL:
Thanks. Happy to get on a call early next week if it would be helpful.
Norman and I sync'd up, we decided on some next steps. The short-term goals are to decide how to measure reliability, identify what the current reliability is, and estimate the improvement for Q3.
@morrisonnorman to sync with @parthshahva on:
@justincc to either confirm tickets are ordered, or do some rough ordering of tickets in terms of effort/value ratio.
When this is done, @morrisonnorman and @justincc should be able to associate some set of tickets from this epic to a targeted reliability improvement for Q4.
@ambrose, the DCP-wide work necessary to cover publishing DCP-wide reliability statistics, which will give the DCP awareness of the true situation in the same way that we have a project tracking dashboard, was being covered in #521. However, @brianraymor closed it because it needed work. I don't have time to try and perfect ticket descriptions this comment will have to serve notice that this work is critical and will be done under this epic.
Regarding the per-component tickets, for reasons known elsewhere I have not had time to consider them. In truth, this is an area where tickets emerge as and when we discover problems. As no other components have chosen to expose their work in this way, and because that part is confined to individual components, I propose to remove it entirely from the DCP view.
The work in this quarter consists of:
a)
per-component reliability workremoved from this board as per discussion in PM 2019-10-31 call b) DCP-wide information gathering on reliability performance, recording and publication. It is critical this is tracked and completed at the DCP level.Following DCP-wide feedback on the existing reliability information, subsequent quarters will need work to gather more information and then specific tasks to increase reliability. Outside of implementation work, we will need product to decide appropriate reliability targets in conjunction with tech-arch, and then a process to identify what needs to be done to improve reliability and schedule the items for action.
See the INSANE DCP reliability working group doc.
Follow on from #418.