# Conceptual Framework for Implementing Temporal Big Data Analytics in Companies
## 6 Verification of the Proposed Conceptual Framework
### Participant Perspectives
#### 6.2.5 Outcome 5: The Practical Value of the Proposed Framework  
Question:_Can the proposed TBDA implementation framework and TBDA analytics ecosystem be applied in practice? The one that would be created as a result of using the proposed framework._  
Even if the proposed solution is at the conceptual level, it is always created for use in practice. Therefore, it was important to get to know the opinions of the focus participants on the practical use of the proposed framework and the TBDA ecosystem created with it. The most interesting citations:  
_It all depends on what details we put in there._  
_It all depends on the technological stack with which we deal in a given company._  
_The model is quite general and only going down to a more detailed level will give us an answer about its usefulness in practice._  
_It seems that it is OK, of course the matter of promoting the solution and marketing remains._  
Again, from the theoretical and conceptual point of view, the proposed framework has been highly rated. Again, the question of its practical implementation has been pointed out. It should be noted that managers, on par with academics, anticipate the practical usefulness of the presented solution, but the next step must undoubtedly be an attempt to implement it in business, at least at the proof-of-concept level. 6.2.6. Outcome 6a: Strengths of the Proposed Framework  
Question: _What are the advantages of the proposed framework?_  
The next question was about what advantages of the proposed framework were perceived by the focus participants. The answers turned out to be extremely interesting. Here are the selected ones:  
_\"The most important advantage is that it was made.\"_  
_\"The most important advantage is that one has to think about TBDA.\"_  
_\"The great advantage is that thanks to this framework we know how to work, what to stick to, thanks to such framework we are able to make the project coherent and carry it out efficiently.\"_  
_\"The biggest advantage of the framework is considering the temporal aspect.\"_  
It seems that the greatest advantage of the proposed framework is its focus on the temporal dimension, as the panelists pointed out. They concluded that the framework constructed in this way forces its users to pay attention to the time dimension in big data analytics. This is in line with the earlier statements of the debaters who, with great appreciation, adopted the basic assumption of the framework, which is to recognize the time dimension as the basic one for BDA. Participants reiterated the framework's consistency. 6.2.7. Outcome 6b: Weaknesses of the Proposed Framework  
Question: _Do you see any weaknesses of the proposed framework?_  
An important issue was whether the participants saw any weaknesses or flaws in the framework they praised:  
_\"Disadvantages will probably come out when going down to these lower levels of detail.\"_  
_\"For me, resignation from the waterfall approach is a certain limitation.\"_  
_\"Failure to include feedback loops.\"_  
_\"At the beginning of the framework, I lacked these purely business needs: why implement TBDA at all.\"_  
_\"Lack of feedback loop, and of machine learning (ML).\"_  
Undoubtedly, considering the comments of the respondents on this issue as well as earlier, the next step in the development of the conceptual framework must be the addition of a feedback loop, enabling the improvement of the TBDA artifacts created. It should also be examined whether it would be possible to include the waterfall approach in the framework, and if so, how and to what extent. In the last part of the focus study, participants were free to comment on the topics they considered important, and which were not included in the moderated discussion. First of all, they referred to the method of combining lean principles with agile principles proposed in the framework. There was a very interesting discussion about whether it is possible to combine Scrum with Kanban. Two positions were clearly outlined. First--Scrum cannot be combined with Kanban.