This article is part of our ongoing series on Agile Business Analysis principles. So far, we’ve covered four principles: See the Whole, Think as a Customer, Analyze to Determine What is Valuable, and Get Real Using Examples. In this post, we’ll explore the fifth principle, Understand What is Doable, which emphasizes the importance of setting realistic goals within Agile initiatives by balancing ambition with constraints and team capabilitites.

Principle 5: “Understand What is Doable”

The principle of “Understand What is Doable” encourages business analysts (BAs) and Agile teams to focus on what can realistically be achieved within current constraints, such as time, budget, and technology. This principle isn’t about limiting creativity but about grounding ideas in a rational assessment of what is feasible given available resources. By focusing on what’s doable, Agile teams can better manage stakeholder expectations, reduce risks, and ensure that whatever a team promises to the business is achievable and sustainable.

Why It Matters for Business Analysts

For Business Analysts, this principle helps maintain a balance between innovation and practical execution. In Agile, where initiatives are based on iterative development and incremental delivery, understanding what can be realistically achieved allows business analysts to avoid over-committing or under-delivering.

This principle stresses that requirements should be clear and attainable. It also gives Agile teams focus and helps producing meaningful progress. When business analysts understand what is doable, they will continuously analyze the need and work out solution options that can satisfy this need within given constraints.

Practical Tips for Business Analysts

1 Evaluate Resources and Constraints: Consciously assess available resources—time, budget, technology, and team capabilities. This assessment helps in setting realistic goals for each iteration.

2 Evaluate Risks: Consider the evolving context of the change and risks to refine and prioritize the product backlog items.

3 Prioritize the Backlog: Regularly refine the backlog to focus on tasks that add value and can be realistically delivered by the team within given constraints. Don’t waste time on impossible.

4 Engage with Stakeholders: Collaborate with stakeholders to align on what’s feasible. Ensure they understand the constraints and rationale behind prioritizing certain features or deprioritizing others.

Stay Tuned!

In the next article, we’ll dive into the sixth principle, Stimulate Collaboration and Continuous Improvement. We’ll discuss how collaboration drives progress and innovation in Agile environments, helping teams achieve success.

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