BamBam! Teamwork Academy is a new series by 84kids focusing on online collaboration, project management and Agile approach to software development.
Each presentation contains a number of useful tips that can be applied in practice to all kinds of development business, from small software houses to engineering companies running on workflows to large production ventures.
Feel free to comment and share!
2. #3 Kanban
Kanban is an Agile methodology that focuses on the
visualization of your workflow (a board of memos)
Workers using Kanban receive their tasks and materials
exactly when they need it, no sooner
Kanban was invented by Toyota as a means of improving
work efficiency
The word comes from Japanese and means a signal-card
What is Kanban?
3. Will Agile work for my company?Will Kanban work in my company?
What is more important for you: individuals and
interactions or processes and tools?
Do you spend more time making your product usable
or making documentation how to use it?
Would you rather collaborate with your clients
or negotiate hard?
Are you able to respond to changes on-the-fly
or do you stick to the plan no matter what?
#3 Kanban
4. If you chose at least one answer in bold
then Kanban is definitely worth giving a shot
#3 Kanban
5. Selected methods of AgileHow does Kanban work?
Work is divided into tasks, prioritised and put into backlog
A task with the highest priority is pulled from the backlog.
When the work on task is finished, it’s marked as ‘done’
and can be pulled by the next person in line
The idea of Kanban is not to push tasks down the line,
but let people pick them when available
#3 Kanban
7. How to make your team commissionedWhat are direct benefits of using Kanban?
#3 Kanban
Work is visualised which reduces confusion
Reduced idle time (waiting) and over-processing
Increased productivity and customer satisfaction
Flexibility
Simplified production planning
8. Common mistakes of new Kanban teams
No backlog grooming
No workflow visualization
Exceeded limit of Work in Progress
Workflow not fitting company process (eg. too many steps)
Moving items back in line due to badly constructed workflow
Creating additional policies that override basic principles of
Kanban
#3 Kanban