Be the first to like this
Are you convinced that test-driven development (TDD) will benefit your team, but you find some developers view the practice as unproductive and unhelpful? Are you the lone voice advocating for continuous integration (CI), really convinced it will bring huge benefits, but others don't want to listen? Do you see the wisdom of secure-by-design and actively assessing software security, yet management feels that they've avoided any problems so far and assume they'll continue to avoid problems.
Research tells us that the information we take in depends on a person’s assumptions, aversions, biases, and preconceptions. Broadly speaking, psychologists and scientists call these cognitive biases. People who study organizational behavior use their understanding of cognitive biases to bring important improvements and change to individuals, teams, and organizations.
Come learn about common cognitive biases that impact development teams. Let's explore strategies to identify and cope with seemingly irrational decisions against new and better practices. Through specific examples, learn some straightforward ways that may help you manage the opposition you encounter that can hold teams back.
Stephen Ritchie is the author of Pro .NET Best Practices (http://www.apress.com/9781430240235) and the organizer of the DC ALT .NET group (http://www.meetup.com/dcaltnet). He has been writing software professionally for over 20 years. Stephen works as a software development consultant at Excella Consulting in the Washington, D.C. area. His passion for following best practices has taught him to appreciate the value of experience, practical know-how, and continuous learning. Stephen is the .NET best practices steward at Excella Consulting, working with .NET project teams to facilitate and sort out the helpful practices from the unhelpful ones, the practicable from the impracticable, and the "sounds good" from the "it really is good" practices and principles.