I try to write a unit test any time the expected value of a defect is non-trivial. Expected value would be: Likelihood of a defect * Cost of a defect.
- No location available
-

Instead, design meetings or conversations should be about getting input and answering questions.
- No location available
-

(highlight:: There are plenty of meetings where the purpose is to “get signoff” or to “get buyin.” You should avoid those and only agree to do one if you’re forced to. You don’t want to need “signoff.” You want to be able to make your own decisions and determine what degree of agreement you need from other people.
Instead, design meetings or conversations should be about getting input and answering questions.)
- No location available
-

Any time you’re given a deadline, ask which one of these it is. Of course, it’s often the case that internal deadlines are required to be “on track” for hard deadlines. But what you want to call out is when internal deadlines are presented as hard deadlines for the sake of pressuring people to work longer.
- No location available
- work management, deadlines, schedule management,

Then some people will get into the difference between two “flavors” of Agile, which are Scrum and Kanban. In my mind, Scrum means that “you have to get certain things done with those two weeks.” Kanban means “do what you can do in two weeks.” If it’s not explicit to you whether the team follows Scrum or Kanban, you should have that conversation explicitly – and you should push for Kanban. Given the difficulty of estimation (see Rule 18), Scrum can easily mean that you’ll get pressured to work extra hours to complete something within that arbitary two-week horizon.
- No location available
-