i don't dislike agile and scrum and all these things, but once you get close to spending more time talking about work than executing, people get tired. planning and retros are valuable (grooming as a separate step from planning may or may not be valuable?) but people don't go into software because they care about some pointing system no one understands, they do software because they want to build things.
the goal of agile was supposed to be about getting work done more efficiently and being more transparent about what you were doing, not spending half your week in Mass with the Scrum Pope
i'm now fortunate to be on a team that loosely does kanban rather than scrum, so our main concerns are:
* is work flowing in?
* is work flowing out?
* is anyone blocked?
* is anyone overburdened?
* are we doing work that helps achieve our higher-level goals (as laid out on a flexible year-long roadmap)?
and that is just so lovely. but the rest of the department is still very much in the "jira charts and scrum masters are our lord and savior" mentality, & my team is part of the department. so.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!