How Much Scope Does a Project Need? - Lessons for Business Analysts from a Classic Tale
"Beware the barrenness of a busy life." – Socrates
In How Much Land Does a Man Need? by Leo Tolstoy, we follow the story of Pahom, a peasant driven by ambition and greed. Offered the chance to claim as much land as he can encircle on foot in a single day, Pahom sets out, consumed by the allure of endless opportunity. But in his relentless pursuit, he overextends, collapsing and dying just as he stakes his claim. In the end, all the land he truly needs is a six-foot plot for his grave.
This powerful allegory has profound lessons for business analysts navigating the intricacies of project scope, stakeholder demands, and organizational ambitions. Much like Pahom’s pursuit of endless land, a project with unchecked scope or misaligned objectives risks collapsing under its own weight.
Let’s unpack the wisdom hidden in Tolstoy’s timeless tale and explore how business analysts can navigate the fine balance between ambition and practicality in project management.
Lesson 1: The Allure of Expanding Scope
Pahom's downfall begins with his inability to recognize the dangers of wanting more than he can manage. Similarly, in project management, scope creep is the siren call that tempts stakeholders and teams alike. A simple project to implement a Customer Relationship Management system can snowball into a sprawling initiative encompassing sales automation, data analytics, and social media integrations—all because stakeholders keep pushing for “just one more feature.”
As a business analyst, your role is to anchor the project to its core objectives. Always ask, does this addition align with the business goals? Will it deliver real value, or is it just another shiny object?
Actionable Insight:
Create a robust scope management plan and involve stakeholders in prioritizing features. Use tools like MoSCoW analysis (Must-have, Should-have, Could-have, Won't-have) to keep everyone focused on what truly matters.
Lesson 2: The Power of Stakeholder Alignment
Pahom's fatal mistake is thinking he’s in complete control. He underestimates the external forces—his own greed, the vastness of the land, and even the setting sun. In projects, misaligned stakeholders can become those external forces, pulling the project in conflicting directions.
Imagine working on a system upgrade where the Information Technology department prioritizes security while the marketing team demands faster deployment at any cost. Without alignment, the project becomes a tug-of-war, doomed to fail.
Actionable Insight:
Conduct stakeholder analysis to understand motivations, priorities, and concerns. Regularly facilitate alignment meetings to ensure everyone stays on the same page. Like Pahom surveying the terrain, knowing your stakeholders’ environment is critical to success.
Lesson 3: Ambition Without Strategy Leads to Ruin
Pahom sets out with no plan other than to claim as much land as possible. His ambition blinds him to practical limits, and he fails to pace himself. Similarly, projects launched without a clear strategy often flounder. You’ve seen it before: organizations dive into digital transformation without a roadmap, only to find themselves drowning in unmet deadlines and spiraling costs.
Actionable Insight:
Every project needs a clear vision, measurable goals, and a well-defined strategy. As a business analyst, use tools like SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) and project charters to ensure the team has a structured plan before setting out.
Lesson 4: The Cost of Ignoring Risks
In his greed, Pahom ignores the obvious risk: the setting sun. He pushes his boundaries too far and pays the ultimate price. In project management, ignoring risks can be just as catastrophic. For example, failing to account for resource constraints or potential system downtimes can derail even the most well-planned projects.
Actionable Insight:
Develop a risk management framework for every project. Identify potential risks early, assess their impact, and prepare mitigation strategies. Remember, it’s better to walk away with less land—or a smaller project scope—than to risk losing everything.
Lesson 5: Knowing When to Stop
Tolstoy’s story leaves us with a sobering truth: knowing when to stop is as important as knowing when to start. In the business world, some projects simply aren’t worth pursuing, either because they lack alignment with strategic goals or because the cost outweighs the benefits.
Imagine being asked to spearhead a project to implement an expensive Artificial Intelligence solution that provides minimal Return on Investment. As a business analyst, it’s your duty to question whether the project should proceed. Saying “no” can save your organization from unnecessary losses.
Actionable Insight:
Be willing to challenge stakeholders with data-driven insights. Use cost-benefit analysis to evaluate whether the proposed initiative is worth the effort. Sometimes, the best decision is to walk away.
Conclusion: The Six-Foot Rule for Projects
Tolstoy’s story reminds us that Pahom ultimately needed only six feet of land—far less than what he chased. The same principle applies to projects: focus on what truly matters and avoid the temptation of endless expansion.
As a business analyst, your role is to act as the compass, steering projects toward their true north. By managing scope, aligning stakeholders, strategizing effectively, mitigating risks, and knowing when to stop, you can ensure that your projects deliver real value without collapsing under the weight of ambition.
The next time you find yourself in a high-pressure project, ask yourself: How much scope does this project truly need? The answer might just be the key to its success.
Author: Olam Osah
Olam Osah is a Senior Business Analyst and thought leader renowned for his deep academic and practical insights. With a PhD in Information Systems from the University of Cape Town and Honours and Masters degrees from the University of the Witwatersrand, Johannesburg, Olam makes complex concepts accessible and actionable. His compelling articles and thought leadership pieces are a must-read for business analysts navigating the ever-evolving world of business information systems. Reach out to him at [email protected].