Some managers who have not been technical in a while have forgotten—or may never have known—that software product development is about learning. They may have spent all of their learning time at a keyboard. Especially if they learned alone rather than in teams, they would not know how to assess a team member’s need for alone time after intense team time.
By implementing configuration flags as part of the initial stages of development, engineers imbue all new features with the capability to leverage system-level strategies, such as multivariate testing, beta testing, and “emergency toggles.” In this article, Noah Sussman describes some battle-tested strategies to implement and leverage configuration flags in production.
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.
One of the most difficult personality types to deal with is the person who always seems mistrustful of others. Sometimes, this lack of trust is justified, but sometimes it is really a manifestation of some dysfunctional personality issue. This article will help you understand this situation and suggest a few ways you can deal with difficult personality types like the paranoid person.
We all know we need to do retrospectives. And sometimes, it feels as if we go through the motions. Maybe with dialogue sheet retrospectives, we don’t have to. Here, Allan Kelly shares his perspective on dialogue sheet retrospectives.
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.
Mariya Breyter explores the role of a ScrumMaster and whether or not one can work effectively when working remotely. If the ScrumMaster is not available to orchestrate product delivery, bridge any gaps, and remove any obstacles, a product will never be delivered—even worse, a wrong product will be delivered. In order to achieve this understanding, the ScrumMaster must show value to the team as a natural leader, no matter if he is onsite or remote.
Leslie Sachs writes on how employees in many companies have essentially learned to no longer raise their concerns because there is no one willing to listen, and—even worse—they may have suffered consequences in the past for being the bearer of bad tidings. Leslie refers to this phenomenon as learned complacency.
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.
Matthias Bohlen shares with us the importance of self organization. As a manager, you must set time or organizational boundaries that serve a purpose and let team members do what they think is appropriate and necessary within those boundaries.