Similarities and Differences between Scrum and Atern
1085 Words5 Pages
Similarities and Differences Between Scrum and Atern
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 ...
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.