Stand up meeting in agile software development Dissertation

substantiate up meeting in agile computer software victimisation - Dissertation ExampleHowever, from the development of software methodologies, some classical or pioneering methods evolved. These are now known as the handed-down approaches to the development of software. The traditional approach to software development involves the definition of requirements which leads to the architecture or design of the development fulfil and murder (Dean and Gravel, 2009 p12). This is a basic model that was steeped in convenience and the ability to complete things according to a archetype pace. The Committee on Certifiable Dependable Software Systems criticized the traditional approaches to software development for lacking the earth for strong and rigorous analysis (2011). This is because these methods were very basic and depended on the software developers testing and brass without the inclusion of other external parties. Another criticism put forward against the traditional approach t o software development is that it assumes that this approach is based on a facility of rigidly defined assumptions that will be used as the guideline throughout the process (Kathleen, 2007). This method usually lacks the flexibility that can encourage in the adjustment of the processes in the course of the software development (Kathleen, 2007). Thus, if the assumption of a given process is not appropriate, the project is prone to failures as it proceeds. A textbook example of the traditional software development approach is the waterfall model which contains rigid steps and levels that the software developer goes through in the completion of a software development process (Segal, 2010). The inherent issues in these systems have led to the creation of more combat-ready and flexible approaches to software development like the Agile Software Development methodology. The literature review will critique these approaches and methods and evaluate them in relation to relevant issues and matters that are define each of them. This will set the parameters for the discussions on stand meetings and scrum meetings in dynamic approaches to software development. 2.1 Waterfall uprise The Waterfall Approach to the development of software happens a sequential process where activities follow each other downwards, like a waterfall hence the name. The sequence applied in this methodology involves the analysis of requirements, design, coding, validation (testing), installation, and maintenance (Royce, 1970). Projects that follow the Waterfall Approach are normally segmented according to the different phases, although some of these phases might circuit during the process. The Waterfall Approach maintains tight resource control, and operations remain limited to the provisions as place in the requirement analysis. The major setback to this method remains the assumption of having all essential problems and requirements determine at the beginning. This is a challenge because at t he onset, there are many opportunities and threats that might not be clear to the software developers. Unpredictable problems encountered during the project lifetime result in project failure. The method contains many activities which must be undertaken through a series of activities identified at the beginning of project. Figure 1 The Waterfall Approach (Source Snyder, 2002) Figure 1 shows the fundamental stages and phases of the Waterfall Approach to software development. It depicts the sequential phases that a software develope