91–100 of 125 posts
Most people post by noon, and the manager has a written log. It's been working well so far.
Standups can however very easily become very uncomfortable in a dysfunctional environment. (As the original article unwittingly demonstrated.) Consider the standup to be the canary in the coalmine. Most of the time people can ignore the dysfunction, work around it and pretend it isn't happening by just getting on with the job as much as possible. But the standup will then become increasingly uncomfortable. Every sing…
Earlier quoted context omitted.
I've been thinking of writing a script that pulls down commits from , formats it "properly" and pipe them to SAY. "Wednesday, 24 April Fixed bug #434, added protocols between user and tasks. " And if they _really_ want to know what I am going to work on or what issues I have. Please check my tracker. There are bugs, features and chores. And each of them has comments that describe any issues I might have run into or w…
Actually in a well ran agile team, you should not need that as you should be focused working on only one user story. If you are fixing bugs then the story should be "x bugs related to foo feature" and your daily standup report should be "I fixed x bugs on foo, I have y to go, should be done today, no blockers"
I'm genuinely curious, how are standups not status meetings? From the article: - Make sure everyone is working on the right thing - Help out other team members by taking work off their plate or helping them by sharing domain-specific knowledge - Keeping everyone informed How is that different from a status meeting? I've heard "standups are not status meetings" over and over from the agile community, but I don't get i…
The daily stand-up as a status meeting is a common anti-pattern and one I often have to coach teams out of. While yes, you may be able to derive status from a daily stand-up meeting, that's not the point. The point is for the team to co-ordinate their work and figure out how they're going to get things done. Done well, it has more in common with a planning meeting than a status meeting. I actually have a whole course…
Good luck with your course.
At my company, we have a HipChat room for "Daily Updates" and an automatic reminder that notifies everyone to post what they did yesterday and what they plan on doing today. That's it. Most people post by noon, and the manager has a written log. It's been working well so far.
Honestly, I can't understand all of the vitriol around "agile" methods that arises here occasionally. If you're doing something that works for your team, do it, if it doesn't work, do something else. Isn't that the whole idea behind "agile" stuff? Do people get stuck in situations where they have to do X because "we're doing agile, and agile says we must do X"? If so, can't the offenders be gently pointed to http://a…
Oh, the vitriol is entirely earned. I learned one of the Agile methods before the term Agile was even invented. Adopting it made a giant difference in the quality and sanity of my work. But so many people today have have pseudo-Agile methods inflicted on them in large corporate contexts. There, the point isn't to make things saner and more effective. It's to please some executive who has a bee in their bonnet. And of…
"Remember, they are not status meetings." Additionally, I think it is important to remember that standup is not a "justify my existence on the team" meeting. Having nothing to report is fine.
How do I communicate this when I'm in such a team and daily meetings are regularly going 30 minutes?
Offtopic - Hate these "github.com" posts that are actually from some blog hosted by some random dude on Github. Makes the domain bit meaningless. Wasn't there some fix for this to show more of the domain in certain cases?
Bookmarklet: https://github.com/johngibb/Hacker-News--Show-Subdomains
Edit: Haven't tried them myself; just did an hnsearch. It would be great if Hacker News would always show the subdomain if not www.
"Remember, they are not status meetings." Additionally, I think it is important to remember that standup is not a "justify my existence on the team" meeting. Having nothing to report is fine.
In a meeting where you're supposed to say what you've been working on, at a job where you're paid to be working on it, in what way is it fine to have nothing to report?