Similarities and Differences Between Scrum and Atern
Introduction
Traditional project management approaches have proven inefficiency and ineffective due to the rate of project management failures experienced in the past (Coleman & Verbruggen, 1998; Vinekar, Slinkman, & Nerur, 2006). These failures led to the emergence of Agile Project Management. Different Agile project management approaches have been designed to improve project management. This work explores the similarities and differences between Scrum and Atern project management approaches.
Similarities between Scrum and Atern
The first similarity between Scrum and Atern is that these two agile project management approaches rely on a common core philosophy (Ambler, 2002; Guntamukkala, Wen, & Tarn, 2006; Jyothi & Nageswara Rao, 2012, Milanov & Njegus, 2012). Agile’s core philosophy is that project management needs to be improved in such a way that its management uncovers better ways of handling software development (Guntamukkala, Wen, & Tarn, 2006; Jyothi & Nageswara Rao, 2012, Milanov & Njegus, 2012; McAvoy & Sammon, 2005). Agile software seeks to help others to achieve a given end by adding value to individuals their interactions rather than focus on tools and processes (Stoica, Mircea, & Ghilic-Micu, 2013).
Scrum and Atern seeks to add value by improving working software rather than focus on comprehensive documentation (Stoica, Mircea, & Ghilic-Micu, 2013; Vinekar, Slinkman, & Nerur, 2006). Scrum and Atern adds value by having close collaborations with the customer rather than emphasize on contract negotiation (Stoica, Mircea, & Ghilic-Micu, 2013; Vinekar, Slinkman, & Nerur, 2006). Scrum and Atern adds value by responding to change rather than emphasizing on following lai...
... middle of paper ...
...20.
Milanov, G., & Njeguš, A. (2012). Analysis of Return on Investment in Different Types of Agile Software Development Project Teams. Informatica Economica, 16(4), 7-18.
Qureshi, M. (2012). Agile software development methodology for medium and large projects. IET Software, 6(4), 358-379. doi:10.1049/iet-sen.2011.0110
Ramsin, R. R., & Paige, R. F. (2010). Iterative criteria-based approach to engineering the requirements of software development methodologies. IET Software, 4(2), 91-126. doi:10.1049/iet-sen.2009.0032
Stoica, M., Mircea, M., & Ghilic-Micu, B. (2013). Software Development: Agile vs. Traditional. Informatica Economica, 17(4), 64-76. doi:10.12948/issn14531305/17.4.2013.06
Vinekar, V., Slinkman, C. W., & Nerur, S. (2006). Can agile and traditional systems development approaches coexist? An ambidextrous view. Information Systems Management, 23(3), 31-35.
Agile project management is an iterative approach to the planning and monitoring of project processes. Agile projects are conducted in smaller tranches called iterations with each of these iterations closely reviewed and critiqued by the project team (employees, representatives of the clients etc.). The knowledge gained from this process is then used to ascertain the next steps of the
Software design and development is a field that requires various skills and abilities. Companies engaged in the development of software should provide an inclusive work environment where the different strengths of their employees are recognised, utilised and respected. Software development involves far more than programming skills. Personnel are required with strong communication, teamwork, attention to detail, creativity, design and problem-solving skills. Different personnel will possess these skills in varying proportions. It is the job of management to foster and encourage the development and enhancement of skills in the workplace.
Large and small businesses, governments, and schools strive to build the next new gadget, manage resources more efficiently, and teach or train in more creative ways. If they set out blindly on a task without proper oversight and thought about the process, then surely the result would be a dismal failure. Project management enables these entities, and various others, to carefully consider the many variables before, during, and after the project actually takes place. Project management refers to the careful planning, organization, and management through a single one-time activity. Projects are non-routine tasks that are set out to be accomplished for a specific amount of time (Trelles-Duckett & Lonergan , n.d.). Projects have an absolute
Wells, D. (2009). Agile Software Development: A gentle introduction. In Agile Process. Retrieved April 20, 2014, from http://www.agile-process.org.
Gray, Clifford F.; Larson, Erik W., Project Management – The Managerial Process, Copyright © 2001 by The McGraw-Hill Companies, Inc.
Gray, C., Larson, E. (2008). Project Management: The managerial Process. New York, NY: The McGraw-Hill Companies Inc.
A software development methodology defines the activities to be undertaken by each individual in the development process, specific techniques for accomplishing those activities, like using a flowchart to document the program logic of a particular software. It also offers guidelines to manage the quality of software at various stages of development.
The Systems Development Life Cycle (SDLC) consists of phases used in developing a piece of software. It is the plan of how to develop and maintain software, and when necessary, replace that software. In 2007 during my hospital’s transition to a new software system, I was fortunate enough to be included in the process. I did not get involved until the implementation phase, but from then on, until now, I remain very active in the process. I decided to highlight the Waterfall Model of SDLC. The Waterfall Model is a “sequential development process” with each phase continuing in a line (McGonigle and Mastrian, 2012, p. 205).
The Scrum approach is pretty flexible. This enables the project to be able to adapt whenever a new situation arises. This aspect of Scrum is pretty important since all projects undergo change during its scope. The ability to adapt allows for your project to stay relevant. This is especially essential in the fast moving world of technology and software. Scrum takes on an empirical approach. This means that there is an understanding that all projects will be faced with unpredicted challenges. Scrum maximizes on its abilities to deliver and respond to these changes. Scrum is a simple concept which tackles difficult tasks. The core of scrum can be divided into 3 primary roles; product owners, development teams, and Scrum masters.
It is possible to have a singular methodology for project management to specify morality and ethics when dealing with customers. Application of agile project management approaches like Atern offer a more inclusive approach for stakeholders including consistent update and revision of strategies. When the project manager violates protocol, all stakeholders should come together, clarify issues of violation, and set standards for all to follow.
Schrodl, Holger and Wind, Stefan, "Adoption of SCRUM for Software Development Projects: An Exploratory Case Study from the ICT Industry" (2011). AMCIS 2011 Proceedings - All Submissions. Paper 256.
As more companies that are leading technology are transforming from the traditional waterfall development model to an Agile software methodology, requirements engineering provides a process for software engineers to understand the problems they need to solve (Martin, Newkirk, & Koss, 2014). It is of key importance to understand the customer 's wants and needs before beginning designing or building the computer-based solution, as developing a solution that ignores the customer’s needs provides value to none of the parties involved. Thus, the intent of requirements engineering is to produce a written understanding of the customer 's problem (Pressman, 2010). Work products that are available to communicate this understanding include user scenarios, function and feature lists, analysis models, and specifications. This paper provides an evaluation of requirement patterns, an assessment of problem solving techniques most effective, a descriptive explanation of the patterns that includes a visual taxonomy, and an explanation of how the patterns identified are related.
Most of the software development projects change just during the development is in process. This is the reason that agile methodology is best for these projects. There is a room for change in them. Software developers follow these methods and this is the reason that they have further modified these methods according to the different types of projects they confront in their development time.
When planning a new project, how the project will be managed is one of the most important factors. The importance of a managers will determine the success of the project. The success of the project will be determined by how well it is managed. Project management is referred to as the discipline that entails the processes of carefully planning, organizing, controlling, and motivating the organization resources so as to foster and facilitate the achievement of specific established and desired goals and meet the specific criteria of success required in the organization (Larson, 2014). Over the course of this paper I will be discussing and analyzing the importance of project management.