The first value in the Agile Manifesto is “Individuals and interactions over processes and tools,” and for many teams, being located in the same place facilitates these interactions. However, being part of an effective, collaborative team is less about location than it is about motivation and good practices.
Some people believe branching and pull requests are inherently bad. True, branching done poorly can slow down a team, but advocating for avoiding branching altogether can lead you to ignore the more important goal of an agile process: rapid integration of changes. First, make sure you're considering the right metrics.
When organizations are distributed across multiple locations, it brings questions about how much each location should have a unique identity relative to the larger company. While a theme of “we are one” is common, it’s better to embrace the differences and work toward being a cohesive group that celebrates diversity.
The values of the Agile Manifesto, while written to apply to software, can form a basis for an adaptive approach to any project. Going from specific to general and inspecting and adapting along the way are great design ideas, no matter what you’re working on. Here's how to use feedback to take agile beyond software.
One of the primary questions for agile teams adopting a new approach such as Scrum is whether to start with principles or practices. Sometimes the best way to learn principles is indirectly, through practice. Experiences are a great way to learn, and sometimes they even teach you skills without your realizing it.
People typically think of training classes as passive activities, where the instructor talks and the others listen. But experiential learning, where you learn through hands-on activities and then reflect on the experience, often gets the lesson to stick in people's brains better. Consider using interactive lessons.
Gerald Weinberg's work inspired many to be better engineers and better leaders. Although he’s no longer with us, his message about the role of people in building quality software lives on in his writings and in those who have learned from him. Here, Steve Berczuk recalls some of Jerry Weinberg's most influential books.