Agile Project Essay examples

3745 Words15 Pages
CHAPTER TWO LITERATURE REVIEW 1.0 Introduction The literature reviews the various literatures that underline the study of training and development in firms both in the public and private sector and its effect on performance. In this chapter, I discussed the literature on agile project management and its benefits and challenges by considering definitions and theories of agile project management, principles and empirical literature. 2.1 Project management and agile project management defined 2.1.1 Project management According to Kerzner (2009, 10th ed.) project management is the planning, directing and controlling of company resources for a relatively short-term objective that has been established to complete specific goals and…show more content…
Sheuly (2013, pp.70) added that project management consists of two principal phases: planning and scheduling phase, as well as controlling phase of the on-going project. According to PMI (2004, pp.5-377) to understand the value of project management, it is necessary to understand the fundamental nature of a project; the core characteristics of project management processes; how success is evaluated, the roles, responsibilities, and activities of a project manager and the expertise required; and the context in which projects are performed. This is shown in the figure 1 below. Figure 1 2.1.2 Agile project management According to Sheuly (2013, pp.70) agile project management is an iterative way of planning and guiding a project. Labine (2010) defined agile project management as short cycles of product development that deliver incremental update of the product rapidly based on the changing needs of the customer. Basili and Turner (1975, pp.390-396) said that agile project management is based on an iterative process that uses smaller, leaner, and flexible software development teams who produce their software products in less time. And Hass (2007) defined agile project management (APM) as a highly iterative and incremental process, which demands that developers and project stakeholders get actively involved in ‘working together to understand the domain, identify what needs
Open Document