Agile Development Case Study

Maintenance phase, if the consumer finds errors and problems; the company will make necessary changes and upgrades to meet customer demands and loyalty. Agile development is heavily based on mathematical computations (Agile Methodology). It focuses on rapid delivery for functional components. Task at hand can be prioritized by the organization (Agile Methodology). If another emergent task appears the plan can be reprioritized and the information can be replanned for the future. The status of the project can be evaluated by team, through each phase of the build. Agile methodologies are open to change and transformation. This can be achieved by constant feedback from the users. Some work might need more priorities than others. In that case, …show more content…
The downfall of Agile is utilization of Scrum. According to Freeman, Scrum cannot be succeeding without a Scrum Master, an individual high qualified and experienced with scrum. Most team members would require at least six months acquiring the knowledge (Freeman). This sometimes can be frustrating for individuals with a background in waterfall method because agile is a highly complicated iterative process. Without an experienced scrum master, training for fellow team members is not going to be efficient. An inexperienced scrum leader will to be able to guide his team through the development phase. Experience is very important factor for this methodology. Inexperienced developers who lack the knowledge of scrum may produce complaints and give agile a bad review to prospective developers. Scrum can only provide maximum output only if everyone is in full collaboration. Another disadvantage is that Independent developers may find it be unnecessary and will slow down the entire process (Freeman). Scrum is supposed to be management tool for agile projects, which gives an overall view of the project (Freeman). Not every project needs scrum. Scrum can only be utilized by large companies who develop large scale products (Ex-apple, Microsoft, and Samsung). These companies only invest in large-scale projects and require a lot more collaborative work than small companies. Small companies cannot utilize scrum and other agile methods because most of the developers are autonomous. According to Freeman, small companies with small scale projects have very little collaborative effort because usually team consists of two or three members. These small companies may want to utilize Personal Kanban or a lean market approach. As mentioned earlier, the great perk of agile is that it allows flexibility. But the flexibility can cause team members developing bad behaviors (Gilley). Carelessness