2 ms·
I think this part is somewhat true. Big problem is management/sales/business analysts taking over the scrum and weaponizing it to blame developers or push them
by ozim 2y ago
I think this part is somewhat true. Big problem is management/sales/business analysts taking over the scrum and weaponizing it to blame developers or push them into thinking they have to do all what they are told.
Issue is those people are usually more pushy, talkative, so it is easier for them to take over and having devs as pushovers.
I work in a company where me and other senior devs made sure that we run the scrum and we use scrum as our shield.
They want to change the scope? well wait till end of the sprint and add new requirements to our refinement , we will see if you have written good requirements or if not we send it back to drawing board. Velocity is not ever increasing, velocity is for us to make sure we don’t put to much work when someone is on vacation or we have new team member that needs onboarding.
Yes there are hotfixes and special cases where we drop stuff and work on something that has priority, but it is not someone just telling us - but you have senior devs to talk to first and explain that really is special case. Because if something really helps us to make customer happy I am also happy to jump on that to fix it.