Skip to content

7. Techniques

Agile Extension to the BABOK® Guide

It can be challenging to select the right technique for the situation to get the desired outcome. The following chart provides general guidance on when to choose a specific technique. Please note that many techniques can be used successfully in a variety of contexts. An agile business analysis practitioner uses his or her domain knowledge, experience, individual competencies, and creativity when selecting the appropriate technique for the desired outcome. The purpose of this chart is to provide a starting point when determining which technique might be useful in a given context.

A team is a group of people working together for a shared goal – this team could be at the Strategy, Initiative, or Delivery Horizon. Stakeholders outside the team are customers, subject matter experts, or people internal or external to the organization who are invested in the team's success but are not part of the team.

The context identifies when each technique is most useful to get the desired outcome.

  • Communication identifies what techniques facilitate shared understanding, collaboration, and increased communication.

  • Process Analysis is about understanding the process to identify ways to improve.

  • Product Management or Refinement is about what solution the team is delivering.

  • Requirements Management includes techniques specifically helpful in facilitating and improving the requirements life cycle.

  • Understanding Your Customer is about identifying, understanding, and clarifying who the customer is and what they need and value.
Table 7.0.1: Selecting the Right Technique