Anastasia Lieva, WiMLDS Paris

1. E
X
T
R
E
M
E
D
A
T
A
-
S
C
I
E
N
C
E
@fuzzyAnastazia
Anastasia Lieva

2. Once upon a time ...

3. EXTREME PROGRAMMING

5. ● Illusion of complete specifications
if customer is not on site
Bewitched links

7. ● Illusion of complete specifications
if customer is not on site
● No one is responsible
● Lack of communication
Bewitched links

9. Cost of change
Time

10. ● Illusion of complete specifications
if customer is not on site
● No one is responsible
● Lack of communication
● Technical debt
Bewitched links

11. ● Illusion of complete specifications
if customer is not on site
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

12. ● Illusion of complete specifications
if customer is not on site
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

13. ● Illusion of complete specifications
if customer is not on site
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

14. EXTREME PROGRAMMING
masterofproject.com

15. EXTREME PROGRAMMING
masterofproject.com

16. EXTREME PROGRAMMING
masterofproject.com

17. EXTREME PROGRAMMING
masterofproject.com

18. EXTREME PROGRAMMING
masterofproject.com

19. EXTREME PROGRAMMING
masterofproject.com

20. EXTREME PROGRAMMING
masterofproject.com

21. EXTREME PROGRAMMING
masterofproject.com

22. Data Science comparing to Traditional Software Development?

23. Data Science comparing to Traditional Software Development?
Rules
Data Outputs

24. Data Science comparing to Traditional Software Development?
Rules
Data Outputs
ML
Data Rules

25. ● Illusion of detailed specifications
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

27. ● Illusion of detailed specifications
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

28. ● Illusion of detailed specifications
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

29. ● Illusion of c̶o̶m̶p̶l̶e̶t̶e̶ ̶s̶p̶e̶c̶i̶f̶i̶c̶a̶t̶i̶o̶n̶s̶ miracles
if customer is not on site
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

30. ● Illusion of c̶o̶m̶p̶l̶e̶t̶e̶ ̶s̶p̶e̶c̶i̶f̶i̶c̶a̶t̶i̶o̶n̶s̶ miracles
if customer is not on site
● No one is responsible
● Lack of communication
● Technical debt
● Lack of visibility
Bewitched links

31. EXTREME DATA-SCIENCE

33. ● Metaphor

34. Collaborative workshops

35. ● Metaphor
● User Stories

36. The anomaly detection system
Epic
Build a prototype to detect the
anomalies in hot water tank
consumption

37. The anomaly detection system
Epic
Build a prototype to detect the
anomalies in hot water tank
consumption
Story 1
As a user I can store the consumption of my hot water tank so
that enable the data analysis for anomalies detection
Story 2
As a expert I can label the timestamps when a hot water tank has anomaly so that the data-scientist
can perform supervised learning of anomalies
Story 3
As a data-scientist I can create synthetic observations targeted as anomalies so that the original imbalanced
dataset not affect the machine learning performance especially regarding its sensitivity metric
Story 4

38. ● Metaphor
● User Stories
● Frequent small releases

40. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity

41. The anomaly detection system
Epic
Build a prototype to detect the
anomalies in hot water tank
consumption
Story 1
As a user I can store the consumption of my hot water tank so
that enable the data analysis for anomalies detection
Story 2
As a expert I can label the timestamps when a hot water tank has anomaly so that the data-scientist
can perform supervised learning of anomalies
Story 3
As a data-scientist I can create synthetic observations targeted as anomalies so that the original imbalanced
dataset not affect the machine learning performance especially regarding its sensitivity metric
Story 4

43. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring

44. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team

47. Workshops with end-users

48. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team
● Pair Programming

50. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team
● Pair Programming
● Coding Standards

51. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team
● Pair Programming
● Coding Standards
● Collective code ownership

52. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team
● Pair Programming
● Coding Standards
● Collective code ownership
● Test driven development

53. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team
● Pair Programming
● Coding Standards
● Collective code ownership
● Test driven development & Test EVERYTHING

55. ● Metaphor
● User Stories
● Frequent small releases
● Simplicity
● Refactoring
● Whole Team
● Pair Programming
● Coding Standards
● Collective code ownership
● Test driven development & Test EVERYTHING
● Continuous integration

56. ● Communication
● Simplicity
● Feedback
● Courage
EXTREME DATA-SCIENCE

57. Thank you !
@fuzzyAnastazia Illustrations by Marina Bobyreva @marinaboby