How it began?
I have always believed that success of any agile methodology purely depends on the team as they play a vital role in making sure the ever changing needs to the software are met with quality and on-time delivery for a great product to be delivered.
The key however lies in understanding how better we as a team are ready to understand fixed and fluctuating priorities and if we need a mix of both to deliver a great software. Agile methodology has always excited me - have been working on Scrum and Kanban framework for more than 4-5 years. I have always been curious to know and envision combining both frameworks without compromising on the ownership and after a bit of research I found 'Kanplan'
Introduction to Kanplan
Kanplan is a mixed methodology which combines the features of both Scrum and Kanban software framework. It will be ideal for teams who want their backlog to be refined but their priorities are fluctuating so need a flexible timeline to deliver it unlike scrum which is time-boxed.In simple words, Kanplan enables teams to combine the planning setup of Scrum with the process flexibility of Kanban as it provides visibility to planning goals, work-in-progress tasks and thus clearly organizing the team's to-do list.
How does Kanplan work?
- Teams create a column for backlog where the items can be prioritized and organized.
- Once the backlog grooming is done, the tasks can be moved from the Kanban backlog to appropriate columns based on status onto the Kanban board.
- Before moving these tasks onto the board, the tasks needs to be assigned to an appropriate person working on them.
How does Kanplan look like?
The Kanplan feature – now available in both Jira Software Cloud and Server – introduces a wide column backlog with issues in a list view. This splits the Kanban Board into two different screens; the backlog for grooming and the Kanban board for the engineering team to select and move tasks through the workflow.
