Experience shows that Agile project management tools such as Atlassian Jira capture the state of EAS projects by relying solely on expert judgement that is not supported by any knowledge model. Therefore, the assessment of project content against strategic objectives and business domain features are not supported by any tool. This is one of the reasons why Agile project management still does not provide sufficient EAS project delivery results. In order to address this problem, the Enterprise Application Software (EAS) development using Agile project management is summarized in a conceptual model. The model highlights the knowledge used and indicates its nature (empirical or causal digitized). The modified Agile management process we have developed and described in previous works is based on causal knowledge models that supports EAS development and Agile management processes. The purpose of this article is to specify knowledge repository to ensure the Agile management solutions of an EAS project are aligned with strategic goals and business domain causality. It is worth noticing that strategic goals have been identified and specified as capabilities using some enterprise architecture framework (NAF, MODAF, ArchiMate, etc.). The novelty of the proposed method is incorporating the business domain causal knowledge modelling approach into the Agile project management process. The causal knowledge unit is considered as a Management Transaction (MT), which includes closed loop dependence of its components. The modified Agile activity hierarchy (theme, initiative, epic, user story) defines the required content of their mutual interactions. An important new results obtained are the conceptual model of causal knowledge base (KB) and specification of enhanced Agile management tool components: project management database and project state assesment knowledge base. Causal KB includes specification of causal knowledge unit (MT metamodel) and specifications of traditional and causal Agile hierarchy meta-models. These conceptual models define the causal knowledge components necessary to evaluate the state of Agile activities in the EAS development project using intelligent Agile project management tool.

The Agile approach and tools are popular for the management of Enterprise Application Software (EAS) development. This article focuses on the issue of inconsistency between strategic business objectives and the functionality of the software developed. Agile management tools lack the functionality of EAS project activities coordination. This article aims to rethink Agile project management using the causal modelling approach. A causal model of Agile project management using a management transaction (MT) concept was developed. The notion of the space of processes was used to identify the MTs location along the axes of aggregation, generalization, and time and to formalize their interaction specifications. Taxonomy of the coordination meta-types and types was developed using the identifiers of the MTs. The modified Agile activities hierarchy was developed, and vertical and horizontal causal interactions between Agile activities were identified. This modified Agile management model helps to consistently track the integrity of EAS project content. Complexity indicators were introduced to evaluate the EAS project complexity and their average and normalized values are presented. Additional attributes in the Agile management tool Jira are proposed. Monitoring mismatch between strategic business objectives and development activities content helps to improve the success of EAS projects delivery.