15030Re: [scrumdevelopment] Scrum is bad for employees (apparently)
- Aug 1, 2006(responding to Richard)(I wrote this before reading the reply from the other Paul; I've addeda postscript)
Friday> ...Anyway, I had a couple of resignations from my staff last> – which was the conclusion of our last sprint.Don't take this as criticism, just something you may want to thinkabout.Suppose you had to continue working with these folk? How wouldyou go about changing their attitudes?The reason I mention this is that if you had that option, you wouldhave two ways of dealing with the situation and could choose whichwas more appropriate. Having a choice is always valuable.I guess it's up to you to decide whether it's worth the cost incurredin taking that skill on board... or using a third party with that skill.It's hard to say from the limited report, but your ex-employee Bmight have been worth the effort. Indeed, where one has to livewith the person, one might find ex-employee A not entirelyintractable.Paul Oldfield.(postscript)
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Employee B was just a poor developer who felt the pressure to>> perform and was exposed by scrum. The gap between him and> all the other developers became more and more apparent the more> sprints we completed. Under “normal” development environments
would have been able to hide a lot better and explain away> he> slow performance as investigative workDo you censure or reward performance for the team as a whole,or for individuals? Scrum is good at exposing problems. We getto choose how to address them. You might find Alistair Cockburn'swritings on "Personal Safety" (e.g. in Crystal Clear) worth reading.
- << Previous post in topic Next post in topic >>