Project scope management using developers’ tools and practices

The article focuses on project management activities in the field of information technology (hereinafter referred to as IT) which is the object of the study, and the tools used to manage the scope of such projects (the subject). Scope primarily refers to requirements for a product, service, or other project deliverable. The article identifies the challenges organisations face when using the most popular requirements management systems – local electronic documents in conjunction with email systems as well as wiki-type systems. These include, in particular, contradiction and inconsistency in requirements. The Docs as Code approach and DocOps (Documentation Operations) practices are highlighted as solutions to these challenges, defining a set of developers’ tools and practices to manage the scope of IT projects.

1. Gorelits, N. K., Kildishev, D. S., & Khoroshilov, A. V. (2019). Requirements management for safety-critical systems. Overview of solutions. Proceedings of ISP RAS, 31(1), 25–48. (In Russian). https://doi.org/10.15514/ISPRAS-2019-31(1)-2

2. Guzenko, O. I., & Baliabin, D. S. (2025). AI agents in project management: opportunities, limitations, and integration strategies. Journal of Project Management, 1(2), 71–78. (In Russian). https://doi.org/10.26425/3034-6916-2025-1-2-71-78

3. Lobzov, A. V. (2023). Application of docs as code approach for financial risk minimisation. Financial risk management journal, 1(73), 72–78. (In Russian). https://doi.org/10.36627/2221-7541-2023-1-1-72-78

4. Wiegers, K., & Beatty, J. (2013). Software requirements (3rd ed.). Microsoft Press.