Processes optimize the efficiency of repetitive work. E.g. reinventing a new way to apply
for vacation every time somebody applies is inefficient.
Problems occur when you try to apply processes to creative work, which by its nature isn’t repetitive.
Scrum is iterative, and iterations are about working on the same subject again. So in my view (as a Scrum Master), it makes sense to have a process for the repetitive parts (a.k.a. the events). But you need to make sure that there is enough space for creativity, and that space isn’t taken away by repetitive tasks (e.g. frequent company meetings)
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.
Processes optimize the efficiency of repetitive work. E.g. reinventing a new way to apply
for vacation every time somebody applies is inefficient.
Problems occur when you try to apply processes to creative work, which by its nature isn’t repetitive.
Scrum is iterative, and iterations are about working on the same subject again. So in my view (as a Scrum Master), it makes sense to have a process for the repetitive parts (a.k.a. the events). But you need to make sure that there is enough space for creativity, and that space isn’t taken away by repetitive tasks (e.g. frequent company meetings)