4 ms·

What exactly is the alternative? This reads like a criticism of capitalism. If there is a better way, prove it.

• pelasaco 5y ago
  I think what he wanted to criticize here was the following: "Agile consultants don’t build software. Their job is to sell training. Software architects and developers have the job of building software. It’s similar to the difference between a film critic and a filmmaker. If you had to make a movie, whose advice would you follow? It’s the same with software. Agile consultants cannot tell you the best way to efficiently build maintainable software because they don’t actually build software. For that, you need a Software Architect." I personally am extremely annoyed by pseudo-psychology used to justify games and interactions on Retrospective meetings.. I worked in a project that we had to draw every Friday afternoon 30 minutes together something about our feelings...
  • icedchai 5y ago
    When they ask the team if there’s anything you want to stop doing during the retrospective, mention “this.” It’ll get some laughs at least. Many, many people hate these agile “rituals”, but few are willing to complain about it. We need to end this nonsense.
  • pydry 5y ago
    I always found that without retrospectives persistent, recurring and systemic problems that the team could easily solve would not be addressed until somebody got hopping mad. There's always something else to do. Retros are often useless though, especially in environments where people feel awkward about speaking their mind. They also have a tendency to degenerate into whinge sessions about things the team has little to no control over. Other than being a bit cathartic this is usually pretty useless.