Scrum is an iterative and incremental agile software development methodology for managing product development.
The product backlog is what will ultimately be delivered, ordered into the sequence in which it should be delivered. Product Backlogs are broken into manageable, executable chunks named sprints. Every certain amount of time the team initiates a new sprint and commits to deliver a certain number of user stories from the backlog, in accordance with their skills, abilities and resources. The project advances as the backlog becomes depleted.
Kanban in Japanese, (kan) can mean to look closely at, take care of, or keep watch. (ban, or ita by itself) means a board. Therefore, Kanban roughly translated should be something like “a board to look at”.
The Kanban methodology is used to divide project development (any sort of project) into stages.
A kanban card is like an index card or post-it note that details every task (or user story) in a project that needs to be completed. The Kanban board is used to move each card from one state of completion to the next and in so doing, helps track progress.
If you work with agile methodologies, you’ve probably heard of Epics. There is no official definition what an Epic Story could look like. Researching the topic we find some concurrence that an Epic is “a large object containing User Stories that can serve to group those Stories, and plan strategically across multiple projects.
Epics on Taiga open up a whole host of new planning opportunities for those of you managing multiple projects with relationships between them. With Epics you can establish and track hierarchical or related relationships between user stories on different projects.
You have a lot of projects in another platform but you’ll love to manage them in Taiga? Never fear, we have your back. Use our importers to bring your Trello, Jira, Asana, Github into Taiga and see just how much more gorgeous they look. Imagine the happiness that awaits you and your team.