Explaining why testing is necessary. Corollary: Explaining why despite having delivered the application once without testing once, it does not mean testing is useless.
Explaining that our testing is not useless because the client found a bug.
Explaining that it is normal that we get some specification wrong and need to change them after further discussion with the client. No we do not need to fire the BA.
Explaining why, despite coding our apps "by the spec" we still need to schedule some integration testing.
Explaining that public shaming of a developer that committed a bug is counterproductive.
Explaining that the priority on task to LOW allow us to know what task will not be done if running out of budget. Also explaining that setting all the task as HIGH is not a workaround for lack of budget.
Explaining that budget consumption is not a proper indicator of progress. Also 9 women cannot have a baby in 1 month.
Sometimes the client is wrong, it is ok to discuss with the client.
It is ok to be wrong. Yes developer are wrong all the time and that does not make them bad developers.
You cannot estimate with 100% certainty.
Analogies and high level description are not substitute for in depth knowledge.
Example:
Explaining why testing is necessary. Corollary: Explaining why despite having delivered the application once without testing once, it does not mean testing is useless.
Explaining that our testing is not useless because the client found a bug.
Explaining that it is normal that we get some specification wrong and need to change them after further discussion with the client. No we do not need to fire the BA.
Explaining why, despite coding our apps "by the spec" we still need to schedule some integration testing.
Explaining that public shaming of a developer that committed a bug is counterproductive.
Explaining that the priority on task to LOW allow us to know what task will not be done if running out of budget. Also explaining that setting all the task as HIGH is not a workaround for lack of budget.
Explaining that budget consumption is not a proper indicator of progress. Also 9 women cannot have a baby in 1 month.
Sometimes the client is wrong, it is ok to discuss with the client.
It is ok to be wrong. Yes developer are wrong all the time and that does not make them bad developers.
You cannot estimate with 100% certainty.
Analogies and high level description are not substitute for in depth knowledge.