teamniteo/handbook

Update standups policy

dmurko opened this issue · 9 comments

dmurko commented

The Story

As a Nitean,
I want to make standups straightforward, quick and clear,
so that we do not lose precious time.

Description

Problem/Task

When we were 4-5, going off-topic with a few minor discussions was not that problematic. Now there are regularly 9-10 people on standups and we need to cut down on these discussions because then other people are idling.

Proposal

We had a discussion on IRL#4 and this is the summary:

  • everyone on standup goes through just three questions:
    • what they've done yesterday
    • what they'll do today
    • if they have any blockers - and who they need to discuss them with
  • following this general standup are specific standups for each department, scheduled when/if necessary and only with people who need to be involved: development, support, marketing, design

Pitfalls

Too many meetings for a few people.

Best Practices (DoD)

  • Documentation is up-to-date:
    • Handbook pages

Expectations (AC)

karantan commented

SP: 1

marbeann commented

SP: 1

cas-- commented

SP: 1

I think we should add this short list of questions to the zoom bot in slack so it primes everyone for standup

  • 👍1
karantan commented

I've added Zoom alert on Slack contains this short list of questions.

  • 👍1
dmurko commented

SP: 1

zupo commented

Do we really need this? Lately, our standups have been fast and efficient, at least in my opinion.

dmurko commented

Because this policy is already implemented in practice but it's not documented.

zupo commented

One by one we'll go over the things done in the last day, things to be done and any blockers anyone has and resolve them. in https://github.com/niteoweb/handbook/blob/master/work-process/standup.md. What's missing?

dmurko commented

Humm. I admit I haven't checked the doc before commenting. We can then close this.