11–20 of 42 posts
I'm pretty ambivalent about it, because after 25 years of seeing methodologies come and go and come again with the same ideas wrapped in different names I believe projects that succeed, succeed in spite of the chosen methodology, rather than because of it. https://www.wittenburg.co.uk/Entry.aspx?id=99bb5987-e08d-4e8...
I'm pretty ambivalent about it, because after 25 years of seeing methodologies come and go and come again with the same ideas wrapped in different names I believe projects that succeed, succeed in spite of the chosen methodology, rather than because of it. https://www.wittenburg.co.uk/Entry.aspx?id=99bb5987-e08d-4e8...
From my experience I've found that scrumm holds back good, fast developers because they focus on only doing their share in a sprint, when they could rocket ahead and be pounding on the backlog. How can you keep your best developers motivated and busy in an agile/scrumm environment?
I can't tell if these are mocking or not? (Even down to capitalisation of SCRUM). Personally I think agile is best thought of as a broad church of methodologies rather than anything concrete to adhere to, and especially I think the sprint approach isn't always suited to business needs. But a generally agile approach I think is good, and I think daily stand-up meetings are good for communication even without sprints o…
And if I had to pose as Scrum Master, every incentive would push me to intentionally propagate cultishness. (Better than those unaware they're doing it, because at least I can turn it off on a dime as the situation requires.)
Consider: My local chapter of the Project Management Institute has ~7000 members. Are the even 7000 competent people in the area that can act as leaf node workers for these folks? I doubt it.
I can't tell if these are mocking or not? (Even down to capitalisation of SCRUM). Personally I think agile is best thought of as a broad church of methodologies rather than anything concrete to adhere to, and especially I think the sprint approach isn't always suited to business needs. But a generally agile approach I think is good, and I think daily stand-up meetings are good for communication even without sprints o…
It's a pretty big fail when people wait until the daily stand-up to communicate. It's better than not communicating at all, of course :-) Either way, daily stand-ups are the worst thing about scrum especially when they are hijacked by PMs. I'm yet to meet a develop who'd look forward to stand-ups. I know they exist somewhere :-) If you are curious about what other people (you don't talk to a lot) are working on then…
I'm pretty ambivalent about it, because after 25 years of seeing methodologies come and go and come again with the same ideas wrapped in different names I believe projects that succeed, succeed in spite of the chosen methodology, rather than because of it. https://www.wittenburg.co.uk/Entry.aspx?id=99bb5987-e08d-4e8...
From my experience I've found that scrumm holds back good, fast developers because they focus on only doing their share in a sprint, when they could rocket ahead and be pounding on the backlog. How can you keep your best developers motivated and busy in an agile/scrumm environment?
Earlier quoted context omitted.
From my experience I've found that scrumm holds back good, fast developers because they focus on only doing their share in a sprint, when they could rocket ahead and be pounding on the backlog. How can you keep your best developers motivated and busy in an agile/scrumm environment?
Scrum focuses on "systemwide" optimization where the "system" is the development of an increment of a software product from concept to completion. Letting a good developer "rocket ahead" optimizes for that developer (localized optimization) but not for the complete system (global optimization). A more "global" optimization of that developer's time and energy, since they can do twice the work in half the time, is to m…
Earlier quoted context omitted.
From my experience I've found that scrumm holds back good, fast developers because they focus on only doing their share in a sprint, when they could rocket ahead and be pounding on the backlog. How can you keep your best developers motivated and busy in an agile/scrumm environment?
The rocket ahead folks are often really good at creating technical debt for everyone else. The minority who are really rockets usually burn out early in their career. Used correctly, Agile prevents too much of either type from getting out of control, evening out the peaks and valleys. That's what you want, right? A sustainable pace.
I can't tell if these are mocking or not? (Even down to capitalisation of SCRUM). Personally I think agile is best thought of as a broad church of methodologies rather than anything concrete to adhere to, and especially I think the sprint approach isn't always suited to business needs. But a generally agile approach I think is good, and I think daily stand-up meetings are good for communication even without sprints o…
It's a pretty big fail when people wait until the daily stand-up to communicate. It's better than not communicating at all, of course :-) Either way, daily stand-ups are the worst thing about scrum especially when they are hijacked by PMs. I'm yet to meet a develop who'd look forward to stand-ups. I know they exist somewhere :-) If you are curious about what other people (you don't talk to a lot) are working on then…
The one thing about stand ups that I find to be a profound waste of time is reporting what you've done. Isn't that what SVN / GIT / JIRA / etc is for?