Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Why would the PMs do their own work when they can have you spoon-feed it to them and sit on Facebook/fantasy sportsball the rest of the day?
Any chance you could call them on the bad behavior?
Hazarth10428dImo It's a good thing. You get to keep everyone in the loop and everyone keeps you in the loop. So if someone is doing something that's already done, or you can help with, or has to be done differently, you or anyone else can bring that up.
Additionally it also holds everyone at the stand up to a standard, you can't really slack off if you need something to report daily
It gives the PM actual up to date info on what's happening, so if the client or PO changed something, or a feature moves up or down in priority, he wont forget to tell that or other potentially useful info!
It's not going to shine everyday, but It's a good tool to be using to prevent human error in many cases and gives everyone a voice
I'm with @Hazarth, I'm in a small team too and we all have our tasks, but it's nice to hear what people are working on and what issues they might be running into - and share your own.
Edit: reporting on every little thing through the day does seem extreme and counterproductive, I agree
matste5737dIn theory, someone should track progress and everyone should seek synchronization, so, in theory, daily meeting are a cargo cult. In practice, managers are lazy and programmers don’t communicate, so it’s better that the tradition exists.
VaderNT14487dI, too, think dailies are a waste of time. I either work with you on something, thus I'm already aware of our progress, or I don't and thus you're telling me irrelevant information.
And PMs/POs can stay in the loop from our Jira tickets, so no micromanagement needed here either.
This has to do with an ITIL principle known as transparency and visibility across all layers, but I understand in your case it's inefficient.