In my old workplace, we had a "definition of done" doc. It listed all the things we needed to do for a task to be done and by saying almost done, others knew we had probably covered 90% of that list. If not, you'd just say "I'm currently working on developing/testing/documentation for this feature" and that was enough to update the team in a stand up.
exactly. the definition of done is very important.
if you say "almost" I think of about 90% completion. however big or long the task was. If it was estimated for a week (5 days), and you are almost done at standup time, it should be done in the evening max.. :-)
"Almost" for something more than a week or two is tricky. I tend to phrase it as "I expect to have a pull/merge request up today, if all goes well" and if I don't, I tell the team the reason why in the next standup. Almost is too vague that I didn't realise I barely use it anymore.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my old workplace, we had a "definition of done" doc. It listed all the things we needed to do for a task to be done and by saying almost done, others knew we had probably covered 90% of that list. If not, you'd just say "I'm currently working on developing/testing/documentation for this feature" and that was enough to update the team in a stand up.
exactly. the definition of done is very important.
if you say "almost" I think of about 90% completion. however big or long the task was. If it was estimated for a week (5 days), and you are almost done at standup time, it should be done in the evening max.. :-)
"Almost" for something more than a week or two is tricky. I tend to phrase it as "I expect to have a pull/merge request up today, if all goes well" and if I don't, I tell the team the reason why in the next standup. Almost is too vague that I didn't realise I barely use it anymore.