communications

Dealing with overly agreeable people can be fraught with obstacles quite different than those usually associated with the stereotypical stubborn geek who seems unable to bend or compromise. This article will help you understand and deal with the unexpectedly challenging aspects that you may experience interacting with some agreeable people.

Leslie Sachs explains what to do when members of your team exhibit overly aggressive or downright combative behaviors. Because you’re unlikely to change your colleagues' modus operandi, it is wise to instead consider how your DevOps effort can benefit from taking into account some typical behaviors of people with Type A or Type B personalities.

Almost any description of a job involving software configuration management—or more generally, application lifecycle management—will include the words “best practices.” Kareen Kircher writes on how to make best practices a reality for your work. The five ingredients to making successful changes happen are relationship, timing, automation, pertinent documentation, and refining.

One of the hardest daily tasks developers, QA, ScrumMasters, and product owners encounter is effective communication with others. Sound implausible? According to many articles, research, and personal observations, the main cause of project failure is not technology or hardware, but inefficient communication stemming from lack of effective communication between team members, incomplete business analysis, imprecise requirements, and vaguely formulated business objectives.