When starting with Kanban, you will most probably have a generic board, probably with steps like “Analysis”, “Development” or “Testing”. But if you look in detail at the actual process you might see that there are many more steps – maybe you do a code review, there may be manual and automation testing and so on. Then again, not all the steps will be used for all work – maybe code review is done only for new features and not bug fixes, while manual testing is done for every UI change, but not for backend change. And still again, an emergency bug fix might be very high priority and have to be pushed live within few hours, bypassing many steps.
See, the actual process followed in often much more complex than the generic 3-step process depicted on the board. So how to reconcile this? That’s what we will discuss in this session.
- Date:28/04/2019
- Time:12:00
- Event:Kanban Day @Chennai
