Stand ups (as originally described) shouldn’t be about what you already did, but what you are going to be working on and if there is a need to collaborate.
Most people got the concept wrong and turned them into mini status meetings.
According to the PMBOK (7th edition) by the Project Management Institute (PMI), daily standup is a “brief, daily collaboration meeting in which the team review progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated.” Source
To be fair, daily standups are defined however your group collectively decide to define it.
For those who decide to report the work from previous day, it’s expected that you would have made your list before the meeting, not during. It’s a practice I too struggle with. 😊
True. I’ve worked in pretty small teams with usually 2-4 devs paired, so it kind of worked out as both what we got through, what’s next priority, and how we plan to split out that day. Especially if we were light on stories.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Stand ups (as originally described) shouldn’t be about what you already did, but what you are going to be working on and if there is a need to collaborate.
Most people got the concept wrong and turned them into mini status meetings.
To be fair, daily standups are defined however your group collectively decide to define it.
For those who decide to report the work from previous day, it’s expected that you would have made your list before the meeting, not during. It’s a practice I too struggle with. 😊
Yepp, and no one really listens to the others, just trying to remember what you did and make sure no one dumps more work on you.
True. I’ve worked in pretty small teams with usually 2-4 devs paired, so it kind of worked out as both what we got through, what’s next priority, and how we plan to split out that day. Especially if we were light on stories.