How Impact Mapping Gives You Multiple Options to Pursue How Impact Mapping Gives You Multiple Options to Pursue

In this article, Lisa Crispin explains how impact mapping allows your team to generate multiple options to pursue. Be creative with your solution experiments. You won’t solve all your problems or achieve all your goals quickly, but small wins and steady progress mean you’ll enjoy the journey of continually improving how you work.

Lisa Crispin's picture Lisa Crispin
 Thinking Up Front about Agile Requirements An Agile Approach to Thinking Up Front about Requirements

Thinking about interacting with the customer at the start of the project? Who would argue against that? Well, it depends on what you call it. It also depends on whether you then do it without the benefit of the rest of the project team. Here, Ulrika Park helps us see what an agile approach to thinking about the requirements might look like.

Ulrika Park's picture Ulrika Park
 Dialogue Sheet Retrospectives Are Important Why Dialogue Sheet Retrospectives Are Important

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.

Allan Kelly's picture Allan Kelly
What Are Your Metrics Trying to Tell You? What Are Your Metrics Trying to Tell You?

Joanne Perold writes that you cannot just look at the numbers; the context behind the data is often far more valuable. Metrics can tell a compelling story or provide meaningful information to anyone who wants to pay attention, but when the focus is only on the number, it can be a disaster.

Joanne Perold's picture Joanne Perold
Fix Your Agile Project by Taking a Systems View Fix Your Agile Project by Taking a Systems View

Kathy Iberle writes that when working on a project, you should take a systems view, which allows you to see the whole development system at once. When you put on your “systems view” glasses, you’ll see that you need to deal with the whole system, not just a single team’s part of it.

Kathy Iberle's picture Kathy Iberle
Problem Solving with Impact Mapping Problem Solving with Impact Mapping

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.

Lisa Crispin's picture Lisa Crispin
Following Agile By the Book Be Truly Nimble Instead of Just Following Agile by the Book

People often ask, “Can we apply agile to fields outside of software?” In this article from Marco Peredo-Saavedra, you can read how a construction project applied agile to its work with Marco as the product owner/customer. Take inspiration, and read his lessons. Then, go apply them!

Marco Peredo-Saavedra's picture Marco Peredo-Saavedra
Be an Effective Leader When Working Remotely Can a ScrumMaster Be an Effective Leader When Working Remotely?

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.

Mariya Breyter's picture Mariya Breyter
A Software Team's Journey to Agile A Software Team's Journey to Agile

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.

John Lynch's picture John Lynch
What Position Do You Play in Software? What Position Do You Play?

Micheleen Merritt explains that as an agile coach, you need to take into account all of the participants of a team, not just the developers. If you aren’t acknowledging the quality assurance analysts, business analysts, and product owners, you aren’t coaching the whole team.

Mickey Merritt's picture Mickey Merritt


AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.