This final paper describes the project plan of an application for managing hunting grounds. Opening it is an analysis of problems and advantages of solutions, in which the arguments are the quality of the idea of such a venture. Through the analysis of current problems and future benefits it becomes clear that this is a profitable operation as a long-term resolve or minimizing action on currently present deficiencies. Furthermore, presented is the structure itself, the manner of implementation, the importance, benefits, and requirements for the skilled person to carry out hunting management through regulations of the Hunting Act in order to achieve a better understanding of the topic of this work by the reader. After us to be informed about hunting management basics and what are its basic components and features, we enter into the creation of the project plan for the application that will fully follow the regulations of the Act and related legal acts step by step up until the recommendation for user interface design. To be able to make a good application that is used simply and intuitively, we use the well-known methods of collecting user requirements and then their analysis of which the initial appearance of the end product is somewhat clearer. When we found out what the user needs, we draw attention to the project team, and before the start of the application development requirements are detailed as definitions of tasks within the process of realizing particular request. The tasks are easier to handle within a team of developers than to the requirements as in this case 11 units. Upon completion of the requirements analysis and the interpretation of the described and assessed tasks, we can create an iterative development plan and thus easier to manage time and resources available to us. Projects that have in the past been extremely successful leave behind the best practices for future projects that are yet to be executed, so another step within the project found its place before coding the application - designing the system architecture. Important for several reasons, such as reducing the cost of the project, obtaining a clearer picture of the final product before production and primarily due to reduced volume of work in order to reduce the risk of adverse outcomes within the development. In the end recommendations are described for user interface design to make the product easier to use, realizing additional savings of time through an intuitive and consistent interface and creating the impression of superior products and superior contractor.