Yes, the Agile methodology has some limitations, some of which are as follows: 

• Poor resource planning. Predicting the amount of effort REQUIRED to finish a task is difficult. It becomes even more challenging in the case of huge projects because it is difficult to estimate the overall effort necessary. 
• It's not always possible to devote enough TIME and attention to the project's design and documentation. 
• There is a scarcity of documentation. Documentation occurs throughout an Agile project and is frequently "just in time" for generating the output, rather than from the start. As a result, it gets less detailed and frequently falls to the bottom of the priority LIST. 
• The output is fragmented. INCREMENTAL delivery may help get goods to market quicker, but it's also a major drawback of Agile. This is because when teams are working on distinct components in different cycles, the final product is OFTEN fragmented rather than a single entity. 
• There is no conclusion in sight. It's easy to get side-tracked offering new, unanticipated functionality because Agile needs less planning at the start. Furthermore, because there is never a clear idea of what the "finished result" looks like, projects have no clear end. 
• The final project may not meet the customer's expectations if the client's requirements are not well grasped. As a result, the customer will be dissatisfied. 
• Only a leader with extensive knowledge of Agile methodology is capable of making critical judgments. Members of the team with minimal or no experience do not participate in decision-making and hence do not have the opportunity to expand their knowledge. 
• Measurement is difficult. Because Agile works in chunks, tracking progress necessitates looking over multiple cycles. As a result, you won't be able to specify many KPIs at the start of the project.