3 ms·
I personally find the cycle of planning => sprint => retrospective to be great for teamwork, but scrum in itself is not really something I would care about. Pic
by dgellow 6y ago
I personally find the cycle of planning => sprint => retrospective to be great for teamwork, but scrum in itself is not really something I would care about. Pick the concepts you like and forget about the rest, there is no need for the full package. For example doing some estimation work during planning to be sure that tasks are clear and simple enough (in the sense of “low complexities”) for everybody in the team is great. But you don’t need to actually assign a “complexity value” or whatever as they create confusion and false expectations.
What works for my teams in the past was to just pick a process then regularly ask ourselves if it’s slowing us down or is missing something, and change it slightly when necessary. You may need a few weeks to get used to a working routine that works for everyone, and it’s likely that will evolve over time depending on the people and projects. Better to keep processes to a minimum and make it easy to change it in cases something doesn’t work.
- de6u99er 6y agoExactly! Scrum is just another tool in a project managers toolbox. I like the process based aproach of PMBOK, which is a set of processes that can be applied or left out, deoending on the project context. Unfortunately I see a lot of Scrum managers, and certified project managers constantly applying all processes they learned about and furthermore annoying those who do the actual work.