Please submit your abstract below. Remember to indicate the length of the session

Kanban in Research Projects

In some organisations, there are separate Research Departments which take care of the new ideas coming up and the initial feasibility study of these ideas for a Go/No-Go decision for further implementation to the Development Department. It does sound like Silos and non-Agile but nevertheless, since it's not possible to immediately shut down these establishments, there's a way to manage flow through these Research Projects using Kanban, which helps us to limit the WIP and hence, limit the number of ideas we want to focus on and help us to prioritize between these ideas using cost of delay so that at any time we are working on the right amount ideas depending upon which are the most important ones based on cost of Delay unlike earlier when every idea coming up was said to be important (only based on gut feeling) and led to numerous number of unimportant Projects with no control on WIP and huge Capacity Utilization (more than 100%) leading to the failure of these Projects. Kanban, not only adds visibility to what's happening to these new ideas but also let these ideas flow through the system in order to convert them into successful Projects.

10 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ravneet Kaur shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base