News for hackers. Stuff that matters.
Re:The Failure of Agile by zelos on Wednesday May 13, 2015 @11:40AM (#9539753)
In my experience, either:

- A few people end up discussing some minor point only of interest to them while everyone else stares into space

- Every retrospective ends up being the same as the previous one: it's like someone recorded a meeting 2 years ago and plays it back every 8 weeks

- Things that went well are all internal; things that went badly are all other teams' fault (this can't always be true)

Yes, I realise those aren't really agile issues, just a symptom of having a relatively poorly defined meeting with lots of people.

Re:The Failure of Agile by kamaal on Wednesday May 13, 2015 @11:56AM (#9539895)
>>A few people end up discussing some minor point only of interest to them while everyone else stares into space

Mostly the manager's minions and pets talk, generally in a softer tone more towards appreciation bordering sycophancy. The remaining fear to give any genuine feedback, fearing retribution. If some one does speak they are taken as non team players who will be handled appropriately the next raise/promotion cycle.

There fore no one talks.

Re:The Failure of Agile by warfangle on Wednesday May 13, 2015 @01:09PM (#9540397)
The scrum master or even "team lead" is supposed to catalyze things a little bit in those situations. A lot of times there's a culture of "everyone knows about it, but nobody will say anything about it because they're afraid of the axe," where "it" is the thing that's horribly wrong.
Re:The Failure of Agile by BenLinders on Thursday May 14, 2015 @03:54PM (#9547204)
These are clear symptoms of not having retrospectives facilitated in a proper Wat. A good facilitator uses different exercises, has people focused on a fixed scope or time period to catch learning points, supports a team in coming up with actions that they can do immediately and that are small enough to finish on a short notice.