Agile Methodology Report

811 Words 4 Pages
Report – Investigation into ‘Agile Methodology’
The purpose of this report is to explain the benefits and drawbacks of adopting an Agile methodology, in particular ‘SCRUM’; providing an overview of this framework. In addition, this report will also conclude with a recommendation of actions for the company according to the findings.
Agile Methodology:
The Agile methodology is created to address and compliment business need for software in shorter timeframes. Using the Agile framework such as ‘SCRUM’, provides a more responsive and flexible approach in accordance to client needs. Therefore, unlike the traditional Waterfall methodology, the SCRUM framework is evidently more iterative.
As a result of being more iterative, the timeline of a SCRUM
…show more content…
The SCRUM master keeps the team focus and shields them from external interference;
5. At the end of each Sprint, the team will have an executable product of business value;
6. To finish, the team will identify how they could do things better/ further development for the overall application.
Benefits:
There are number of benefits of using the SCRUM methodology, especially in the environment that our company is in. These benefits are:
1. Using the SCRUM methodology will allow our company to grow with each iteration.
2. Each iteration we sent out to the market will gain a business value of its own.
3. As producing a product using the SCRUM methodology generally requires a shorter amount of time, it will give the company the potential to be the ‘first mover’.
4. Due to the nature of our business, updates and demands are very hard to keep up with. Using the SCRUM methodology will allow us to manage the project easier, as well as creating the flexibility and adaptability our products need.
5. It allows us to nurture and improve the involvement with customers. Allowing the company to upgrade and prioritise changes according to our customer
…show more content…
These are:
1. Given that this methodology is designed to progress along with customer needs. It is often that the project will create a ‘scope creep’; forcing the company to prolong the product.
2. Unlike the Waterfall approach, more expertise is needed for a project using this methodology. This is because a clearer and in-depth communication is needed, due to the decrease in time for each iteration.
3. Due to the concept that the project is likely to be prolonged due to the development of each iteration. It is likely that it could force the business to lose track of its initial objective for the product.
Recommendation:
While the Waterfall methodology is generally agreed to be the traditional approach to use as a project lifecycle. After the findings, it is recommended that the company should take on the SCRUM methodology approach for all future projects. It is clear that using such methodology will be most beneficial for the company, especially in the case of software development. Using this approach will allow the company to focus

Related Documents