Technique 23 of 31
Zmey Planning
Transform your estimation into a legendary masterpiece.
- Estimation
- Planning
- Complexity Assessment
In short
Zmey Planning is an Agile estimation technique based on a three-headed dragon from Slavic mythology. Each head is one dimension of a task: complexity, uniqueness and ambiguity. The team rates each with coins worth 0, 1, 2, 5 or 10, as in Planning Poker, and the summed Zmey Tax becomes the estimate and a basis for velocity.
For: Agile teams estimating and planning work
The Problem
Estimation is essential in Agile planning, yet teams often do it by habit rather than necessity.1 Traditional methods provide structure but don’t always capture complexity, leading to inaccurate forecasts and wasted effort.2 Through curiosity, we explored estimation beyond numbers, uncovering its deeper challenges—complexity, novelty, and ambiguity.3
The Experiment
Merging various techniques,4 we developed the Zmey Planning Technique, inspired by Slavic mythology. Here, the Agile team battles a three-headed dragon—each head symbolizing complexity, uniqueness, and ambiguity. Instead of fearing uncertainty, teams tackle it directly, breaking down work, anticipating obstacles, and refining estimates with confidence.5
What Are the Three Heads of the Zmey?
To achieve more accurate estimation for any given task, we must delve into the depths of its specifics. The three heads of the Zmey—complexity, uniqueness, and ambiguity—hold the key to unlocking a comprehensive estimation. Let’s explore what each head encompasses:
1. Complexity678
- Assess the technical intricacy of the solution, including data structures, algorithms, and integrations.
- Evaluate the impact scope on existing system components and interfaces.
- Address non-functional requirements and cross-cutting concerns such as performance, security, and scalability.
- Review current technical debt and code quality in affected areas.
- Consider architecture and design constraints, including technology stack limitations.
2. Uniqueness91011
- Determine the novelty of the task and the level of creativity, innovation, and problem-solving it demands.
- Evaluate the acquisition of new knowledge or competencies required for its execution.
- Account for external pressures, such as client expectations, business demands, and social influences.
- Anticipate the dynamics during task execution, encompassing interruptions, task switching, handovers, and communication needs.
- Identify any dependencies on external parties or other teams.
- Anticipate potential problems and obstacles related to infrastructure, working environments, and other relevant factors.
3. Ambiguity1213
- Ascertain the completeness of requirements, ensuring all aspects of the developed functionality are covered.
- Verify the accuracy of requirements, aligning them with real business needs.
- Eliminate ambiguity in requirements, fostering clarity and preventing room for interpretation.
- Ensure consistency between requirements and existing functionalities or other established criteria.
- Consider the ease of testing, validating, and verifying the developed functionality post-implementation.
What Tribute Is Demanded by the Zmey?

Within the realm of legends, the Zmey, in exchange for peaceful coexistence, demands a tax from villages in the form of gold.
In our realm of task estimation, the Agile team levies a similar toll. By assessing three crucial characteristics—complexity, uniqueness, and ambiguity—we determine the Zmey Tax required for each task.
To conduct this evaluation, we employ special coins designed exclusively for this purpose.
Each coin bears a face value based on estimation scales proven effective in Agile practices:14 0 (requiring minimal or no tax), 1 (low tax), 2 (moderate tax), 5 (high tax), and 10 (extremely high tax). These values follow an exponential progression to reflect how uncertainty increases with complexity.15

For every characteristic of the task, a coin is designated and offered as tribute to the Zmey. These coins are then combined, yielding the total tax for the task. For instance, if complexity is assigned a coin value of 1, uniqueness a value of 2, and ambiguity a value of 5, the Zmey Tax would amount to 8.
How Do We Calculate the Zmey Tax?
The estimation and planning process using the Zmey Planning technique closely resembles that of Planning Poker.16
- Introduce the functionality to be developed to the Agile team.
- Distribute the unique coins, granting each participant a total of 15 coins—3 of each face value (3 × 0, 3 × 1, 3 × 2, 3 × 5, and 3 × 10).
- Anonymously, each participant assesses the complexity tax for the designated functionality by selecting a coin. Upon completion, participants place their chosen coin face down on the table. When all are ready, the coins are simultaneously revealed. If values differ significantly (more than one step apart), participants discuss their reasoning to understand the differences in perspective. The team must reach consensus on a final value before proceeding. Once agreement is reached, the agreed-upon coin value is recorded.
- The previous step is replicated for both the uniqueness tax and the ambiguity tax, ensuring comprehensive estimation.
- In the heart of the table, all the coins are gathered to form the collective sum of the tax to be paid to the Zmey. To determine the final estimation, this sum is divided by the number of participants.
- Transform the Zmey Tax into a practical planning tool by tracking your team’s historical performance. Calculate your team’s average velocity in terms of Zmey Tax points completed per iteration. For example, if your team typically completes tasks totaling 20 Zmey Tax points per sprint, use this as a baseline for future capacity planning. Monitor and adjust this baseline as team efficiency improves or conditions change. Compare similar Zmey Tax values across different tasks to refine future estimates and identify patterns in your team’s delivery capabilities.
References
- M. Usman, E. Mendes, and J. Börstler, “Effort Estimation in Agile Software Development: A Survey on the State of the Practice,” in Proceedings of the 19th International Conference on Evaluation and Assessment in Software Engineering (Association for Computing Machinery, 2015), 50–59, http://dx.doi.org/10.1145/2745802.2745813.
- A. Trendowicz and R. Jeffery, Software Project Effort Estimation: Foundations and Best Practice Guidelines for Success (Springer, 2014).
- K. Conboy, B. Fitzgerald, and L. Mathiassen, “The Complexity Challenge in Modern Software Development,” Information and Software Technology 151 (2022): 106985.
- M. Jørgensen, “Estimation Techniques for Agile Development Projects: A Review of Empirical Research,” Journal of Systems and Software 156 (2019): 110403.
- Y. Petit and B. Hobbs, “Uncertainty Management Strategies Throughout the Project Life Cycle,” International Journal of Project Management 39, no. 2 (2021): 159–70.
- A. Abran, Software Project Estimation: The Fundamentals for Providing High-Quality Information to Decision Makers (IEEE Computer Society Press, 2015).
- N. A. Ernst and J. Mylopoulos, “On the Perception of Software Quality Requirements During the Project Lifecycle,” in Requirements Engineering: Foundation for Software Quality, ed. R. Wieringa and A. Persson (Springer, 2010), 143–57.
- P. Kruchten, R. L. Nord, and I. Ozkaya, “Technical Debt: From Metaphor to Theory and Practice,” IEEE Software 29, no. 6 (2012): 18–21.
- J. Highsmith and A. Cockburn, “Agile Software Development: The Business of Innovation,” IEEE Computer 34, no. 9 (2001): 120-127.
- T. Chow and D. Cao, “A Survey Study of Critical Success Factors in Agile Software Projects,” Journal of Systems and Software 81, no. 6 (2008): 961-971.
- T. DeMarco and T. Lister, Peopleware: Productive Projects and Teams (Addison-Wesley, 2013).
- D. M. Fernández et al., “Naming the Pain in Requirements Engineering,” Empirical Software Engineering 22, no. 5 (2017): 2298–338.
- K. Pohl, Requirements Engineering: Fundamentals, Principles, and Techniques (Springer, 2010).
- M. Cohn, Agile Estimating and Planning (Prentice Hall, 2005).
- K. Moløkken-Østvold and M. Jørgensen, “A Review of Surveys on Software Effort Estimation,” Journal of Systems and Software 70, no. 1-2 (2004): 37-60.
- V. Mahnic, “A Case Study on Agile Estimating and Planning Using Scrum,” Electronics and Electrical Engineering 111, no. 5 (2011): 123–28.
From Never Stop Experimenting by Stavros Stavru, PhD, illustrated by Iva Grueva. Published here in full on .
How to cite this technique
Stavru, S. (2025). Zmey Planning. In Never Stop Experimenting: 31 Real-World Experiments for Continuous Growth in Work and Life. Morgan James Publishing. https://neverstopexperimenting.com/techniques/zmey-planning
Related techniques

24 · Product & delivery
The Fatware Matrix
Your product should undergo a regular diet and exercise to stay in top shape.

01 · Foundation
The NSE Ratio
Uncover the optimal frequency for engaging in new experiments.

16 · Leadership & teams
The Decision Compass
Assess and enhance the efficiency of your decision-making.
One new experiment, now and then
New techniques, real-world results and behind-the-scenes stories from Stavros. No spam; unsubscribe anytime.