A former employee in good standing has changed jobs. Unfortunately a lot of their work just prior to leaving did not satisfy some acceptance criteria found by QA, and had other bugs. I'm picking up the slack in fixing them. I expect some of it to not be trivial for me to begin fixing (due to my skill/knowledge being lower), and to have to work through this for a while, and what is the best way I should talk about this during daily stand ups?
My goals are
- not to make it sound like I'm speaking badly about the code or the former employee that left, whose work I'm fixing.
- to try not to make myself look bad as I'm going to be busy fixing something that didn't pass muster (I think it looks bad when you push things that are found to have issues when tested), for at least a single sprint, wherein I may not be contributing as much to the new work we've pulled in.
- not to sound like I'm trying to deflect responsibility for fixing it, but certainly I wouldn't want to be mistaken for the source of these issues.
Edit: To clarify the tickets bounced our QA process as they didn't satisfy all the acceptance criteria within them and some other bugs were found, so perhaps saying they only had bugs isn't precise. (The code's already merged in behind a feature flag though.)