Mind the Burndown, Comrade – Scrum Propaganda Posters
1–10 of 42 posts
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#2I'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...
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#3I'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?
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#4I 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 or a maintained backlog.
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#5Philosophically I find it hilarious these posters supporting a particular agile flavor are using the style of the ultimate waterfall command and control system which certainly was not based on reciprocal communication and immediate feedback loops :D
Love the hands in the "all blockers" poster.
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#6I'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 think the problem with how agile is "sold" is that it is offered as a prepacked pack of tricks without going to its roots in the queing theory which gives a pretty good reason for a lot of stuff thus leaving the users of the methods partially deaf and blind. But any constraints for projects are better than none and there are worse things than scrum out there...
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#7I'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?
From my corporate experience, retaining two types of developers on staff for the two different types of challenges is a good idea in general. At my current company, we have a dedicated scrumm team working on the really large projects and individual waterfall engineers cranking out special requests. We swap out engineers between the two groups so they can enjoy creating both types of work product.
The only downside to scrumm IMO is that some companies champion it like it's the only valid solution and waterfall is demonized somewhat. It seems to me the best organizational design is the one that takes into account all likely possibilities. Flexibility twists with the wind. Rigidity eventually cracks and collapses.
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#8I'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?
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 mentor, support, teach, and otherwise spend their energy helping EVERYONE get to their level. Since they can and will get their "portion" of the work done quickly, they have bandwidth to add values in other ways as a force multiplier.
From my experience people like this end up in "lead" or "architect" roles.
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#9I 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 Hubot is a good solution. Hubot has a great plugin to let you share what you are working on without having to deal with stand-ups.
Re: Mind the Burndown, Comrade – Scrum Propaganda Posters
#10I'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...
Has it been the same cycle of cargo-culting management as well? I've only been in this game for 3 years, and the number of different labels for "Good Software Development" is already uncountable.