Hands-On Software Engineering with Python

Kanban

Kanban, as a process, has a lot of similarities to Scrum:

• The main unit of effort is a user story.
• Stories have the same sort of story-level process status, to the point where the same sort of task board, real or virtual, is used to track and provide visibility into work in progress.
• Stories should have all of their requirements and other relevant information ready and waiting before work on them commences. That implies that there is some sort of story grooming process, though it may not be as formally structured as the equivalent in Scrum.

Kanban, unlike Scrum:

• Is not time-boxed—there is no Sprint.
• Does not expect or require the daily status/stand-up meeting, though it's a useful enough tool and is thus commonly adopted. Other ...