Kanban pull and flow - a transparent workflow for improved quality and productivity in software development

  • Raju H
  • Krishnegowda Y
  • 34

    Readers

    Mendeley users who have this article in their library.
  • 0

    Citations

    Citations of this article.

Abstract

In software industry, there has been a significant focus shift from sequential waterfall model to iterative agile/scrum methods to continuous lean software development in the last several years. Traditional waterfall model is the dominant project management para-digm, agile methodology is direct response to waterfall model, and lean is recent one. In practice, when software companies make an attempt to adopt agile/scrum methods, the team is unwilling to alter their way of doing the day-to-day work. The mismatch between the processes makes the team very difficult to accept the new approach and ultimately regress to their former process — waterfall model. On the other hand, flow-based Kanban offers an opportunity to build on what is already working well and gradually makes the transformation to better process. Kanban is based on lean prin-ciples. There have been a lot of attempts for making Kanban suitable for software development process.

Get free article suggestions today

Mendeley saves you time finding and organizing research

Sign up here
Already have an account ?Sign in

Find this document

Authors

  • H.K. Raju

  • Y.T. Krishnegowda

Cite this document

Choose a citation style from the tabs below

Save time finding and organizing research with Mendeley

Sign up for free