Scrum is really good at turning task into solution. Problem is that it is very hard to know in advance if your tasks are "make this waste" or "create this value". This is where Lean comes to the rescue. By putting high emphasis on measurements and experimentation you can turn your guesses into real high value tasks. Definition of done should not be only technical. Each task should be measured from business side and be done only when business kpis are hit or we have learned why our guess was wrong. Presentation will include short intro into Lean and practical examples of applying Lean thinking in pre and post development phases of the tasks.

1. Scrum meats Lean
Rokas Antanas Balevičius

8. Lean

9. Philosophy of improvement through waste reduction

13. Patient perspective

14. Doctor

15. Doctor Nothing

16. Doctor DoctorNothing

17. Doctor Doctor Doctor DoctorNothing Nothing Nothing Nothing

18. Doctor Doctor Doctor Doctor
Treatment
starts
Nothing Nothing Nothing Nothing

19. Doctors perspective

20. Day
start
Day end

21. Patient Patient Patient Patient PatientPatient
Day
start
Day end

22. Optimization of resources not patient value

23. Doctor Doctor Doctor Doctor
Treatment
starts

24. Patient Patient Patient PatientNothing Nothing NothingDay start Day end

25. Now you can see and reduce waste

26. Back to Scrum

27. Backlog : prioritized list of features

28. Business value?

29. Prioratized list of hypothesis

36. Create Knowledge

37. Genchi Genbutsu

38. Trying to sell my product

40. Uncover great guessers

42. One-Piece-At-a-Time Production

43. Developers are way ahead in this challenge

44. Definition of done : technical vs business

47. Bad Great
Intensityoffeedback

48. Bad Great
Intensityoffeedback

50. You can not care about someone who hates you

51. Key learnings

52. Challenge your Product Owner

53. Introduce yourself to Lean

54. Create your backlog
not just own it

55. Measure your decisions

56. Challenge me!