| > [standup is] not too bad compared to other stressful jobs My beef with the standup is that it does not serve the developers. It's simply the act of management pulling the oil stick from the engine, wiping it clean and firing the engine up REGARDLESS of what oil levels are present. So many times I've had the standups used simply as a one-way process. People get their information but theres "no time" to discuss anything at length and the deciders are magically busy all day long afterwards. I don't think its wrong to have brief updates and not get into long-winded discussions during the updates, but if there's not ever time to discuss relevant issues this becomes a social / psychological tactic by deciders / planners to avoid "blowing scope" and "adding additional work" as I have experienced it. Fuck the people working on the thing, we already decided. Stop complaining nerd just sprinkle some PHP on it and get on with your life. Granted, I am painting a worst-case scenario picture here based on my experiences. The alternative (no check-ins, or hardly ever) is actually worse in my opinion. The common thread is give-a-shit. Do the people asking for updates actually care or are they simply collecting information to regurgitate to others. One of these two personality types brings value to the organization, which one do you think it is? I will talk all day to people who are on the same page as me, or people who genuinely care and want to understand. The ones who actively don't want to understand can go directly in the volcano. |