The adoption of Software Engineering practices in a Scrum environment

References

• Abrahamsson, P., and O. Salo. 2008. “Use and Usefulness of Extreme Programming and Scrum.” IEEE Xplore Journal 2 (1): 1–7.
   Google Scholar
• Allan Kelly Associates. 2010. “The Scrum Wall (Another Agile Failure Mode).” Accessed 20 September 2020. https://www.allankellyassociates.co.uk/archives/869/scrum-wall-another-agile-failure-mode/.
   Google Scholar
• Appelo, J. 2008. Management 3.0, Leading Agile Developers, Developing Agile Leaders. Berlin: Springer Verlag Publishers.
   Google Scholar
• Awad, M. A. 2005. A Comparison Between Agile and Traditional Software Development Methodologies. Western Australia: School of Computer Science and software Engineering, The University of Western Australia.
   Google Scholar
• Balsamo, S., A. Di Marco, P. Inverardi, and M. Simeoni. 2004. “Model-Based Performance Prediction in Software Development: A Survey.” IEEE Transactions on Software Engineering 30 (5): 295–310.
   Web of Science ®Google Scholar
• Bang, T. J. 2007. “An Agile Approach to Requirement Specification.” 8th International Conference on Agile Processes in Software Engineering and Extreme Programming, 193–197. Berlin: Springer-Verlag.
   Google Scholar
• Bjeirmi, B. F., and A. K. Munns. 1996. “The Role of Project Management in Achieving Project Success.” International Journal of Project Management 14 (2): 81–87.
   Google Scholar
• Braun, V., and V. Clarke. 2006. “Using Thematic Analysis in Psychology.” Qualitative Research in Psychology 3 (2): 77–101.
   Google Scholar
• Brhel, M., H. Meth, A. Maedche, and K. Werder. 2015. “Exploring Principles of User-Centered Agile Software Development: A Literature Review.” Information and Software Technology 61: 163–181.
   Web of Science ®Google Scholar
• Cao, L., and B. Ramesh. 2008. “Agile Requirements Engineering Practices: An Empirical Study.” IEEE Software 25 (1): 60–67.
   Web of Science ®Google Scholar
• Capitalhead. 2006. “Software Development.” (June 11). Accessed August 12, 2011. http://capitalhead.com/solutions/software-development.aspx.
   Google Scholar
• Cho, J. 2009. “A Hybrid Software Development Method for Large -Scale Projects: Rational Unified Process with Scrum.” Issues in Information Systems Journal 10 (2): 338–347.
   Google Scholar
• Cockburn, A. 2001. Agile Software Development. Boston: Addison-Wesley Professional.
   Google Scholar
• Cohn, M. 2007. “Differences Between Scrum and Extreme Programming.” Accessed August 11, 2011. Mountain GoatSoftware:http://blog.mountaingoatsoftware.com/differences-between-scrum-and-extreme-programming/comment-page-1.
   Google Scholar
• Digital.ai Software, Inc. 2020. "14th Annual State of Agile Report." Texas, United States: Digital.ai Software, Inc. https://digital.ai/catalyst-blog/the-14th-annual-state-of-agile-report.
   Google Scholar
• Drnovscek, S., and V. Mahnic. 2005. Agile Software Project Management with Scrum. Ljubljana: University of Ljubljana, Faculty of Computer and Information Science.
   Google Scholar
• Dyba, T., and T. Dingsoyr. 2008. “Empirical Studies of Agile Software Development: A Systematic Review.” Information and Software Technology 50 (9-10): 833–859.
   Web of Science ®Google Scholar
• Eckstein, J. 2013. Agile Software Development with Distributed Teams: Staying Agile in a Global World. Boston: Addison-Wesley.
   Google Scholar
• Etikan, Ilker, Sulaiman Abubakar Musa, and Rukayya Sunusi Alkassim. 2016. “Comparison of Convenience Sampling and Purposive Sampling.” American Journal of Theoretical and Applied Statistics 5 (1): 1–4. doi:10.11648/j.ajtas.20160501.11.
   Google Scholar
• Evans, E. 2004. Domain-Driven Design Tackling Complexity in the Heart of Software. New York: Addison-Wesley Publishers.
   Google Scholar
• FreeTutes.com. 2011. "Waterfall Software Development Life Cycle Model." June 26. Accessed at http://www.freetutes.com/systemanalysis/sa2-waterfall-software-life-cycle.html.
   Google Scholar
• Fowler, M. 2005. The New Methodology, December 13. Accessed April 11, 2011. Martinfowler.com: http://www.martinfowler.com/articles/newMethodology.html#FromNothingToMonumentalToAgile.
   Google Scholar
• Fowler, M., K. Beck, J. Brant, W. Opdyke, and D. Roberts. 2002. Refactoring: Improving the Design of Existing Code 1999. Boston: Addison-Wesley.
   Google Scholar
• Highsmith, J., and A. Cockburn. 2007. “Agile Software Development: The Business of Innovation.” IEEE Xplore Journal 3 (5): 1–3.
   Google Scholar
• Highsmith, J., and J. Highsmith. 2009. Agile Project Management: Creating Innovative Products. Chicago: Addison-Wesley Publishers.
   Google Scholar
• Hunt, J. 2006. Agile Software Construction. London: Springer - Verlag Publishers.
   Google Scholar
• Jyothi, V. E., and N. K. Rao. 2011. “Effective Implementation of Agile Practices Ingenious and Organized Theoretical Framework.” (IJACSA) International Journal of Advanced Computer Science and Applications 2 (3): 1–8.
   Google Scholar
• Kanwal, F., K. Junaid, and M. A. Fahiem. 2010. “A Hybrid Software Architecture Evaluation Method for FDD – An Agile Process Model.” The Institute of Electrical and Electronics Engineers.
   Google Scholar
• Kerzner, H. 2009. Project Management: A Systems Approach to Planning, Scheduling and Controlling. New Jersey: John Wiley and Sons.
   Google Scholar
• Keshta, N., and Y. Morgan. 2017. “Comparison Between Traditional Plan-Based and Agile Software Processes According to Team Size & Project Domain (A Systematic Literature Review).” In 2017 8th IEEE Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON), 567–575. IEEE.
   Google Scholar
• Kim, Y. 2007. “Analyzing Scrum Agile Software Development with Development Process, Social Factor, and Project Management Lenses.” Americas Conference on Information Systems (AMCIS), 1–10. California: Americas Conference on Information Systems.
   Google Scholar
• Kruchten, P., and P. Kroll. 2003. The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP. Boston: Pearson Education, Inc.
   Google Scholar
• Larman, C. 2004. Agile and Iterative Development: A Manager's Guide. Boston: Pearson Education, Inc.
   Google Scholar
• Lei, H., F. Ganjeizadeh, P. K. Jayachandran, and P. Ozcan. 2017. “A Statistical Analysis of the Effects of Scrum and Kanban on Software Development Projects.” Robotics and Computer-Integrated Manufacturing 43: 59–67.
   Web of Science ®Google Scholar
• Lynema, E. 2010. Agile Project Management and the Real World. New York City: NCSU Libraries.
   Google Scholar
• Moe, N., T. Dingsøyr, and T. Dybå. 2009. "Overcoming Barriers to Self-Management in Software Teams." IEEE Software 26 (6): 20–26.
   Web of Science ®Google Scholar
• Olaleye, S. A., I. T. Sanusi, F. S. Mark, and J. Salo. 2020a. “Customers’ Loyalty to Tablet Commerce in Nigeria.” African Journal of Science, Technology, Innovation and Development 12 (2): 217–229.
   Web of Science ®Google Scholar
• Olaleye, S. A., I. T. Sanusi, and J. Salo. 2020b. “Mobile Customers’ Experience and Loyalty: A Study of Tablet Gender Divergence in Finland.” International Journal of Internet Marketing and Advertising 14 (3): 275–298.
   Google Scholar
• Pudusserry, A. 2009. Agile Project Management Implementation Approach. Bangalore: Project Management Research Institute.
   Google Scholar
• Sahota, M. 2011. 5 Ways Scrum Creates Safety: Why One CSC Uses Scrum and XP Together to Avoid XP Risks, February 22. Accessed April 8, 2011. Scrum Alliance transforming the world of work: http://www.scrumalliance.org/articles/180–ways-scrum-creates-safety-why-one-csc-uses-scrum-and-xp-together-to-avoid-xp-risks.
   Google Scholar
• Scaffidi, C., and M. Shaw. 2007. “Developing Confidence in Software Through Credentials and Low-Ceremony Evidence.” In Institute for Software Research, 1–3. Pittsburgh: School of Computer Science Carnegie Mellon University.
   Google Scholar
• Schwaber K. 2004. Agile Project Management With Scrum. Redmond: Microsoft Press.
   Google Scholar
• Schwaber, K. 2010. “Waterfall, Lean/Kanban, and Scrum.” July 3. Accessed August 11, 2011. fromkenschwaber.wordpress.com:http://kenschwaber.wordpress.com/2010/06/10/waterfall-leankanban-and-scrum-2/.
   Google Scholar
• Schwaber, K., and M. Beedle. 2002. Agile Software Development with Scrum. Upper Saddle River, NJ: Prentice Hall.
   Google Scholar
• Shore, J., and S. Warden. 2008. The Art of Agile Development. California: O'Reilly Media Inc.
   Google Scholar
• Singh, V. 2009. “Differences Between Scrum and Extreme Programming.” Accessed August 11, 2011. Mountain GoatSoftware:http://blog.mountaingoatsoftware.com/differences-between-scrum-and-extreme-programming/comment-page-1.
   Google Scholar
• Srivastava, A., S. Bhardwaj, and S. Saraswat. 2017, May. “SCRUM Model for Agile Methodology.” In 2017 International Conference on Computing, Communication and Automation (ICCCA), 864–869. IEEE.
   Google Scholar
• Stafford, J., Y. Francino, B. Matturro, and M. Webb. 2011. Definition Scrum. Accessed August 12, 2011. SearchSoftwareQuality.com: http://searchsoftwarequality.techtarget.com/definition/Scrum.
   Google Scholar
• Sutherland, J. 2004. “Agile Development: Lessons Learnt from the First Scrum.” Cutter Agile Project Management Advisory Service Journal 5 (20): 1–6.
   Google Scholar
• Sutherland, J. 2007. Deep Lean. Boston: Massachusetts Institute of Technologypublishers.
   Google Scholar
• Vallon, R., B. J. da Silva Estacio, R. Prikladnicki, and T. Grechenig. 2018. “Systematic Literature Review on Agile Practices in Global Software Development.” Information and Software Technology 96: 161–180.
   Web of Science ®Google Scholar