> There was no division of duties on the team. Everyone was responsible for the system as a whole. The authors point is valid: It is necessary to be aligned w

> There was no division of duties on the team. Everyone was responsible for the system as a whole. The authors point is valid: It is necessary to be aligned with your team leader. :( I think that this author has had a key misconception about their team. Regardless of what the 'official policy', it turns out that that the team is happiest (excluding the auther) so long as this author is continuously monitoring certain issues. It's less efficient for multiple persons to be doing the same monitoring. If I were in her position, I would attempt to divest myself of the menial task of checking/monitoring and write some code to do it instead. (And automatically deal with this "extra master")