Ceremonies

  • Kanban Introduction
    • Introduce the team to the framework itself.
  • Kick-off Backlog Creation
    • Find out the different streams of work and make sure that the team adds it to the ticket system.
    • From now on all will be tracked through the ticket system (no more excel list, email threads, chat rooms or any other ways of getting the team to do work not being tracked in the ticket system).
    • Your Queue will go up until it stabilizes and then it will decrease to find it average.
  • Standup (15 minutes ever day)
    • What is each person going to be working today?
    • Are there any blockers?
  • Backlog Grooming (15 minutes every day)
    • Check if all new tickets added to the team queue belong to the team if not pass it to the correct queue.
    • The team estimates and discuss on how to implement this ticket(Request, Changes, Tasks in general, not Incidents as incidents need some investigation before they can be resolved). This helps to cross-skilling the team.
    • Add all new tickets to the physical Kanban board (Ready Column) every day.
    • Usually First In First Out unless the Team Manager changes the priority.
    • If there are incidents they usually should go on the Top of the Ready column to be worked asap.
  • Knowledge Sharing (1 to 2 hours per week)
  • Retrospectives (1 hour every 2 weeks)
  • Project Planning ( ad hoc per project)
    • Project work should be part of the team workload and not split the team into sub-teams.
    • Getting the team involved during the Project life cycle it makes it easier for later support of what the project delivers.
    • There are no dependencies on people going on holidays or being off. Anybody in the team can work on project tasks as the team cross-skills.