Project Estimator: A Role-Based Production-Estimation Model for Creative and Game Development Pipelines
Keywords:
bottleneck analysis; capacity planning; creative pipelines; game development; pre-production; production estimation; role-based modelAbstract
Early-stage estimation remains one of the weakest points of creative production and game development. Teams commit to scope, budgets, and deadlines before the structure of the required work has been examined, and a single aggregate figure of hours conceals how the load falls across professional disciplines. This article formalizes a role-based production-estimation model represented as a task-role effort matrix, in which task quantities and per-unit role hours are used to derive role-level workloads, and describes its free, publicly available web implementation, Project Estimator. The model decomposes a project into task types, multiplies each type by its planned quantity, assigns the professional roles that participate in producing 1 unit, and attaches per-unit hours to each role. From these inputs, the model derives the total production volume, workload per discipline and per specialist, projected duration, required team composition, cost at given hourly rates, deadline feasibility, and production bottlenecks. Project duration is determined by the maximum role-level duration under the specified staffing and working-time assumptions, which distinguishes the model from aggregate schedule reasoning that divides total effort by total headcount. The argument follows a review format. The model grew out of more than 20 years of production practice; its spreadsheet predecessor was presented at an industry conference in 2021, and no primary usage data are reported. A worked example with a hypothetical 25-character project illustrates how the role-based view exposes a bottleneck that an aggregate estimate would hide. A structured comparison positions the model against task-management systems and software-estimation methods, and identifies its niche at the stage preceding project launch. Limitations regarding empirical validation and the quality of expert input are discussed, along with directions for future verification.
References
[1] L.-E. Dubois and J. Weststar, “Games-as-a-service: Conflicted identities on the new front-line of video game development,” New Media & Society, vol. 24, no. 10, pp. 2332–2353, 2022, doi: 10.1177/1461444821995815.
[2] C. Politowski, F. Petrillo, G.C. Ullmann, and Y.-G. Guéhéneuc, “Game industry problems: An extensive analysis of the gray literature,” Information and Software Technology, vol. 134, Art. no. 106538, 2021, doi: 10.1016/j.infsof.2021.106538.
[3] L. Pieva and M. Bernardino, “Trends and research in digital game project management: A systematic literature review,” Journal on Interactive Systems, vol. 14, no. 1, pp. 533–545, 2023, doi: 10.5753/jis.2023.3196.
[4] D. Hawey, “Understanding game art practice beyond technical expertise: A qualitative study,” in Proc. 20th Int. Conf. Foundations of Digital Games (FDG ’25), 2025, Art. no. 7, pp. 1–12, doi: 10.1145/3723498.3723724.
[5] B. Alsaadi and K. Saeedi, “Data-driven effort estimation techniques of agile user stories: A systematic literature review,” Artificial Intelligence Review, vol. 55, no. 7, pp. 5485–5516, 2022, doi: 10.1007/s10462-021-10132-x.
[6] J.T.H. de A. Cabral, A.L.I. Oliveira, and F.Q.B. da Silva, “Ensemble effort estimation: An updated and extended systematic literature review,” Journal of Systems and Software, vol. 195, Art. no. 111542, 2023, doi: 10.1016/j.jss.2022.111542.
[7] T. Dingsøyr, F.O. Bjørnson, J. Schrof, and T. Sporsem, “A longitudinal explanatory case study of coordination in a very large development programme: The impact of transitioning from a first- to a second-generation large-scale agile development method,” Empirical Software Engineering, vol. 28, no. 1, Art. no. 1, 2023, doi: 10.1007/s10664-022-10230-6.
[8] H. Edison, X. Wang, and K. Conboy, “Comparing methods for large-scale agile software development: A systematic literature review,” IEEE Transactions on Software Engineering, vol. 48, no. 8, pp. 2709–2731, 2022, doi: 10.1109/TSE.2021.3069039.
[9] S. Hartmann and D. Briskorn, “An updated survey of variants and extensions of the resource-constrained project scheduling problem,” European Journal of Operational Research, vol. 297, no. 1, pp. 1–14, Feb. 2022, doi: 10.1016/j.ejor.2021.05.004.
[10] Z. Bahroun, R. As’ad, M. Tanash, and R. Athamneh, “The multi-skilled resource-constrained project scheduling problem: A systematic review and an exploration of future landscapes,” Management Systems in Production Engineering, vol. 32, no. 1, pp. 108–132, 2024, doi: 10.2478/mspe-2024-0012.
[11] Games Gathering, “Dmitrii Yeremenko – Tvorcheskii protsess dlia ‘fabrik’ po proizvodstvu igr [The creative process for game production ‘factories’],” Internet: https://www.youtube.com/watch?v=eKxTmGOcpZ0, Dec. 1, 2021 [Nov. 1, 2026].
[12] D. Yeremenko, “Project Estimator,” Internet: https://www.projecttoolestimator.online/ [Nov. 1, 2026].
[13] L.-E. Dubois and A. Chalk, “Service withdrawal: The uncertain future of the games-as-a-service model,” Convergence: The International Journal of Research into New Media Technologies, vol. 31, no. 2, pp. 479–499, 2025, doi: 10.1177/13548565241256888.
[14] Y. Lamine and J. Cheng, “Understanding and supporting the design systems practice,” Empirical Software Engineering, vol. 27, no. 6, Art. no. 146, 2022, doi: 10.1007/s10664-022-10181-y.
Downloads
Published
Issue
Section
License
Copyright (c) 2026 Dmytrii Yeremenko
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
Authors who submit papers with this journal agree to the following terms.
