User:Hamzah2018/sandbox

This is the user sandbox of Hamzah2018. A user sandbox is a subpage of the user's user page. It serves as a testing spot and page development space for the user and is not an encyclopedia article. Create or edit your own sandbox here.

Other sandboxes: Main sandbox | Template sandbox

Finished writing a draft article? Are you ready to request review of it by an experienced editor for possible inclusion in Wikipedia? Submit your draft for review!

Agile Kanban Method

Inroduction

Software Project Management (SPM) is the concept that involves knowledge, techniques, and tools, which are essential needed for managing the development process of software projects. SPM is a sub-discipline of project management in which software projects are planned, implemented, monitored, and controlled ^[1]. In addition, in order to deliver the software on the time, a software project manager is responsible for planning and scheduling the process of Software Development Projects (SDPs). ^[2]

Kanban Method

The concept of Kanban has been introduced at Toyota in 1947, however, recently has gained an increasing momentum in domain of Software Engineering (SE). Kanban term has taken from Japanese term, which means ‘signboard’. It is a visual process management system that can manage knowledge and work with considering the Just In Time (JIT) delivery, whereby JIT does not overload team members. Beside of that, Kanban method can focus on removing bottlenecks and waste, along with reducing waiting times, which lead to increase the number of throughputs ^[3].

David J. Anderson, described Kanban as “an approach to incremental, evolutionary process, and systems change for organizations” ^[4]. Moreover, Kanban method can enhance understanding, visibility, and controlling the workflow. It can help the management by identifying the bottlenecks during the development process of software projects ^[5].. Furthermore, Kanban method uses the pull system as core approach in order to expose the problems of system process, and to stimulate collaboration for continuously improving the system ^[6]. Kanban is vital method for managing workflow and controlling waste. The works in traditional methods look as a chain, whereby the work of one member is given to another. This may cause lags in the development cycle in case of next member has problems related to others member work, thus this member is being overloaded. However, Kanban method does not push the work tasks to members, but it utilizes the pulling system. All team members must have only one task to work on at a specific time. After finishing that task, team member can pull another task ^[7]. Recently, Kanban method is gaining increasing attention and popularity, due to its numerous advantages that make it performs better than other methods in terms of managing software projects ^[8].. However, some studies have revealed that Kanban method still having challenges prevent its adoption in SDOs. Therefore, the advantages and challenges of Kanban method will be discussed further in the subsequent subsections, after presenting an introduction to Kanban board, Kanban principles, and Kanban practices.

Kanban Board

Kanban method has a board that used to visualize the workflow and monitor the project progress by showing the activities of the development process and keeping WIP in control. Kanban board also gives developers the ability to concentrate on few tasks. Thus, resources and time waste would be reduced due the switching process between the tasks in Kanban board ^[9]. Kanban board is considered as the key aspect of Kanban method, where the development process can be tracked ^[10]. Typically, Kanban board is vertically divided into different columns or stages. Each stage refers to the task state. Each task is represented by a card that attached on the board in the stage to represent the task‘s current state. On Kanban board, cards are moved from left side to right side based on the changes of task's state ^[11]. Figure 1 shows a Kanban board.

References

^ (Agarwal & Tayal, 2011; Tarom, 2014)
^ (Kaur, Singh, & Rakshit, 2013; Khattak & Qureshi, 2015; Popescu, 2016; Sharma & Pandey, 2013)
^ (Ansah & Sorooshian, 2017; Brechner, 2015; Michael, 2012)
^ (Anderson, 2010)
^ (Ahmad et al., 2015; Matharu et al., 2015)
^ (Anderson, 2010)
^ (Ahmad et al., 2015; Concas et al., 2013)
^ (Ahmad et al., 2016; Anttila, 2014; Flora & Chande, 2014; Karunanithi, 2016; Kirovska & Koceski, 2015; Lei et al., 2017)
^ (Anderson, 2010; Dennehy & Conboy, 2016)
^ (Saltz & Crowston, 2017)
^ (Nakazawa & Tanaka, 2016)

[1] (Agarwal & Tayal, 2011; Tarom, 2014)

[2] (Kaur, Singh, & Rakshit, 2013; Khattak & Qureshi, 2015; Popescu, 2016; Sharma & Pandey, 2013)

[3] (Ansah & Sorooshian, 2017; Brechner, 2015; Michael, 2012)

[4] (Anderson, 2010)

[5] (Ahmad et al., 2015; Matharu et al., 2015)

[6] (Anderson, 2010)

[7] (Ahmad et al., 2015; Concas et al., 2013)

[8] (Ahmad et al., 2016; Anttila, 2014; Flora & Chande, 2014; Karunanithi, 2016; Kirovska & Koceski, 2015; Lei et al., 2017)

[9] (Anderson, 2010; Dennehy & Conboy, 2016)

[10] (Saltz & Crowston, 2017)

[11] (Nakazawa & Tanaka, 2016)

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]