The ideal length depends on the situation. If you can't finish important work in a week you have basically two options:
Try to split the major improvements into smaller, incremental changes.
Try 2-week long sprints.
Whatever you do, you will need to evaluate whether it solved the problem. A good way to do that is define your process changes as experiments and answer the following questions:
What is our current situation?
What is our target situation?
What are we going to try next?
And when you've had some time to try the changes, go through those questions again and check if the new current situation is closer to the target situation than the previous current situation. Then you can define a new next step to get even closer to the target situation.
Just to reiterate, there's no ideal length, it depends on your specific context. What works for another team might not work for your team, and what works for your team now might not work anymore after six months. Hence the need to review and adapt your process periodically.
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.
The ideal length depends on the situation. If you can't finish important work in a week you have basically two options:
Whatever you do, you will need to evaluate whether it solved the problem. A good way to do that is define your process changes as experiments and answer the following questions:
And when you've had some time to try the changes, go through those questions again and check if the new current situation is closer to the target situation than the previous current situation. Then you can define a new next step to get even closer to the target situation.
Just to reiterate, there's no ideal length, it depends on your specific context. What works for another team might not work for your team, and what works for your team now might not work anymore after six months. Hence the need to review and adapt your process periodically.