People & Teams

It's the perennial question: Is there a role for business analysts in an agile environment? It stems from the fact that the Scrum Guide defines only three roles on the team: the development team, the ScrumMaster, and the product owner. Business analysts often feel like they have to justify their role. But the BA provides significant value. Here are three main ways they can make a difference on an agile team.

The rapid rate of technological change is forcing enterprises to reinvent themselves and provide more flexible approaches, so agile transformations are key. However, knowing that agile is important is one thing, but the ability to properly implement the main principles, tools, and techniques of agile is another. Let’s explore time-tested agile principles that will help your organization build innovative products that customers love.

Implementing agile often means throwing out the rulebook when it comes to how teams work, how projects are organized, and even what the office floor plan looks like. This can be a difficult transition, but it's nothing to fear if you can anticipate the challenges and plan accordingly. Here are six of the greatest challenges teams face when implementing agile, along with some tips on how to avoid them.

People have different cultural backgrounds, habits, beliefs, interests, capabilities, knowledge, skills, and temperaments. When put together on a team, they can’t always be governed by a rulebook to become self-organized. The dynamics among them have to be understood to recognize the anti-patterns first. Here are six anti-patterns that must be avoided and remediated to help teams move toward self-organization.