- Respond to an asynchronous standup
For example, our remote development team has a law that makes it compulsory to respond to an asynchronous standup. To respond means that if I don't give an answer, then I say "I can't answer / I don't have time", i.e. people should understand what's going on.
There shouldn't be a situation where someone writes his standup and doesn't know whether others read it or not.
No, if I read, then I should give a feedback: discuss it or send a some emoji so that everyone would know that the information was received.
- You need to indicate your schedule and report any changes in it
This is required not for fixing your working time but for ensuring that other people working with you understand when you will and will not be available so as not to wait for a response from you; so that they can plan all the activities, understanding the schedule of another person.
- If you're going to criticize it, then suggest something else.
It gives you the opportunity to listen to and hear other people's position on your problem.
- There is no individual zone of responsibility, but a common product
Yes, everyone has their own area of responsibility. However, if while doing something, you discover that some things aren't working correctly but you still ignore it just because you are not the one directly in charge of that, then this is a wrong approach.Everything concerns everyone, because everyone is working on one common product.
Of course, it's not always possible to do everything perfectly, and it's good when everyone, noticing the problems and challenges, reports them for general discussion in order to come up with a solution.
Then comes the rule "If you're going to criticize it, then suggest something else"
– that's how the process of grinding and improving occurs.