Johanna Rothman bucks conventional wisdom and writes that it's not always cheaper to hire workers from places where the wages are less expensive. When you have fractions of teams in remote places, you could have communication problems and other issues that will increase the cost for every feature.

While many teams can use help structuring their conversations, some teams also need some way to know whether the structured conversations that have taken place have provided sufficient information. Kent McDonald explains how using visualization boards can help in these situations.

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.

Payson Hall writes that it is dangerous to describe or assess IT investments without context. As an IT professional, you need to work with accounting subject matter experts and take the time to develop more robust business proposals for your IT system that are explicit about costs and assumptions.