1. Ease of use: Simple to understand
2. Cards provide task clarity/key information instantly e.g. status
3. Promotes continuous and stable improvements
4. Adaptability: Flexible for regularly evolving requirements
5. Collaboration: Encourages collaboration within and between teams
6. Low Overheads: Supervision is easier
7. Reduces Costs/Wastage: Highlights issues/bottlenecks
1. No Task Start/End Dates: No idea how long tasks are on the board
2. Not a Standalone: Usually combined with JIT/Scrum
3. Lacks explicit iteration
4. Difficult to apply to larger projects with many inter-dependencies
5. A Monitoring Tool: Lacks focus on quality
6. Board Cluttered: A lot of space per card
7. No Task Owners: No responsibility assigned to any single person
Kanban-C (Kanban-Controlled)
Kanban-C (Kanban-Controlled) is a patent-pending methodology for workflow management with controls.
It keeps the best of Agile:
Delivers output frequently (every 1-8 weeks); prioritises client satisfaction, quality delivery and monitoring; encourages creativity and innovation;
welcomes/encourages change or changing customer requirements; includes iteration; promotes feedback, as well as continuous and stable improvements; and includes
self-organised teams with users assigned one or more roles.
Kanban-C Improvements
Terminology is simple. It is flexible and works well for regularly evolving requirements and is applicable for all teams and industries.
Cards provide clarity and responsiveness. Teams view key information instantly: More than traditional Kanban, without clutter as users select 5 columns for status options.
Learn moreKanban-C does not require significant training nor practitioners experienced in the methodology. Scrum and other approaches take far longer.
Groups are: Prep, Working, Review & Final Stages, with 49 customisable status options across groups. Teams still discuss the backlog and pull items onto the board, subject to WIP, but only the PM signs off and moves items between groups.
Learn moreIt includes start-end dates for parent, child and grandchild tasks. Responsibility is re-introduced. The team largely work on Child Tasks (within parent task start-end date ranges).
Methodically work, review, test, client review and pre-release, while reducing knee-jerk reactions. It includes collaboration (notes/chat) between teams and Project/Product Manager, without wasting excessive time in meetings.
Learn moreIf a team member is stuck/waiting they enter estimated percent complete to the manual timeline and can pull more items onto the board, up until max WIP.
Learn moreThere are full audit trails. When a team member, who is not PM or task owner, updates the manual timeline, the person's initial is displayed. This can serve as a flag to spot disgruntled/unethical staff.
Learn moreWhen materials are required M (green/red) indicates "in stock"/shortage and links to stock requisition. When equipment is required E (green/red) denotes available/unavailable.
Learn more