Do your team members have a problem they can’t solve? Maybe it’s time to try impact mapping. In this article, noted author Lisa Crispin shows us how she uses impact mapping to solve problems. Impact mapping takes a lot from other brainstorming and planning tools, such as mind mapping and story mapping.

Many professionals, while having expertise in their technical niche, are sometimes less than perfect at communicating effectively with colleagues from other departments. This can result in departments failing to work effectively together; these departments resemble silos more than a collaborative and cohesive organization. This article will help you identify and understand some of the reasons why teams operate in silos and what you can do to change that.

Kent McDonald writes that teams often assume that they cannot split their changes into small stories because the resulting stories would not provide value. What they fail to realize is that they can split these bigger changes into smaller changes and gain value by showing their stakeholders, getting feedback, and incorporating that feedback in their continued development.

Did you ever wonder if a team needs some prerequisites before transitioning to agile? In this true story, John Lynch shows us the story of a team who teetered on the brink of dysfunction and then was able to create its foundation so team members could begin their agile transition.