Using SCRUM, DSDM, and Lean Software Development - Essay Example

USING SCRUM, DSDM, AND LEAN SOFTWARE DEVELOPMENT Using SCRUM, DSDM, and Lean Software Development Affiliation Analyze how projects are planned and executed under the following frameworks and provide an example for each: Scrum Scrum is very well-known agile software development methodology. Scrum software development starts with the customer’s story. This story can be anything which a customer uses to describe their requirements. For instance, end-user needs to add a new contact in address book, in order that he can interact with the person in the future by email or postal mail. These stories are further explored by the software development team. In this scenario, the customer does not provide the full, thorough clarification of things and requirements that need to be completed in a project, however the burden shifts on the shoulders of software development team for the reason that the software development team better understands how to solve the problem they are provided with. Hence, in the Scrum software development a sprint planning meeting involves the discussion on the required results. In the Scrum methodology, the software development process is measured through a series of sprints. Normally, these sprints are delivered within a duration of two weeks. In this scenario, a meeting is conducted in the beginning of each sprint, in which project team determines what requirements they can complete, and then develop a sprint backlog on the basis of this analysis as well as a list of the actions needs to be carried out during the sprint (Cohn, 2012; Rees, 2013). DSDM Dynamic Software Development Methodology (DSDM) looks a great deal similar to the eXtreme Programming technique, however in this methodology the concentration is paid to the design of a software product. This methodology suggests that software development teams should complete just adequate design up front at the initiation stage of software development with the purpose of determining and clarifying the structure of the complete solution as well as to develop an agile plan for delivery of the project. For instance, a client wants the software development to develop an ATM software, it is a good practice to develop some part of the design in the early stage of the software development. In this scenario, software development team can better understand the requirements and feasibility of software. This design can include only some basic functionality of the system. Hence, this practice starts up the basis for effective software development and delivery. In addition, the design phase of the DSDM differs with the analysis and design phase of the traditional waterfall software development because in the traditional software development a detailed design is completed while in DSDM only some details are covered (Craddock, Roberts, Richards, Tudor, & Godwin, 2012). Lean Software Development Methodology Basically, the lean methodology is widely used in production industries. However, with the passage of time its usage has been increased for the software development as well. This methodology is aimed at reducing the waste in the software development. This is done by sensibly dividing projects into small chunks with the purpose of identifying what components or requirements of a software system are inessential and can be eliminated. For instance, in case of an ATM software, an initial analysis can be carried out to determine what components can be excluded such as additional buttons or graphics but basic functionality should not be compromised. After that in light of the requirements the size of a team is determined and desired resources are provided to the team. After that the project is broken into smaller components to make the management simple. For instance, in case of the ATM project first component can be “view credit” and second can be cash withdraw and so on (Duggan, 2013). 2. Highlight three (3) benefits and three (3) trade-offs for each of the following frameworks. Advantages and Disadvantages of Scrum Like all other agile software development methodologies it requires a continuous response from the user. With Scrum software development, it is easier for the software development team to deliver a quality product at a scheduled time. In addition, because of small sprints and continuous customer’s response, it becomes simple for the software development to deal with the changes (Uhlig, 2013; Adell, 2011). This methodology is believed to be the major cause of scope creep for the reason that until there is a certain delivery or final date, the project stakeholders keep demanding that new functionality should be added. In the same way, if the project management team fails to define a task effectively, the cost and time estimation will not be correct. In this scenario, a task can take a number of sprints. In addition, in order to complete a project successfully, team members should be committed (Adell, 2011). Advantages and Disadvantages of DSDM Dynamic software development methodology focuses on the actual needs of the business. Additionally, it ensures the delivery of a project with high quality. In addition, like other agile software development approaches it also develops products in iterations (Mejillano, 2011). In view of the fact that this methodology involves strict rules and principles, so they can make it difficult for the project team to work with as compared to other agile software development approaches. Additionally, it requires the software development team to develop the initial design of the system which can take additional time and cost. In addition, the effective use of this methodology requires extensive knowledge and experience (Mejillano, 2011). Advantages and Disadvantages of Lean Software Development As this methodology ensures the elimination of wastes prior the initiation of the project, which can increase the overall effectiveness of the development process. In this scenario, the speed of the software development increases and the cost and time required to complete a software development reduces. Additionally, the delivery of a software application as soon as possible gives the software development team a definite advantage because with this methodology a software development team can add more functionality in a minimum time span (My-Project-Management-Expert, 2009). The lean software development methodology highly depends on the coordination of the team members so the success of a project relies on the discipline of the team members and their technical skills. In this scenario, if a software development firm does not have staff members possessing good expertise to balance each other, it can face serious problems. Additionally, in order to get fruitful results from the usage of this methodology, it is essential for both the project clients and sponsors to understand what they need and make decisions they will stick to. In addition, if a software development firm does not have a person with the appropriate business analyst skills and experience then it can surely face a problem scope creep (My-Project-Management-Expert, 2009). Identify the potential obstacles to using the following frameworks and analyze the risks and issues associated with each of them. Obstacles, Risks and Mitigation for Scrum One of the major obstacles in the Scrum software development methodology is that there is no project manager, which can communicate with project stakeholders and run the project effectively. For instance, a project manager is essential to bridge a gap between project stakeholders, especially between project team members and clients. This obstacle can raise various risks such as poor communication, poor management, and poor quality and so on. This obstacle and associated risks can be better dealt with by choosing a ScrumMaster. In this scenario, it is essential to choose a ScrumMaster who possesses strong leader qualities. In addition, the team should make sure that the person they are choosing to be the ScrumMaster is really capable of overseeing, guiding, leading, and carrying out any follow-through that must be undertaken (Bowen, 2013). There is another biggest obstacle in Scrum software development methodology is the daily SCRUM meeting. Without a doubt, a daily meeting can be a serious obstacle which can raise risks of time overrun, budget overrun and change in schedule. However, by developing a particular agenda a software development team can deal with this issue. For instance, they should establish three basic questions that need to be answered in a meeting of 15 minutes. These questions can include what was done? What will be done? And what is blocking future progress? Moreover, in order to save time this meeting can be held virtually by making use of any web based technology (Bowen, 2013). Normally, an obstacle occurs when a company attempts to use Scrum methodology with a team that resists change. As a result, there can occur a variety of risks such as time wastage and poor quality. For instance, a company wants to use Scrum in the place where project team members are expert at using Lean Six Sigma methodologies or Six Sigma methodologies in project management. In this scenario a software development team must implement an appropriate change management methodology (Bowen, 2013). Obstacles, Risks and Mitigation for DSDM One of the basic obstacles in DSDM is its restricted philosophy and a list of principles that need to be followed in order make a project a success. However, this obstacle can raise a variety of risks for instance team members of a software development members are not experts at using this methodology, or they can fail to implement it properly, they can require additional guidance or training. In this scenario, this problem can be solved by coordinating with employees and gaining their confidence. In the same way, some useful training sessions can be conducted. Another obstacle in using DSDM is its extensive need for the customer involvement. For instance, in a project which involves the implementation of a business application a customer needs to be always present to acknowledge the working or functionality of the system. So there is a risk of budge or time overrun due to not the presence of a customer. These issues can be resolved by establishing a suitable timeframe with the customer. Another obstacle is that in this methodology a lot of time is required for decision making. For instance, there is not a central authority that is responsible for decision making as a result a lot of time and effort is spent on the decision. These issues can be resolved by establishing an appropriate decision making process and authority in agreement with all the stakeholders. Obstacles, Risks and Mitigation for Lean Software Development One obstacle is that lean software development does not recommend any practices. For instance, it does not define what practices need to be adopted by a software development team to reduce the waste, but it just defines principles that need to be followed. So there is a risk of not following this approach effectively. In order to resolve this issue the software development team must validate that definite process definitions are adjacent to the values and principles (Anderson, 2014). In addition, this methodology is newly emerging so it has not been standardized yet. For instance, this methodology does not define any specific tools or set of practices that need to be used for the software development. In fact, this methodology was created for the production industry. So there is a risk in using this methodology for the software development until it is fully developed (Anderson, 2014). Since this methodology requires removing waste, but it is difficult to determine the waste in terms of software development. With this obstacle, there is risk of eliminating some useful functions. So a software development team must spend some time in analyzing the nature of waste (Anderson, 2014). References Adell, L. (2011, April 11). Benefits & Pitfalls of using Scrum software development methodology. Retrieved from http://blog.belatrixsf.com/benefits-pitfalls-of-using-scrum-software-development-methodology/ Anderson, D. J. (2014). Lean Software Development. Retrieved from Microsoft.com: http://msdn.microsoft.com/en-us/library/vstudio/hh533841(v=vs.110).aspx Bowen, R. (2013, May 15). Dealing with SCRUM Implementation Obstacles. Retrieved from BrightHubPM.com: http://www.brighthubpm.com/agile/57682-dealing-with-scrum-implementation-obstacles/ Cohn, M. (2012). Scrum. Retrieved from Mountain Goat Software: http://www.mountaingoatsoftware.com/agile/scrum Craddock, A., Roberts, B., Richards, K., Tudor, D., & Godwin, J. (2012). The DSDM Agile Project Framework for Scrum. DSDM Consortium. Duggan, P. (2013, February 07). Going with the Flow – The Lean Approach to Successful Project Management. Retrieved from Backbase Blog: http://blog.backbase.com/2935/going-with-the-flow-the-lean-approach-to-successful-project-management/ Mejillano, A. C. (2011, October 02). The Advantages and Disadvantages of Agile Development Software Methods. Retrieved from EzineArticles.com: http://ezinearticles.com/?The-Advantages-and-Disadvantages-of-Agile-Development-Software-Methods&id=6600314 My-Project-Management-Expert. (2009). Agile Project Software. Retrieved from http://www.my-project-management-expert.com/the-advantages-and-disadvantages-of-lean-software-development.html Rees, D. (2013). Agile Project Management with Scrum. Retrieved from ITWales.com: http://www.itwales.com/998612.htm Uhlig, D. K. (2013). Advantages and Disadvantages of the Scrum Project Management Methodology. Retrieved from Chron.com: http://smallbusiness.chron.com/advantages-disadvantages-scrum-project-management-methodology-36099.html Read More