Agile planning is a simple way to manage complex projects. It’s a way to divide a large meal into bite-sized chunks. With agile, teams can better respond to changing requirements and enjoy an even distribution of project responsibility. In agile, this degree of responsiveness to changing requests is valued above the ability to predict the needs of the market. Arguably, the two most popular methods of agile planning are Scrum and kanban.
For Scrum Users
Scrum is based around timeboxed planning usually known as sprints or iterations. These timeboxes mark a focused effort with prioritizing taking place in the backlog before the highest priority goals are pushed into a sprint. Each sprint is meant to enhance the product’s market value or add new functions and improvements and the key measure of success is a functioning product at the end of each sprint.
For Kanban Users
Kanban is marked by continuous flow where the team works in columns on a kanban board, traditionally divided by To Do, In Progress, Review, and Done.
With kanban, all the focus is on the items in those progressive columns. Multitasking is avoided and team members are not looking beyond the scope of the current kanban board. The product owner prioritizes items in the backlog and once an item is completed in the kanban board the team adds a new one from the backlog. The aim being continuous delivery.
In kanban at its purest the team is not working in timeboxed activity such as sprints or iterations although, as this video will show, there are ways of incorporating the Scrum timeboxes into the process.
In this video we explore how two different teams can do their planning on the Tempo Planner timeline. One using a JIRA Scrum board and one using a JIRA kanban board. We will illustrate how both teams can benefit from Tempo’s adaptive planning solution.
The Tempo Suite of Solutions
Upgrading Tempo Planner is free for all customers with an active license. New customers can purchase or evaluate Tempo Planner for JIRA Server through the Atlassian Marketplace.