3 ms·
Definitely don't join an agile shop with 2hr ceremony BS meetings
by steveBK123 5y ago
Definitely don't join an agile shop with 2hr ceremony BS meetings
- ipaddr 5y agoYour comment made me realize why burnout exists.
- steveBK123 5y agoIt's funny because we all think the grass is always greener and yet.. my most recent 2 job leads: * a firm that was demanding devs return to office already in January pre-vaccine, justifying it by paying for Ubers & doing PCR testing in office * a firm which in its job-spec explicitly listing that "8a-6p are standard hours" and "plus other hours as required for role / due to support / meetings out of region / some flexibility required" what a shitshow tech can be
- danjac 5y agoWe can push back by publicly shaming bad actors and ensuring they go to the back of the queue along with the firms with psychopathic interview processes when it comes to choosing tech talent at a time of high demand. Unionising would probably be better but for some reason a bad word around these parts...
- janandonly 5y agoMuch Good has come from unions. So why would that be a "bad word around these parts" ?
- mixedCase 5y agoBecause Much Evil has also come from unions, devs are in high demand, and unions are political structures instead of technical ones.
- HWR_14 5y agoWhy does the fact that devs are in high demand mean a union is bad? How does demand relate to unions at all?
- FredPret 5y agoI’m an uber capitalist but I think all workers should be totally free to unionize. Unions gave us the weekend, can’t be all bad.
- quickthrower2 5y agoThe good thing about the ceremony is having the whole team see whats being planned and giving input and helping each other out. But there might be a more efficient way to do this. Get everyone to read a published "this is our roadmap" page or something like that.
- pstuart 5y agoThe ceremony is usually: what's the status of this Jira ticket?
- deleted 5y ago[deleted]
- steveBK123 5y agoThe worst ceremony is the retrospective. Let's talk about what made us do a bad job this sprint. Some revolving list of "other team __" being slow/unreliable/hard to manage/etc.. The same 1 or 2 senior devs is tasked with taking away some discussion points to have with them. Rinse&repeat.
- nicbou 5y agoI've organised those meetings. You could halve their length by doing most of the grooming yourself, and just saving the remaining questions for the team. The meetings would only take a few minutes with Kanban, assuming the backlog stayed sorted. I just asked where the new tickets had to go in the current sorted list. These meetings would be much faster if project managers didn't clog the backlog with stream-of-consciousness tickets. However I was never an Agile guy. I trimmed the process heavily, and took up most of the backlog maintenance so that others could work.
- steveBK123 5y agoThis requires the organizer to be organized. If management is running sprint ceremonies but in 5-6 hours/day of meetings, they come in unprepared and ad-lib. Our product manager sits in on the meetings such that he can says yes/no when questioned on tickets, but for all I know could be watching soap operas given his level of engagement.