Engineering Software Engineering Teams - SSE 2011

1,105 views

Published on

Presentation from the 4th International Workshop on Social Software Engineering on "Engineering Software Engineering Teams".

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,105
On SlideShare
0
From Embeds
0
Number of Embeds
556
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Talk about other models of organizations, such as garbage can, distributed constraint satisfaction, etc
  • These are not the only views, but they are the prominent views. These two concepts came up quite a bit with regards to government fiscal stimuli.
  • We can initially have a nice layout for our team, and this may work with initial constraintsAny software that exists in an enterprise will have some issues with external stakeholders
  • We can initially have a nice layout for our team, and this may work with initial constraintsAny software that exists in an enterprise will have some issues with external stakeholders
  • People worked for “global blue” corporation
  • Engineering Software Engineering Teams - SSE 2011

    1. 1. Engineering Software Engineering Teams<br />Patrick Wagstrom<br />IBM TJ Watson Research Center<br />Presented at SSE’11 – September 5, 2011<br />
    2. 2. What Does an Organization Do?<br />MAGIC!<br />Bob, can you help me here?<br />Maybe Carl can help.<br />Can I act on this?<br />Info<br />Carl<br />Here’s the nugget of info you need.<br />Alice<br />More Info<br />Bob<br />September 5, 2011<br />2<br />
    3. 3. Hey! You Got Economics in my Software Engineering!<br />Keynesian<br />Austrian<br />September 5, 2011<br />3<br />
    4. 4. I am not an Economist<br />(nor do I play one on TV)<br />Keynesian<br />Austrian<br />Knowledge flows down<br />Knowledge flows up<br />September 5, 2011<br />4<br />
    5. 5. What about Software Engineering?<br />September 5, 2011<br />5<br />
    6. 6. Solutions?<br />Developer tools!<br />Bugzilla<br />SCM<br />Mailing lists<br />Integrated Tools<br />Rational Team Concert<br />GitHub<br />September 5, 2011<br />6<br />
    7. 7. What about Software Engineering?<br />September 5, 2011<br />7<br />
    8. 8. What We Did<br />Interviewed numerous developers, architects, managers, executives, etc<br />Part of a larger project to build tools to support the complete software delivery process<br />September 5, 2011<br />8<br />
    9. 9. General Findings<br />Projects had tried to work bottom up or top down, but failed<br />Often time there was one important cog<br />This person was well known<br />Not necessarily established rank<br />Significant pull with external stakeholders<br />Knowledge of the process<br />We call this person an intercessor<br />September 5, 2011<br />9<br />
    10. 10. Where it Gets Messy…<br />Sometimes managers were not aware of what intercessor did<br />Sometimes developers were not aware of what intercessor did<br />Intercessor may leave the organization and no one may know<br />Is there a way to empirically discover the intercessor?<br />September 5, 2011<br />10<br />

    ×