SCRUM Methodology and Agile Processes in the Development Process - Assignment Example

The development process in is greatly misunderstood and assumed method that be completed successfully through planning and cost estimation. This is not always true as in real practice. SCRUM methodology makes an assumption that the systems development process is quite uncertain and complex that can only be gauged and determined as the net progression. Introduction Scrum is a management, upgrading, and maintenance methodology for production prototype or for current systems. It reuses the existing design and code which is a typical feature for object-oriented development as a result of the available class libraries. SCRUM views the systems development process as a collection of actions that integrate known workable mechanisms and procedures with the best development team to develop systems. Since these actions are loose, controls to handle the process and underlying risks are used. SCRUM is a typical upgrade of the commonly utilised incremental object-oriented development cycle. Software product version releases are planned based on the following variables: • Customer requirements - identifies how the current system requires enhancement. • Time pressure – identify what time frame is needed to secure a competitive advantage. • Competition – what is the competition up to, and what is required to best them. • Quality – what is the needed quality level, given the above variables • Vision – what modifications are needed at this stage to attain the system vision • Resource – what labour and funding are available. These variables form the inceptive plan for a software enhancement project. Nevertheless, these variables also vary during the project. Waterfall Methodology Although waterfall methodology makes it compulsory the use of undefined processes, it has a huge drawback. Its linear nature gives it this large drawback. The process does not provide way of responding to unanticipated output from any of the transitional stages. This problem is overcome by Spiral methodology where each of the waterfall phases is terminated with risk assessment and prototyping activities. The main reasons as to why the waterfall methodology to software development is not suitable Requirements (user and system) are not completely realised prior to commencement of the project The users of the system have the tendency to know exactly what they want after a release of an initial version of the software product. It is characterised with scope creep where requirements change frequently in the course of the software construction process, The emergence of new tools and technologies make implementation approaches very unpredictable. Spiral methodology This method is analogous to the peeling of onion layers that corresponds to users deciding whether to send prototype back to preceding phases or termination of the development process. Spiral methodology stages and stage processes are linear. Requirement analysis and design activities are conducted in requirements phase and design phase respectively with each of the stages comprising of linear, precisely and clearly communicated defined processes Iterative methodology This is an improvement on the Spiral method. Each of the iteration comprises of all phases in standard Waterfall model. Each of these iterations covers a single set of parsed functionality. The overall project deliverable expected is subdivided into designated subsystems, each with clean interfaces. This method allows one to test the feasibility of a subsystem and its technology in the inceptive iterations. Later iterations improve the the project while increasing the speed of delivery. This method increases flexibility, has a better cost control and checks delivery of systems. Nevertheless, the Iterative method is also linear as underlying development processes are still defined and linear. Each of the development technologies improve on another with no significant change. Both the Spiral and Iterative methods implement a risk control techniques for handling uncertainty in the results. Scrum Methodology Both Waterfall and Spiral development methodologies determine the product context and deliverable requirement during the early phases of the project. On the other hand Scrum and Iterative methodologies make plan for the context and broad deliverable requirements prior to the commencement of the project, and subsequently change the deliverable in the course of the project precisely depending on the environment. Underlying development processes in Scrum methodology are not to fully defined and therefore utilises control procedures for high flexibility. The major disparity between the defined/ typical development methodologies (that include Waterfall, Spiral and Iterative) and empirical (Scrum) model is that the Scrum scheme assumes that the initial processes (analysis, design, and development) in the Sprint stage are uncertain. As a result a control procedure is used to handle the uncertainty and control the risk. The end result for is high flexibility, responsive and reliable results. Features of Scrum methodology The Planning (first) and Closure (last) phases comprise of precisely defined processes, where all items that includes inputs, outputs and processes are well documented. The details on how to executive these processes are precisely and clearly communicated and the flow of activities cascades with some iterations in the initial phase. The second phase; Sprint phase is a factual process. Most of the processes in the sprint stage are not defined or controlled. This phase acts as a black box that needs external controls. Consequently, these controls as well as risk management requirement are included in each of the iteration of Sprint phase to evade confusion while achieving the best possible flexibility. Sprints are flexible but not linear. It is therefore important that precisely and clearly communicated process knowledge is first utilised; otherwise trial and error method is utilised to create process knowledge. Sprints are utilised for the eventual change of the final software product. At this stage the project is open and exposed to environmental ramifications and therefore needs to close. This shields the project from competitive, time, quality, and financial pressures. The deliverable can be altered at any given time in both of the Planning and Sprint stages of the project The deliverable set in the course of the project depends on the environment. Table 1 a comparison of different development methodologies Feature Waterfall Spiral Iterative/Agile SCRUM Defined Needed Needed Needed Planning processes Closure phases Final product Confirmed Confirmed Set in the course of the project Set in the course of during planning during planning project Project cost Set during planning Vary partially Set in the course of the project Set in the course of the project Date of completion Decided during planning Vary partially Set in the course of the project Set in the course of the project Responsiveness to environment Planning Planning primarily At end of each iteration Throughout Team flexibility, creativity Limited - Manual documentation approach Limited - Manual documentation approach Limited - Manual documentation approach Limited - Manual documentation approach Knowledge transfer Training necessary prior to project Training necessary prior to project Training necessary prior to project Teamwork during project Chances of success Low Medium low Medium High Scrum Methodology Phases Scrum methodology has the following phases: Pregame Planning: This stage involves backlog items, their approximate cost and time that determines the the definition of a new release. It comprises of conceptualisation and analysis for scenarios where new systems are currently in development. If a system currently in operation is being upgraded, this phase comprises of reduced analysis. Architecture : Gives the design of how the backlog items will be carried out. This phase includes system architecture adjustments and an elevated design. Game •Development Sprints: entails the development of functionality for the recent release, with time, quality, cost, requirements, and competition variables being factored in. This phase comes to a close when the interaction with these variables occurs. The system requires numerous iterative developments that bring change/modify the system Postgame • Closure- encompasses formulating a procedure for release and final documentation of the product. It also involves pre-release testing and release. Closure The project manager ensures that the project is completed in time and within the specified budget. This phase enables the management to evaluate the variables. If a balance exists amongst the variables the release is declared closed. This closure phase makes the developed product ready for a general release. Several activities occur under closure and this includes: Integration, system testing, user manual documentation and both training and marketing materials preparation. Advantages of the Scrum Development Methodology Typical software development methodologies address the issue of unpredictability of both the development and external environments at the beginning of the enhancement cycle. A more current methodology such as the spiral model and its closely associated versions are restricted in the extent to which they respond to scope creep as the project progresses. In contrast, the Scrum development methodology is completely capable of being changed throughout the stages. It implements control techniques for creating a plan for an early product version release as well as managing variables while still the project is running. This renders it possible for enterprises to alter the deliverables and the project at any stage of the development process and still create a suitable product version release. In Scrum development methodology, the software developers are free to add and implement other requirements they think are fit as the environments changes. It involves small, coordinated units of developers sharing a common pool of development process knowledge. This environment provides a rich ground for maximum training amongst the developers. Scrum development methodology is an Object Oriented technology; therefore the classes, objects or the software features provide a distinct and manageable environment. Programs of procedural orientation are not suited to Scrum technology due to the tight coupling of the interface modules. There is an exception to this where procedural codes are implemented in clean interfaces with high cohesion and firm data orientation. Disadvantage or limitations of scrum Agile development process Scrum methodology is an unstructured process of working It is not suitable for large-scale enterprises Scrum methodology lacks proper documentation and artefacts It is devoid of problem solving stage Scrum development methodology is not architecture-oriented It lacks the development of prototypes or conceptual models in the initial phases of the development process. Conclusion SCRUM methodology and Agile Processes focuses on rapid iterations, continuous releases and changing user requirements as the users are incorporated and play key part in the development process. In practice, developing this particular artefact (Traffic Control Simulation and Monitoring system is found to be a very viable way of solving problems associated with product development. The project is delivered on time and surpasses the expectations the stake holders. In the course of the development the team is intensive. The programmers feel a sense of accomplishment together with enjoyable and satisfying experience. Read More