I think that burnup charts are a valid alternative, I think you made some good points. In addition, if possible, I would reserve some time (maybe 20%) for “slack”, i.e. time that you don’t plan in advance. If something unexpected happens, you use that slack time. Otherwise, you use it for refactoring, bug fixing, learning or communicating what you’re doing to the rest of the org.
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.
I think that burnup charts are a valid alternative, I think you made some good points. In addition, if possible, I would reserve some time (maybe 20%) for “slack”, i.e. time that you don’t plan in advance. If something unexpected happens, you use that slack time. Otherwise, you use it for refactoring, bug fixing, learning or communicating what you’re doing to the rest of the org.