HACKER Q&A
📣 rexlucis

How to Deal with Agile Card Scope Creep


Hello everyone,

I have a coworker that whenever he reviews anyone's merge request, he comments about fixing other things that are related to that MR.

For example, if I pull a card from Trello and it says something like 'Disable selecting future dates in Peferences', after you code it and submit, he will add 'I think you should also fix this for all calendars in the app'

Is that appropriate to require in an Agile environment? I could see how that is being flexible and responding to change, but I lean toward it should be a separate card to include all inputs instead of extending the current card.

I'm new so I was hoping to get y'alls opinions on this. Thanks!


  👤 jameshe Accepted Answer ✓
It seems like the comment would be better as a note for the next Sprint retrospective / planning meeting since it should be a separate card. Under the ticket/card/issue/MR seems non-productive to me but if your coworker seems to do it often, it might be because he doesn't understand or didn't have clear instruction for where comments like that can go.