Lately we've been semi-scrumming in the section. We tried to integrate some of the Scrum practices, while ignoring others (the hard ones, you know, like the ones that require management commitment and stuff like that). This isn't so healthy, I know, since the practices were designed to work together; but we're trying to use a sensible subset, in an
(
Read more... )
Comments 5
Reply
Reply
I'm not telling that Scrum is bad. I'm telling that it's just another methodology and "metodologiot yesh tesha belira". Why do you switch from one to another? I'd bet that every time the reason is the same: you don't deliver on time and it gives hope that this time it will work. But why don't you deliver on time? Because the requirements aren't clear enough, there are tasks you didn't take into the account and the working class is constantly disturbed from the outside? Scrum won't fix that because you problem is not about optimizing the developers. Photographing the white-board is fine (I myself believe in it) but doing that you optimize one developer's time. Is that indeed your bottleneck?
I have *a lot* to say on this issue. But I'm getting too agitated. Maybe next time.
FireAphis
Reply
Reply
Sorry for being too aggressive.
I still have _a lot_ to say about it (actually I'm on a team that manages to deliver all its reqs on schedule). But I'm getting too de-agitated. Maybe next time.
(Of course I'm always glad to answer any of your questions)
Reply
Leave a comment