How to Pick Your Battles on a Software Team

Re:How to Pick Your Battles on a Software Team by mknocker on Tuesday June 21, 2016 @09:56AM (#11945594)

I fully agree. When working on a team, you have to think about the future not only the current moment. If every time you have a disagreement it results in a win-lose situation I can guarantee you the mood among the your team will go down quite rapidly. I would suggest 'Getting to yes' by Bruce Patton, Roger Fisher, and William Ury on this matter of negotiation.

[ Parent | on HN ]

Re:How to Pick Your Battles on a Software Team by pjc50 on Tuesday June 21, 2016 @10:14AM (#11945726)

But this is one of the things that the article sets out to define! That the work process should not be driven individual competitive arguing (which is pretty much the default mode of interaction for male technical staff), but people need to think about whether the arguments that they find themselves having are worth it for themselves and for the team.

"Conversely, there are several different conditions that constitute “losing.” The team can lose if you make a teammate feel like their contributions aren’t valuable. The product itself can also lose by missing out on early critique of its features, or by missing an opportunity to have its features developed less expensively."

[ Parent | on HN ]

Re:How to Pick Your Battles on a Software Team by mk89 on Tuesday June 21, 2016 @10:17AM (#11945739)

I don't know this book - thanks for the advice. I would recommend "How to win friends and influence people", which gives also good advice and a lot of hints.

[ Parent | on HN ]

Re:How to Pick Your Battles on a Software Team by AlexCoventry on Tuesday June 21, 2016 @12:37PM (#11947017)

Getting to Yes is a far, far better book than How to Win Friends, with a much more nuanced and broadly useful perspective.

[ Parent | on HN ]

Re:How to Pick Your Battles on a Software Team by mknocker on Tuesday June 21, 2016 @10:21AM (#11945779)

Yes. I read it. Good book indeed :)

[ Parent | on HN ]