PM Day Kharkiv 2019. Denys Ryzhykh

1. И тут мне говорят….
Мы должны работать по скраму

2. Myth No 1
Project Goal = deliverables
Deliverables = Project Goal

4. Myth No 1
Project Goal = deliverables
Deliverables = Project Goal

10. Myth No 1
Project Goal = deliverables
Deliverables = Project Goal
● MVP
● Sprint goal
● User Story construct

15. Myth No 2
Satisfy Customer = deliverables

16. Myth No 2
Satisfy Customer = deliverables
● Scrum team is a luxury for saving funds
● Fail Fast, Fail Cheap
● Maximize work not Done

17. ● Scrum team is a luxury for saving funds
● Fail Fast, Fail Cheap
● Maximize work not Done

18. Myth No 3
Team productivity can be measured
● Deliverables is not a “Business Value” delivered
● Faking Agile Metrics
● NPS
● Learning metrics

19. ● Deliverables is not a “Business Value” delivered

20. ● Faking Agile Metrics
Goodhart's law
“Any observed statistical regularity will tend to collapse
once pressure is placed upon it for control purposes”.
https://en.wikipedia.org/wiki/Goodhart%27s_law

21. ● Faking Agile Metrics
● Accept “mostly” done Product Backlog items as done, and create new tasks to finish them at a
later stage
● Accept “buggy” items and create new Product Backlog items to fix the issues
● Add points to spikes or bugs
● Include tickets from other teams on your board
● Open and then close fake tickets
● Add tickets for Scrum events
● Change the base value of points/the reference stories
● Multiply the estimate of user stories by 2, use higher numbers during estimation
● Reestimate stories by increasing their complexity after implementation
● Add story points to each sub-task of an item
● Add story points to epics additionally
● Do it slow and steady to show steady growth; do not over-deliver at any time
● In the case of spillover, collect the story points partially and create a new user story with the full
estimate for the new Sprint
● Automate tasks and pretend they are still done manually
● Slice an issue into several smaller issues that collectively have a higher estimate.
https://age-of-product.com/faking-agile-metrics/?fbclid=IwAR0a8Klrh8itD-YUIfg91ZU7caT-7v922L2yy1oJre9N5L7UgeSRAyD-gII

22. ● NPS
● Learning metrics
https://holub.com/kpis-velocity-and-other-destructive-metrics/
● the number of experiments you've performed
● the number of process and institutional changes instigated by those
experiments
● the number of things you've learned in the past month
● the number of validated business-level hypotheses you've developed
● the number of times a week you talk to an actual customer
● the number of changes to your backlog (if it's not changing, why not?)

23. ● EBM - Evidence Based Management

24. Myth No 4
The Scrum Team is something that we can run just
by conducting Scrum ceremonies

25. Myth No 4
The Scrum Team is something that we can run just
by conducting Scrum ceremonies
● Long Run
● Learning Mindset, Responsibility process
● Summerhill school

29. Afraid of showing up with
unfinished work
-----
Criticizing unfinished work

33. Инженерные команды
Recruitment
Уютный Open Space
Питание в офисе
Развозка
Соц.пакет
Командировки
Менторство
Дружный коллективОКБ 29 (Шарага)

34. Myth No 5
Hire 2 seniors, multiple juniors, mentorship…
...more testers
● No grades
● All professionals
● Team responsibility
● Soft skills
● Power Distance -> waterfall
● “Life sucks”

35. ● No grades
● All professionals
● “Life sucks”

36. ● Soft skills
● Power Distance -> waterfall
● “Life sucks”
Опыт Категоричность

37. ● Team responsibility
● Power Distance -> waterfall
Power
Knowledge

38. ● Team responsibility
● Power Distance -> waterfall

39. ● Team responsibility
● Power Distance -> waterfall

40. ● Team responsibility
● Power Distance -> waterfall
BA
Dev
QA

41. ● Team responsibility
● Power Distance -> waterfall
BA
Back End
Dev
QA
Front End
Dev

42. ● Team responsibility
● Power Distance -> waterfall
BA Team
Back End
Team
Team
Front End
Team

43. ● Team responsibility
● Power Distance -> waterfall
BA Team
Back End
Team
Team
Front End
Team

44. Myth No 6
Scrum Master is responsible for team’s efficiency
● Lefferts law
● Services of the Scrum Master
● One parents blame other parents

45. Myth No 6
Scrum Master is responsible for team’s efficiency
● Lefferts law

46. ● One parents blame other parents

47. ● Services of the Scrum Master

48. ● Services of the Scrum Master

49. Myth No 7
The Customer will appoint a first random Executive
to act as a Product Owner
● Introduce in person
● Why does he/she is (not)interested
● Customer is not the End User
● It is not the person which the Team shall please
● Do not hire a Proxy!

50. Myth No 8
Proxy Product Owner would facilitate
communication
● Yet it is not another person which the Team shall please
● Power Distance -> waterfall
● Team Language (Transparency, Openness,
Individuals and Interactions)

51. ● Cognitive Biases
● Barely Sufficient
● Documentation - afterwards

52. Myth No 9
Fixed Price Projects are good enough to be
managed along with the Scrum framework
● Trust <-> Courage
Fear Trust

53. А теперь - Котики

54. А теперь - Котики Кодики

55. Denys Ryzhykh
14.Dec-15.Dec.2019
Провожу тренинг в Харькове
Agile Certified Professional
-10%
tinyurl.com/engteams
facebook.com/Engineeringteams
%KPMD%
Promo-Кодик