1. Project1
   1. About Our Kanban Transformation. Our first steps
      1. https://www.xmind.net/m/VK3c/
   2. Scrum Team
      1. Maintenance phase
      2. Change the Team (members)
   3. Why
      1. Problems
         1. Slow response to changes
         2. to much increment delivery time
         3. Heroic Iterations => Losses (Lean)
         4. not clear Process for stakeholders
      2. What we want
         1. More frequent releases
         2. Continuous improvement => No Losses!
         3. Focus on customers
         4. CI / CD
         5. More effective Team
   4. What we use
      1. http://kanbanguide.ru/wp-content/uploads/2018/02/Essential-Kanban-Condensed-v1.0.01.02-_rus.pdf
   5. First ...
      1. first steps
         1. Kanban board (current tracker TFS)
         2. We limit WIP (experimentally)
         3. Define DOD
         4. Define classes of service for USs
         5. Create design of cards
         6. Define the Work with blocks
      2. first problems
         1. Regress
         2. Scrum meetings
         3. UnProduct Bugs
         4. Time opacity
   6. Summary
      1. People are not afraid of change, people are afraid of uncertainty
      2. Kanban has a simple entry point
      3. Think: when can you leave project
      4. Agents of change
      5. Document important points
   7. Self-organization
      1. Team members organized around the work, taking the initiative to improve the process at all levels
2. I'am KMP 1
   1. https://edu.leankanban.com/users/darya-manukhina
   2. Statistics!
   3. Flow rate determined by the weakest link
   4. Be in the context of reality
   5. There are no formulas for assessing WIP
   6. SDM is a manager!
3. Project 2
   1. hart project for company
      1. a lot of legacy code
      2. https://www.xmind.net/m/uqGF/
   2. STATIK
      1. https://connected-knowledge.com/2018/04/05/time-to-update-the-statik-a3/
   3. Problem
      1. Could not choose a tool to visualize the board
   4. Now. in progress
      1. The Teams unification
         1. + one new Team
      2. new kanban board design
   5. Summary
      1. Do not stop
      2. Individuals and interactions over processes and tools
         1. https://agilemanifesto.org
4. Project 3
   1. A lot of new technologies
   2. Steps
      1. Kanbanization of Editor Service. Service Result: Report
      2. Discovery Kanban: from idea to US
         1. Us can go at any stage
      3. Kanban for the Product Team: we try to solve current problems
   3. What we wanted to treat
      1. Don't like tracker
      2. No understanding of project goals
      3. Too many events
      4. No PO
      5. Lack of resources
      6. Burnout
         1. https://www.xmind.net/m/Kudc/
   4. Summary
      1. Kanban is not a silver bullet!
      2. We should not implement Kanban, just because we played enough with Scrum!
5. Project 4
   1. kanban in operational management
      1. STATIK
6. Important!
   1. Never compromise quality!
   2. Be Agile! DevOps! Be better!
   3. Do not hold on to the past!