Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Voxera113933yThat sounds like either bad planning, bad information or management that think meetings in by them self will solve things.
A good meeting will have just the necessary people and unless its a response to some acute problem every one should have a good grasp on why they are in the meeting so they can come prepared. -
msdsk31793y@Voxera
Last time at a meeting of >100 developers they took half an hour to talk about changes... in the user manual. 50 work hours at least irreversibly lost. -
acz09033903yI used to work for a company where Scrum was a religion. The amount of time that got wasted at planning meetings every effing day!
-
Voxera113933y@acz0903 for our trams scrum meetings take on average 6-7 hours out of every two weeks or 80 scheduled work hours.
And that includes refinement where we look at the actual tasks and discuss ideas and who needs to be involved, for example if we need ux, frontend and or backend, and that is almost a pure dev meeting except where we invite stake holders so we can ask questions to clarify the requirements or raise objections or suggestions if we think there are better solutions.
Then every 12-14 weeks we have two days of meetings to plan for next quarter where we also sync with all other teams and departments so we fo not end up building something that depends on some other task that will mot get done until next year ;)
Nothing gets me so anxious like endless work meetings that have nothing to do with my part of the task. Why am I even here? Should I understand this? Why is it taking 2 hours? Can I finally kill myself?
rant