3 ms·
> high trust What do you do if you work in an organization that is set up with scrum managers whose sole job it is is to run through tickets + follow up? "Hey
by MuffinFlavored 4y ago
> high trust
What do you do if you work in an organization that is set up with scrum managers whose sole job it is is to run through tickets + follow up?
"Hey developer, how is the progress on that ticket coming? Any blockers? When do you estimate it will be done? How many story points should it be? Should we pull it into the next sprint? Don't merge any code into the release branch for that ticket until we start the next sprint. Let's have a daily standup meeting, then let's have a weekly planning meeting for the next sprint." The scrum manager reports to the manager manager who reports to the director/VP who wants to see progress through releases/tickets, etc. etc.
Like... how many HackerNews readers live this every day versus how many will say "if that was my 9am-5pm, I'd quit because it's a sign of ________ in an organization/corporation/team and I wouldn't stand for that. I only work for teams that let me do whatever I want with 0 observability into progress/ticket tracking".
- dijit 4y agoI mean, if you’re at that point then you’ve already failed the scenario I described. A scrum master is a symptom of lack of trust personified into a role. I’m sure some are servant leaders that seek to unblock, unify or enhance development; but that would be the exception. The causes for them being employed to begin with are likely lack of visibility or lack of trust in the ability of the team to understand what is a high priority.