Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

зотин Scrum, kanban, что дальше. история nokia

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

  • Be the first to like this

зотин Scrum, kanban, что дальше. история nokia

  1. 1. Scrum, Kanban… Что дальше? История Nokia Антон Зотин
  2. 2. Кто я? ✴ 13 лет в IT ✴ 11 лет Agile ✴ опыт работы от тестера до топ-менеджера ✴ Agile Coach
  3. 3. Кто вы?
  4. 4. Что вы узнаете/ не узнаете из этого доклада?
  5. 5. Немного истории
  6. 6. Networks HERE Technologies Mobile
  7. 7. Структура команды
  8. 8. ProdM PO+SM PrjM
  9. 9. Design DevOps
  10. 10. Боевой опыт
  11. 11. Инженерные практики • покрытие unit-тестами >85% • парная работа • обязательное ревью кода • code quality pedants • continuous integration • continuous deployment
  12. 12. Инженерные практики
  13. 13. Достигнуто
  14. 14. Что хотелось улучшить?
  15. 15. Осень-зима 2014
  16. 16. • TEAM OWNERSHIP: Our team knows web mapping. We love our product. We will take the business goals and design/implement amazing solutions to fulfill these goals. • MEASURABLE AND TIME-BOXED PROJECT MISSIONS: Project teams get a single “project mission”, project success metrics and mutually agreed time box (in # of weeks allocation). When the project is completed, the team stops working on the project and gets staffed onto new projects. • SELF-ORGANIZED TEAMS: We will form self-organized teams organized for a specific mission. Different disciplines are added to the teams (or available “as a service”) as the teams decide. • WORK HOW YOU WANT BUT KNOW WHERE YOU ARE: Teams can chose their way of working (Scrum or Kanban or …), but they must be able to report burn-down of scope (completion vs. target) and performance against project metrics at any time of the project.
  17. 17. • REVIEW, DON’T SPECIFY: Teams review their work weekly with a product manager, but product managers are NOT allowed to write JIRA tickets (or other types of specification). • DONE MEANS DONE: Code goes into “maintenance” when project completes, i.e. bugs will not get fixed unless critical. Because of that, project acceptance will have strict quality requirements. • END TO END: Teams are responsible for getting their feature into production, load testing, measuring user metrics, looking for errors/problems, etc . • EVERYONE IS AN INNOVATOR: Everyone can request a project (ideally supported by a research week prototype), projects are accepted on the basis of business relevance (how does it fit the proposition / roadmap) and differentiation potential.
  18. 18. Миссии и сроки
  19. 19. Разбиение на команды
  20. 20. Дележ офисного пространства
  21. 21. Исследовательская неделя
  22. 22. Первые шаги…
  23. 23. Синхронизация команд
  24. 24. Синхронизация команд
  25. 25. Синхронизация команд
  26. 26. Синхронизация команд
  27. 27. Что делают РО?
  28. 28. Что делают менеджеры?
  29. 29. Командная динамика
  30. 30. Т-образный специалист
  31. 31. Неожи да нно ст…и
  32. 32. Чего достигли уже сейчас?
  33. 33. Что дальше?
  34. 34. Финальное предостережение
  35. 35. Антон Зотин Agile Coach +49 151 216 90225 @antonzotin