Giving your clients the opportunity to voice their opinions after conducting business with you is a great way to express your interest in continuing to work with them. Just make sure you're earnest in hearing their thoughts and that you don't simply think this is accomplished with a survey alone.

Johanna Rothman received a variety of responses to her recent writing on agile architecture. In this article, she attempts to clarify her case for having an architect on some—but not all—agile programs, depending on a number of factors.

We all know what it’s like to be frustrated with someone else when that person isn’t being as responsive as we would like. It’s especially easy to do when our own work or responsibilities are on the line. In this tale from Naomi Karten, she shows that a lack of response doesn’t necessarily mean a lack of care and explains how very important it is to have the full story before you get too worked up.

“Business analyst” is not a distinct role on Scrum or other agile teams. And yet, the goal for the team—to deliver high-valued product needs—requires strong business analysis skills. Ellen Gottesdiener and Mary Gorman describe the vital analysis work needed reach the goal, regardless of role.