Agile Development focuses on the end product rather than the documentation. In this approach, the frequent user involvement during the construction phase can result in “scope creep”. Sometimes users keep asking for additional changes, thereby resulting in an exponential increase in the workload of the developers (Barrett, 2012). This in turn results in administration problems during the construction phase. Moreover, agile method does not pin down the cost of the project during the inception phase. The decision making is based on fictitious data that covers each iteration in the Agile Model.

Due to the frequent user involvement in Agile Development one cannot foresee what the output of the project is going to be. Therefore fixing the cost for the project and even scheduling the project becomes laborious (Waters, 2007). Documentation is done during the transition phase. Due to the variable scope in Agile Development, documentation is challenging. In addition whenever a new feature has been added based on an user request; the documentation team must be briefed about the change. Miscommunications between the Development, Test and documentation team can lead to out of date user manuals, functional requirements et al (Barrett, 2012). Agilists feel that documentation must also been done during the construction life cycle of the project (Ambler et al., 2012).

In Agile Methodology products are delivered frequently and each feature needs to be signed off; this makes the UAT testing lengthy and cumbersome, moreover this also requires that resources at the product owner’s end are available when there is a release. During the construction phase testing is done for each iteration, furthermore testing resources are needed throughout the construction iterations of the project resulting in higher costs (Waters, 2007). This phase is lengthy but it removes all the risks that would result in a failure of the project.

Agile methodology is developer centric and focuses on the working software and sometimes even overlooking the strategic goals that needs to be decided during the inception phase of the project (Goldsbury, 2010). The project can also derail if the customer is not clear about the result. In addition only Senior Developers are key decision makers regarding the course of the project rather than the management. Thereby, resulting in frequent architectural repetitions that affects the project schedule. These issues can be avoided if the project management gets involved in the project and stays up to date with the project by using the appropriate agile software tools.

The other area of concern is the daily standup meetings which runs for hours. This can sometime affect the work schedules of the developers, QA specialists and Analysts (Barrett, 2012). The frequent iteration also results in developer burnouts which takes a toll in the project outcomes. These issues that occur during the construction phase can be overcome if there is a proper design in place, and when the teams are well connected by communicating with each other. Agile must be adopted for projects that are developed incrementally.