I think the daily standup and retrospective meetings are easy to implement because they can be seen as status meetings for the chicken's benefit. They aren't, r

I think the daily standup and retrospective meetings are easy to implement because they can be seen as status meetings for the chicken's benefit. They aren't, really, but it does seem easy to turn these from "developers appraising other developers about their problems and status" to "give me, the chicken, a list of the ticket numbers you plan on working on today and their status" Retrospectives of course are seen as meetings (and managers love meetings) where the team works internally to make itself better. Woh , what a great idea! Except this also misses the point - sometimes the retrospective generates feedback for the organization/environment the team works in. "Sales people should file tickets, instead of cornering us and making us listen/do their thing". Things like this may be ignored or shoved in a desk drawer because "it's just developers whining"