3 ms·
That's how it works in well-functioning agile teams, but in "Agile" teams the team can't decide on their own to e.g. totally ditch standups. Management won't al
by corrral 4y ago
That's how it works in well-functioning agile teams, but in "Agile" teams the team can't decide on their own to e.g. totally ditch standups. Management won't allow it, or they've set up the project manager to be God of Agile and they get last say on that kind of thing, and so on.
"Agile" teams outnumber agile teams by a large margin.
- henrikschroder 4y agoIf you have a good team with good people, it doesn't matter much which process you're following, because shit will get done anyway. Agile was a way of trying to document how some good teams got shit done, but most of the companies and people trying to implement it didn't understand that you actually need good people, they thought it was the process, and thus "Agile" was born. ...and to the complete mystery of everyone involved, "Agile" teams don't get shit done.
- Silhouette 4y agoThis is painfully true and also deeply ironic given one of the lines in the Agile Manifesto itself.
- quickthrower2 4y agoGood people but not just that. Good culture, good management, good business model / funding, and a good sprinkle of luck. And what makes them high performing? What is the metric? Money?
- g051051 4y agoThat's how it works in well-functioning teams, period. Being "Agile" or "agile" has nothing to do with it.
- digisign 4y agoI've tried to explain several times to a client that 20-25 people is too many for a standup.
- corrral 4y agoMy "favorite" is when they mix teams working on unrelated things in the same standup. That sucks no matter how many people are in the meeting (thought obviously it's worse the larger the attendance)
- quickthrower2 4y agoThe advantage if this is you have now 20 bored people waiting their turn to spit out a sentence. As they tune out their subconscious mind figures out an elegant solution to what they were suck on.
- urthor 4y agoI've encountered almost zero agile manifesto teams in my time for back-end software. For 95% of projects, getting non-technical customers & stakeholders to read the manifesto and come demo software fortnightly, in person is impossible. At best we get an intern or underling. Interestingly, if the GUI was changed, they usually come racing.