agile

Articles

 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
Decorating Cakes Can Teach Us about Iterations What Decorating Cakes Can Teach Us about Iterations

Kent McDonald shares with us a story about decorating cakes and how that relates to doing agile the right way. To be truly effective, teams need to focus more on the need to reflect and adapt, and then figure out the best way to do that in their environment without worrying about whether they are doing it exactly right.

Kent J. McDonald's picture Kent J. McDonald
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
Agile Is Cheaper, Right? Agile Is Cheaper, Right?

Kenneth Grant explains whether or not being agile is really as cheap for an organization as its proponents claim it to be. Agile’s relentless focus on business value and just-enough work can help teams identify waste—or poor return on investment (ROI) requirements—and gives them the opportunity to change it or leave it out all together.

Kenny Grant's picture Kenny Grant
Attacking Silos with DevOps Attacking Silos with DevOps

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.

Leslie  Sachs's picture Leslie Sachs
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
Building a Backlog for Legacy System Changes

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.

Kent J. McDonald's picture Kent J. McDonald

Pages

AgileConnection is a TechWell community.

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