3 ms·

I'm a manager who recently transitioned my team to Scrum. I see many parallels from the doc to my team vis-a-vis the Scrum process as implemented by our scrum

I'm a manager who recently transitioned my team to Scrum. I see many parallels from the doc to my team vis-a-vis the Scrum process as implemented by our scrum master. I think it's an awful process and I'm questioning whether it was the right move. I don't really see any improvements despite my engineers' desire to adopt it. It seems to help junior engineers by making them comfortable tackling unfamiliar systems and code. However, it's completely slowed down my senior engineers. I feel Parkinson's Law (work expands to fill the time allotted for it) creeping in. The scrum master encourages the engineers to be conservative in their sprint workload. I suspect if my engineers were more enthusiastic and proactive, it might have paid off. However, I think enthusiastic, organized and proactive engineers don't need any process to be productive.

winrid 8y ago
You hit the nail on the head. Hire the right people, keep the teams small, and you can just give them context and let them solve the problem.
commandlinefan 8y ago
> completely slowed down my senior engineers > if my engineers were more enthusiastic and proactive You should definitely get rid of all of them. They're holding you back. Free them to pursue other opportunities, because it's obvious that you would be taking over the world if you weren't hamstrung by lazy, coddled, overpriced, whiny complainers. After all, even if you don't have the budget to offer what the absolute best and brightest might command somewhere else, I'm sure that the most talented engineers would jump at the opportunity to work for and with a true visionary like yourself.
- deleted 8y ago
  [deleted]
- kradroy 8y ago
  You're a true leader with your inspiring, insightful comments. I've worked with these engineers for the past 5 years as a technical lead and as their manager. I'm thoroughly qualified to pass critical judgment on them. I instituted Scrum because they asked for it thinking it would be helpful. It hasn't had that effect. My point was that process means little if your people aren't engaged.
simonswords82 8y ago
> However, I think enthusiastic, organized and proactive engineers don't need any process to be productive. I understand the point you're driving at, but process is essential. It makes bad engineers less dangerous, and good engineers more productive.
williamdclt 8y ago
> However, I think enthusiastic, organized and proactive engineers don't need any process to be productive. They definitely do: I'm currently working with a team of enthusiastic, organized and proactive devs and they are delivery at a crawling pace due to the lack of process.

winrid 8y ago

You hit the nail on the head. Hire the right people, keep the teams small, and you can just give them context and let them solve the problem.

commandlinefan 8y ago

> completely slowed down my senior engineers > if my engineers were more enthusiastic and proactive You should definitely get rid of all of them. They're holding you back. Free them to pursue other opportunities, because it's obvious that you would be taking over the world if you weren't hamstrung by lazy, coddled, overpriced, whiny complainers. After all, even if you don't have the budget to offer what the absolute best and brightest might command somewhere else, I'm sure that the most talented engineers would jump at the opportunity to work for and with a true visionary like yourself.

deleted 8y ago
[deleted]
kradroy 8y ago
You're a true leader with your inspiring, insightful comments. I've worked with these engineers for the past 5 years as a technical lead and as their manager. I'm thoroughly qualified to pass critical judgment on them. I instituted Scrum because they asked for it thinking it would be helpful. It hasn't had that effect. My point was that process means little if your people aren't engaged.

simonswords82 8y ago

> However, I think enthusiastic, organized and proactive engineers don't need any process to be productive. I understand the point you're driving at, but process is essential. It makes bad engineers less dangerous, and good engineers more productive.

williamdclt 8y ago

> However, I think enthusiastic, organized and proactive engineers don't need any process to be productive. They definitely do: I'm currently working with a team of enthusiastic, organized and proactive devs and they are delivery at a crawling pace due to the lack of process.