This post is part of an ongoing series exploring the 7 Agile Business Analysis Principles outlined by the IIBA (International Institute of Business Analysis) Agile Extension to BABOK. Following our discussion on the first principle, “See the Whole,” this post dives into the importance of adopting a customer-centric mindset with the second principle, “Think as a Customer.”

Principle 2: “Think as a Customer”.

In the world of Agile Business Analysis, this principle emphasizes the importance of a customer-centric approach. Rather than focusing solely on the needs of a business, this principle encourages business analysts (BAs) to incorporate the voice of the customer and adopt their perspective ensuring that every feature developed meets customer expectations and adds value.

Why It Matters for Business Analysts

In an Agile environment, the ability to deliver value quickly and iteratively is essential. By thinking as a customer, BAs can better understand what features are most valuable to the end user, enabling the team to prioritize work that will have the greatest impact. This approach helps in avoiding the development of unnecessary features and ensures that the final product aligns with user needs and expectations.

The “Think as a customer” principle is about empathy. Daniel H. Pink said:

“Empathy is about standing in someone else’s shoes, feeling with his or her heart, seeing with his or her eyes. Not only is empathy hard to outsource and automate, but it makes the world a better place.”

It is deeply rooted in empathy, as when applied, this principle requires business analysts to put themselves in the customer’s shoes, understanding their needs, frustrations, and desires. By developing empathy, BAs can better anticipate what customers truly value, enabling the team to create solutions that resonate and address real-world problems effectively.

Practically, understanding the customer’s perspective also helps BAs in refinement activities. When the customer perspective is clear and drives the requirements, the team focus is on the development and delivery of those stories with the highest benefit in the shortest time possible.

Practical Tips

1 Engage directly with customers: Regular interactions with customers can provide insights into their pain points, preferences, and behaviors. Use techniques like surveys, interviews, and feedback sessions to gather this information.

2 Create personas: Develop detailed customer personas to represent different segments of your audience. They help model and understand customer needs and experiences.

3 Implement feedback loops: Establish mechanisms to gather feedback from customers throughout the development process. This can help in making quick adjustments to features based on real user experiences, ensuring continuous alignment with customer needs.

“Thinking as a customer” helps business analysts bridge the gap between business objectives and user satisfaction, making it easier for Agile teams to deliver products that resonate with their audience.

Stay Tuned!

In our next post, we will explore the third Agile principle, “Analyze to Determine What is Valuable,” and discuss how business analysts can ensure that teams know what are high-priority items. Stay tuned to learn more about how this principle supports the Agile business analysis!

Mini-course: Introduction to the BABOK® Guide V3

Do you want to learn about the Business Analysis Body of Knowledge from the International Institute of Business Analysis™, but you don’t have time to follow a class? Enroll for this free-of-charge mini-course “Introduction to the BABOK® Guide.” In five weeks, you receive ten compact lessons via e-mail about IIBA® and the knowledge areas of the BABOK.

References

Agile Extension to the BABOK® Guide v2, ISBN-13: 978-1-927584-07-1