- it’s very important for programmers members of a team to keep focusing on their development work, and don’t stop every 5 minutes reading the emails… for example
- avoid too frequent dev-status meetings. Since they are meant to know if the project is on time, they can be replaced by: correct time estimation, notifications of a complete step to the rest of the team, come to the dev lead when something is not clear or problems arise.
- never say "YES" to a feature request, if you don’t know exactly how to place it by the required release time; better to say "NO" instead of saying "YES" and generating other issues.
I’m continuing reading the book and let you know my final thoughts. However, I’ll propose to my team some new concepts based on what I read,… and I’ll also let you know how the experiment is going on later 🙂