Software Development Methodology

1753 Words8 Pages

CHAPTER 3
METHODOLOGY
1. Introduction
This section will discuss the different types of methodologies.

1.1 Methodology
A methodology is a system of broad principles from which specific procedures maybe be derived to solve different problems within the scope of a project. The purpose of a methodology is to allow controlling of the entire management process through effective decision making as well as problem solving, on the other hand, ensuring the success of specific processes, approaches, methods and techniques(McConnell 2010).

1.2Traditional Software Development Methodology
This section will discuss some of the earlier software development models, for example:
1.2.1 Waterfall Model
“The waterfall model was introduced in the 1970s by Win …show more content…

Being an emerging agile methodology, it offers a number of practices, values and principles thatdevelopers are advised to adopt in order to run a software development project. Extreme Programming was targeted at small co-located teams developing non-critical products. It has been suggested that the early adopters of agile methods have been small high-tech companies. However, it has currently been proven at many companies of all different sizes and industries worldwide (Malik Hneif 2009).

Extreme Programming provides a list of simple, specific, and values that guide the software development process throughout the four main phases of software development namely planning, coding, designing and testing. The main purpose is to deliver what the customer needs at the time it is needed. In addition, one of the main reasons of its success is its ability to accept changes at anytime during the development. Extreme programming emphasizes teamwork, experiences from all stakeholders are employed to meet specific goals and within the given constraints (Malik Hneif …show more content…

It fails to address usability needs of the users as product owners keep their focus mainly on business issues and forget about usability(Malik Hneif 2009).
There are some benefits of using the scrum methodology such as daily meetings makes it possible to measure individual productivity which therefore leads to the improvement in the productivity of each of the team members. It is a lightly controlled method, which insists on frequent updating of the progress in work through regular meetings, which means there is a clear visibility of the project development. It is through the regular meetings that issues are identified well; they are discussed and hence can be quickly resolved(Mahalakshmi & Sundararajan 2013).
It can be difficult for the scrum master to plan, structure and organize a project that lacks a clear definition. In addition, the daily scrum meetings and frequent reviews require substantial resources. A successful project depends on the maturity and dedication of all participants, as well as their ability to maintain consistently high levels of communication through each backlog(Mahalakshmi & Sundararajan

More about Software Development Methodology

Open Document