SCRUM, DSDM, and Lean Software Development - Essay Example

? Assignment 2: Using SCRUM, DSDM, and Lean Software Development Overview Different invaluable software has become an integral part of modern societysince past two decades. Likewise, there exists several software development processes as compared to the past. The software development process is considered to be the foundation in the field of software engineering as it provides an opportunity to develop software using cost effective approaches, along with saving time and helping in framing quality products. Agile software development is considered to be one of the most commonly used approaches assumed by the large industries while developing software. It is essentially a group of software development approaches constructed on collaborative and incremental development procedures. The prime reason behind adapting this procedure of developing software by major software developers in the modern context is that it provides an opportunity where requirements and solutions evolve through collaboration amid self-organizing and cross-practical teams. Additionally, it supports the implementation of adaptive planning, advancement development and delivery, along with a time boxed interactive approach (Keith, 2002). The main objective of this study is to conduct a descriptive analysis showing how projects are planned and are executed in SCRUM, Dynamic Systems Development Model (DSDM) and Lean Software Development that are being used for agile development and project management. 1. a. SCRUM Scrum is determined to be a simple yet incredibly powerful set of principles and practices that help teams provide products in short cycles, facilitating fast feedback, constant enhancement and rapid amendment to change. The development process is mainly centered on a flexible holistic product development approach where all the members engaged in the development task work mutually to reach a common goal. It is considered to be a popular agile project management method that has introduced the concept of empirical process control for managing complex and changing software projects (Szalvay, 2004). Examples. Companies such as Scrum Alliance, Inc. use scrum approach to develop their software (Scrum Alliance, Inc. 2013). b. Dynamic Systems Development Model (DSDM) Dynamic Systems Development Model (DSDM) is based on Rapid Application Development (RAD), heavily relying on prototyping and providing a framework for delivering quality solutions quickly. Since its origin in 1994, DSDM is considered to be one of the most extensively used frameworks for developing software in the United Kingdom (UK). The vital reason behind the increasing adoption of DSDM as one of the major approaches while developing software is that it defines nine core principles that are essential for the success of software. For instance, the approach mainly focuses on developing software through ensuring viewable active participation of the users, teaching design groups for making vital system related decisions and ascertaining that all kinds of changes during the process can be reversible (Abrahamson, Salo, Ronkainen, & Warsta, 2002). Examples. For instance, in DSDM, it has been viewed that the system first prepares a prototype and then empowerment. The next step is assigning the role to the different personnel associated with the process roles and suitable DSDM applications are followed while developing software (Howard, 1997). c. Lean Software Development In lean software development, the principle of the approach not only identifies the quality concern of the software that is being developed but also helps in recognizing and providing an opportunity to mitigate other issues that act as a barrier in the developing process. This facilitates in improving the quality of the software each time it is being built (Dasari, n.d.). Example. In lean software development, organizations use a decentralized form of decision making. Companies such as Microsoft are viewed to be using this form of agile development model for developing software (Microsoft, 2013). 2. Three benefits and three trades-offs for each of the following frameworks are stated hereunder: SCRUM Benefits. 1. The major advantage of this project management approach it that it aids in creating a balance amid the four variables i.e. cost, schedule, requirements and quality of the software that is being developed. 2. It helps in delivering products within a scheduled time. 3. The overhead price in terms of procedure and administration is marginal thus leading to a faster and cost effective result (Szalvay, 2004). Trade-offs 1. If the associated project related tasks in this approach are not executed according to the plan, it can result in incurring huge cost. 2. It is good for small firms as it works with small team. 3. If any of the members resigns during the process, it results in creating considerable negative effects on the project (Szalvay, 2004). DSDM Benefits. 1. It facilitates in eliminating waste of resources. 2. It helps in delivering the product faster. 3. It aids in empowering the team. Trade-offs 1. It at times delays the process. 2. Lack of proper coordination could bring about certain mistakes in the entire process. 3. Lack of proper planning. Source: (Abrahamson, Salo, Ronkainen, & Warsta, 2002). Lean Software Development Benefits. 1. Easier and flexible process as compared to other software development approaches. 2. Rapid and simplified process. 3. Small footprint for easy completion of task. Trade-offs. 1. Success of the project depends on how coordinated the different programs are. 2. The role of business analyst is given prior importance. 3. The clients may change anything at any moment which acts as a barrier in completing the project within the speculated period. Source: (Dasari, n.d.). 3. There are certain potential obstacles for using these frameworks. These include: SCRUM In this approach, the clients may change their preferences at any time which may act as a barrier in the process. DSDM In DSDM approach, it has been viewed that the entire process is dependent on the analyst, if the analyst resigns, it can act as an obstacle (Dasari, n.d.). Lean Software Development In this approach, it is vital that the every small detail must be addressed to the client which at times involves a lengthy process. This may act as an obstacle in the process. 4. SCRUM Example. David was allocated as a SCRUM product owner of a new software development project. One of his first tasks was to start requirement engineering. Accordingly, David wrote down all the vital aspects of the software that is to be developed and discussed them with all the people associated with the project. After collecting all the high level cases and requirements, David wrote them all into the Scrum Product Backlog, accordingly estimation and prioritization session with the architects and certain senior developers was conducted. Generation of a rough estimation and identification of prior factors of the project were performed. Breaking down the high-level requirements into smaller parts was also performed as a key task. Subsequently, he called for the first Sprint Planning Meeting. On the first sprint planning meeting, backlog items were present from highest to lowest. In this step, all the aspects were studied and the item that cannot be realized in this sprint was kept separate. At the end, a meeting was conducted and the tasks were written down on the task board. On day 2 of the sprint meeting, a short description of the things that have been achieved was conveyed and any obstacle that would hinder a task was determined. Similarly, meetings were conducted each day to identify flaws in the development process and measures were taken to mitigate them. However, it was viewed that the owner added new items to the backlog based on the recent customer meetings conducted in which resulted in the commencement of Sprint 2 (International Scrum Institute, 2013). However, as a project manager, it can be said that an alternative plan of the changes made would have been prepared which could be used as a referral in future. Additionally, as a project manager, a survey would have been conducted to list out the entire licenses that need to be renewed or replaced with the new once. Figure: Scrum Phases and Sprints (International Scrum Institute, 2013) DSDM Example. With reference to the determined obstacle, it can be viewed that in DSDM, the entire process is dependent on the analyst. Therefore, if two-three people are assigned in the same position, the task would be known amongst them which would help in maintaining the work even if any individual resigns. For instance, it has been viewed that in many scenarios organizations assign two persons in the same position to divide the work and to ensure that the organizational operational procedures are not affected if any one resigns (Arizona National Guard, n.d.). Lean Software Development Example. With regard to the identified obstacles, it can be viewed that informing the client is very essential after a fixed period which would help in completion of the project effectively. For instance, if an agreement is fixed with the client that the status of progress would be provided after the completion of a milestone then it would help in successful and efficient completion of the project (Project Agency, n.d.). References Arizona National Guard. (n.d.). Position Management Handbook for Supervisors/Managers. The Position Management Study, 1-19. Abrahamson, P., Salo, O., Ronkainen, J., & Warsta, J. (2002). Agile Software Developmnent Methods. VTT, 1-100. Dasari, R. K. (n.d.). Lean software development. Retrieved from http://www.projectperfect.com.au/info_lean_development.php Howard, A. (1997). A new RAD-based approach to commercial information systems development: the dynamic system development method. Industrial Management & Data Systems, 97(5), 175-177. International Scrum Institute. (2013). Introduction to scrum - a real world example. Retrieved from http://www.scrum-institute.org/Introduction_to_Scrum_A_Real_World_Example.php Jonsson, H. (2012). Lean software development: A systematic review. Retrieved from http://www.idt.mdh.se/kurser/ct3340/ht12/MINICONFERENCE/FinalPapers/ircse12_submission_18.pdf Keith, E. R. (2002). Agile Software Development Processes A Different Approach to Software Design. New York University, 1-25. Microsoft. (2013). Lean software development. Retrieved from http://msdn.microsoft.com/en-us/library/vstudio/hh533841.aspx Project Agency. (n.d.). Project management. Retrieved from http://www.businessballs.com/freematerialsinword/project%20management%20tips.doc Scrum Alliance, Inc. (2013). Who uses Scrum and why? Retrieved from http://www.scrumalliance.org/why-scrum/who-uses-scrum Szalvay, V. (2004). An Introduction to Agile Software Development. Danube Technologies, Inc., 1-11. Read More