This document discusses research into factors that influence whether developers communicate around code changes. It presents findings from surveys and interviews with developers on items like code reviews, approvals, fixes and social factors that encourage discussion. It also covers how development mode, risk perception, business goals and guidelines can impact communication. The overall goal appears to be using this research to design tools that facilitate productive discussion around code changes.

1. To Talk orCommunication around Change-Sets
Factors that Influence
Not to Talk
Adrian Jorge Daniela Irwin
Schroeter Aranda Damian Kwan

2. What is a Change-Set?

3. What is a Change-Set?

4. What is a Change-Set?

5. What is a Change-Set?

6. What is a Change-Set?

7. What is a Change-Set?
The difference is in the lines.

9. The Development Team

10. The Development Team

11. The Development Team

13. Data Collection

14. Observation

15. Participant
Observation

16. Participant
me
Observation

17. Interviews
Let me tell you a war story
from the old days, when developers
were still real developers.

18. Surveys

19. Surveys
Process

20. Surveys
Process Developer

21. Surveys
Process Developer Code

22. Surveys
Process Developer Code
Rank items by likelihood that it would make
you talk to another developer

23. Surveys
Process Developer Code
In Endgame
Rank items by likelihood that it would make
you talk to another developer

24. Surveys
Process Developer Code
In Endgame
Code Review
Need Approval
Verify Fix
Role
Rank items by likelihood that it would make
you talk to another developer

25. Surveys
Process Developer Code
In Endgame Experience
Code Review
Need Approval
Verify Fix
Role
Rank items by likelihood that it would make
you talk to another developer

26. Surveys
Process Developer Code
In Endgame Experience
Code Review Work Quality
Need Approval Same Team
Verify Fix Met in Person
Role Location
Rank items by likelihood that it would make
you talk to another developer

27. Surveys
Process Developer Code
In Endgame Experience API Change
Code Review Work Quality
Need Approval Same Team
Verify Fix Met in Person
Role Location
Rank items by likelihood that it would make
you talk to another developer

28. Surveys
Process Developer Code
In Endgame Experience API Change
Code Review Work Quality Complex Code
Need Approval Same Team Your Code
Verify Fix Met in Person Bug Fix
Role Location Re-factoring
Rank items by likelihood that it would make
you talk to another developer

29. Research Findings

30. Development Mode
t

31. Development Mode
Release
t

32. Development Mode
Release
Let’s develop
features!
t

33. Development Mode
Release
Let’s develop
features!
t

34. Development Mode
Release
Let’s develop
features!
t
Do not break
the build!

35. Development Mode
Release
Let’s develop
features!
t
Do not break
the build!

36. Perception
Perception

37. Risk Assessment

38. Risk Assessment
“with every tenth bug fix
you introduce another bug
to the system”

39. Business Goals
Quality Work Company Survival

40. Business Goals
Quality Work Company Survival
“I want to be proud
of my work”

41. Business Goals
Quality Work Company Survival
“I want to be proud “we need to ship”
of my work”

42. Design Guidelines

43. Development Mode
Release
t

44. Development Mode
Release
t
Guideline #1:
Tools should adjust to mode dependent
information needs.

45. Perception
Perception

46. Perception
Guideline #2:
Tools should leverage
social factors.
Perception

47. Business Goals
Quality Work Company Survival

48. Business Goals
Quality Work Company Survival
Guideline #4:
Tools should account for alternative goals.

49. Conclusion

50. Conclusion

51. Conclusion

52. Conclusion

53. Conclusion