Software Development Methodologies Background

Software development methods background without any introduction or conclusion. Focused mainly agile methodologies.
references can be usedAckermann, C.& Lindvall, M., 2006. Understanding Change Requests to Predict SoftwareImpact. Columbia, MD, 30th Annual IEEE/NASA Software EngineeringWorkshop,, pp. 66-75.Amabile, T. M. et al., 2002. Time Pressure and Creativityin Organizations: A Longitudinal Field Study, s.l.: Harvard BusinessSchool Working Paper.Anderson, D. J., 2003. Agile Management for SoftwareEngineering: Applying the Theory of Constraints for Business. Upper SaddleRiver, NJ: Prentice Hall.Anderson, D. J., 2010. Kanban: Successful EvolutionaryChange for Your Technology Business. Washington: Blue Hole Press.Appelo & Jurgen, 2011. Management 3.0: Leading AgileDevelopers, Developing Agile Leaders. Upper Saddle River, NJ:Addison-Wesley.Babik, L., 2005. Plans are useless, but planning isindispensable. Panama City, Panama, Project Management Institute.Beck, K. et al., n.d. Manifesto for Agile SoftwareDevelopment. [Online]Available at:[Accessed 16 09 2021].Berger, H. & Beynon-Davies, P., 2009. The Utility of aRapid Application Development (RAD) approach for a large complex InformationSystems Development. Information Systems, Volume 19, pp. 549-570.Conboy, K. & Fitzgerald, B., 2004. Toward aConceptual Framework of Agile Methods: A Study of Agility in DifferentDisciplines. New York, Association for Computing Machinery, p. 37–44.Cusumano, M. A., MacCormack, A., Kemerer, C. F. &Crandall, W., 2009. Critical Decisions in Software Development: Updating theState of the Practice. IEEE Software, 26(5), pp. 84-87.Drobka, J., Noftz, D. & Raghu, R., 2004. Piloting XP onFour Mission-Critical Projects. IEEE Software, 21(6), pp. 70-75.Highsmith, J. & Cockburn, A., 2001. Agile SoftwareDevelopment: The Business of Innovation. Computer (Long Beach, Calif.), 34(9),pp. 120-122.Johansen, T. & Gilb, T., 2005. From Waterfall toEvolutionary Development (Evo):. INCOSE International Symposium, Volume15, pp. 1676-1686.Slack, N., Johnston, R. & Chambers, S., 2010. OperationsManagement. 6th ed. London: Pearson.Sliger, M. & Broderick, S., 2008. The SoftwareProject Manager’s Bridge to Agility. 2nd ed. Upper Saddle River, N.J.:Addison-Wesley.Smith, P. G., 1990. Fast-cycle Product Development. EngineeringManagement, 2(2), pp. 11-16.Smith, P. G., 2007. Flexible Product Development:Building Agility for Changing Markets. 1st ed. San Francisco: Jossey-Bass.Snowden, D. J. & Boone, M. E., 2007. A Leader’sFramework for Decision Making. Harvard Business Review, 85(11), pp.68-76, 149.Szalvay, V., 2010. An Introduction to Agile SoftwareDevelopment, s.l.: Danube Technologies, Inc..Vidgen, R. & Wang, X., 2006. Organizing for agility:A complex adaptive systems perspective on agile software development process. s.l.,ECIS 2006 Proceedings.Wang, X. & Conboy, K., 2009. Understanding agility insoftware development from a complex adaptive systems perspective. s.l.,ECIS 2009 Proceedings.Wiegers, K., 1998. Know your enemy: software riskmanagement. Software Development, 6(10), pp. 38-42.Williams, L. & Cockburn, A., 2003. Agile SoftwareDevelopment: Its about Feedback and Change. IEEE Computer, 36(6), pp.39-43.