To Talk orCommunication around Change-SetsFactors that Influence                      Not to TalkAdrian    Jorge    Daniela...
What is a Change-Set?
What is a Change-Set?
What is a Change-Set?
What is a Change-Set?
What is a Change-Set?
What is a Change-Set?  The difference is in the lines.
The Development Team
The Development Team
The Development Team
Data Collection
Observation
Participant              Observation
Participant       me              Observation
Interviews    Let me tell you a war storyfrom the old days, when developers      were still real developers.
Surveys
SurveysProcess
SurveysProcess   Developer
SurveysProcess   Developer   Code
SurveysProcess         Developer        CodeRank items by likelihood that it would makeyou talk to another developer
SurveysProcess         Developer        CodeIn EndgameRank items by likelihood that it would makeyou talk to another devel...
SurveysProcess         Developer        CodeIn EndgameCode ReviewNeed ApprovalVerify FixRoleRank items by likelihood that ...
SurveysProcess         Developer        CodeIn Endgame       ExperienceCode ReviewNeed ApprovalVerify FixRoleRank items by...
SurveysProcess         Developer        CodeIn Endgame       ExperienceCode Review      Work QualityNeed Approval    Same ...
SurveysProcess         Developer        CodeIn Endgame       Experience      API ChangeCode Review      Work QualityNeed A...
SurveysProcess         Developer        CodeIn Endgame       Experience      API ChangeCode Review      Work Quality    Co...
Research Findings
Development Mode                   t
Development Mode      Release                   t
Development Mode              Release Let’s develop  features!                        t
Development Mode              Release Let’s develop  features!                        t
Development Mode               Release  Let’s develop   features!                         tDo not break the build!
Development Mode               Release  Let’s develop   features!                         tDo not break the build!
PerceptionPerception
Risk Assessment
Risk Assessment “with every tenth bug fix  you introduce another bug  to the system”
Business GoalsQuality Work   Company Survival
Business Goals   Quality Work       Company Survival“I want to be proud  of my work”
Business Goals   Quality Work       Company Survival“I want to be proud   “we need to ship”  of my work”
Design Guidelines
Development Mode      Release                   t
Development Mode                   Release                                            tGuideline #1:    Tools should adjus...
PerceptionPerception
PerceptionGuideline #2:    Tools should leverage    social factors.Perception
Business GoalsQuality Work   Company Survival
Business Goals    Quality Work           Company SurvivalGuideline #4:   Tools should account for alternative goals.
Conclusion
Conclusion
Conclusion
Conclusion
Conclusion
Talk or Not to Talk @ CSCW 2012
Talk or Not to Talk @ CSCW 2012
Upcoming SlideShare
Loading in …5
×

Talk or Not to Talk @ CSCW 2012

1,821 views

Published on

My original presentation at cscw 2012, I'll try to make a web version of that as soon as i find the time

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,821
On SlideShare
0
From Embeds
0
Number of Embeds
995
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Talk or Not to Talk @ CSCW 2012

  1. 1. To Talk orCommunication around Change-SetsFactors that Influence Not to TalkAdrian Jorge Daniela IrwinSchroeter Aranda Damian Kwan
  2. 2. What is a Change-Set?
  3. 3. What is a Change-Set?
  4. 4. What is a Change-Set?
  5. 5. What is a Change-Set?
  6. 6. What is a Change-Set?
  7. 7. What is a Change-Set? The difference is in the lines.
  8. 8. The Development Team
  9. 9. The Development Team
  10. 10. The Development Team
  11. 11. Data Collection
  12. 12. Observation
  13. 13. Participant Observation
  14. 14. Participant me Observation
  15. 15. Interviews Let me tell you a war storyfrom the old days, when developers were still real developers.
  16. 16. Surveys
  17. 17. SurveysProcess
  18. 18. SurveysProcess Developer
  19. 19. SurveysProcess Developer Code
  20. 20. SurveysProcess Developer CodeRank items by likelihood that it would makeyou talk to another developer
  21. 21. SurveysProcess Developer CodeIn EndgameRank items by likelihood that it would makeyou talk to another developer
  22. 22. SurveysProcess Developer CodeIn EndgameCode ReviewNeed ApprovalVerify FixRoleRank items by likelihood that it would makeyou talk to another developer
  23. 23. SurveysProcess Developer CodeIn Endgame ExperienceCode ReviewNeed ApprovalVerify FixRoleRank items by likelihood that it would makeyou talk to another developer
  24. 24. SurveysProcess Developer CodeIn Endgame ExperienceCode Review Work QualityNeed Approval Same TeamVerify Fix Met in PersonRole LocationRank items by likelihood that it would makeyou talk to another developer
  25. 25. SurveysProcess Developer CodeIn Endgame Experience API ChangeCode Review Work QualityNeed Approval Same TeamVerify Fix Met in PersonRole LocationRank items by likelihood that it would makeyou talk to another developer
  26. 26. SurveysProcess Developer CodeIn Endgame Experience API ChangeCode Review Work Quality Complex CodeNeed Approval Same Team Your CodeVerify Fix Met in Person Bug FixRole Location Re-factoringRank items by likelihood that it would makeyou talk to another developer
  27. 27. Research Findings
  28. 28. Development Mode t
  29. 29. Development Mode Release t
  30. 30. Development Mode Release Let’s develop features! t
  31. 31. Development Mode Release Let’s develop features! t
  32. 32. Development Mode Release Let’s develop features! tDo not break the build!
  33. 33. Development Mode Release Let’s develop features! tDo not break the build!
  34. 34. PerceptionPerception
  35. 35. Risk Assessment
  36. 36. Risk Assessment “with every tenth bug fix you introduce another bug to the system”
  37. 37. Business GoalsQuality Work Company Survival
  38. 38. Business Goals Quality Work Company Survival“I want to be proud of my work”
  39. 39. Business Goals Quality Work Company Survival“I want to be proud “we need to ship” of my work”
  40. 40. Design Guidelines
  41. 41. Development Mode Release t
  42. 42. Development Mode Release tGuideline #1: Tools should adjust to mode dependent information needs.
  43. 43. PerceptionPerception
  44. 44. PerceptionGuideline #2: Tools should leverage social factors.Perception
  45. 45. Business GoalsQuality Work Company Survival
  46. 46. Business Goals Quality Work Company SurvivalGuideline #4: Tools should account for alternative goals.
  47. 47. Conclusion
  48. 48. Conclusion
  49. 49. Conclusion
  50. 50. Conclusion
  51. 51. Conclusion

×