Please enable JavaScript.
Coggle requires JavaScript to display documents.
SOFTWARE METHODOLOGIES (Waterfall (In general, this type of methodology is…
SOFTWARE METHODOLOGIES
Waterfall
In general, this type of methodology is used to manage projects in an orderly manner, and by deadlines, for a given project.
The budget is agreed with the specific provider from the beginning of the project. In this way, there will no longer be changes in the money to be paid that could harm one of the parties. This also guarantees that the agreed economic amount was received safely.
V Model
It is an SDLC model where execution of processes happens in a sequential manner in a V-shape. It is also known as Verification and Validation model.
-
Spiral Model
Spiral Model is a combination of a waterfall model and iterative model. Each phase in spiral model begins with a design goal and ends with the client reviewing the progress.
Construction & Release: It includes testing, coding and deploying software at the customer site.
System Evaluation: Evaluation of software by the customer. Also, includes identifying and monitoring risks such as schedule slippage and cost overrun
SCRUM - Pros
-CREATIVITY AND INNOVATION: Scrum approach emphasizes creativity and innovation to maximize the business value of the solution.
-LOWER COSTS: reduced overhead resulting from reducing unnecessary documentation and control requirements.
IMPROVED QUALITY: The developers know that quality is not “someone else’s responsibility”.
-It provides continuous feedback: requires daily check-ins for progress reports, there is always feedback.
-
It is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development team.
Communication: Software development is more or less a team sport and no team can function effectively without proper communication.
Simplicity: XP is all about using the simple things that have proved to work. Why simplicity is a major factor to avoid wastage so as to only do the things that are absolutely necessary.
Feedback: Constant feedback concerning the previous efforts of the team allows the team to clearly identify the areas that need revision as well as improvement.
Courage: Kent Beck in his book "Extreme Programming Explained" defines courage as the preference of action based principles whereby the results are not harmful to your team.
Respect: If your team members want to communicate with each other effectively, accept as well as provide constructive feedback and work with each other properly, and cohesively work together, then they'll need to learn how to respect each other as a whole.