Teams CS4911 Fall 2007
What is a Team? <ul><li>“ A small number of people  </li></ul><ul><ul><li>with complementary skills </li></ul></ul><ul><ul...
Highly Effective Teams <ul><li>Shared vision </li></ul><ul><ul><li>Common big picture </li></ul></ul><ul><ul><li>Builds tr...
Software Project Roles <ul><li>Programmer </li></ul><ul><li>Project Manager </li></ul><ul><li>Technical Lead  </li></ul><u...
Possible Organization <ul><li>Team Leader/Project Manager </li></ul><ul><ul><li>Motivate team members </li></ul></ul><ul><...
Possible Organization (2) <ul><li>Development Manager </li></ul><ul><ul><li>Lead team in producing development strategy </...
Possible Organization (3) <ul><li>Planning Manager </li></ul><ul><ul><li>Lead the team in producing project plan </li></ul...
Possible Organization (4) <ul><li>Quality/Process Manager </li></ul><ul><ul><li>Lead team in producing and tracking the qu...
Possible Organization (5) <ul><li>Support Manager </li></ul><ul><ul><li>Lead team in defining support needs and obtaining ...
Why Teams Can Fail <ul><li>Personnel Problems </li></ul><ul><ul><li>Team leaders unwilling to confront and resolve problem...
Dysfunctional Team Members <ul><li>Hitchhikers </li></ul><ul><li>Couch Potatoes </li></ul>
Some Advice... <ul><li>Everyone on your team should not be exactly like you </li></ul><ul><li>Remember diversity of projec...
Team Selection
Upcoming SlideShare
Loading in …5
×

Teams

977 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
977
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Teams

  1. 1. Teams CS4911 Fall 2007
  2. 2. What is a Team? <ul><li>“ A small number of people </li></ul><ul><ul><li>with complementary skills </li></ul></ul><ul><ul><li>who are committed to a common purpose, </li></ul></ul><ul><ul><li>performance goals, and </li></ul></ul><ul><ul><li>approach </li></ul></ul><ul><ul><li>for which they hold themselves mutually accountable” </li></ul></ul><ul><ul><li>[Katzenbach & Smith] </li></ul></ul><ul><li>“ When two heads together are better than two heads individually” [McConnell] </li></ul>
  3. 3. Highly Effective Teams <ul><li>Shared vision </li></ul><ul><ul><li>Common big picture </li></ul></ul><ul><ul><li>Builds trust </li></ul></ul><ul><li>Commitment to the Team </li></ul><ul><ul><li>Team supercedes individual </li></ul></ul><ul><ul><li>Desire to contribute </li></ul></ul><ul><li>Interdependence among Team </li></ul><ul><ul><li>Rely on strengths </li></ul></ul><ul><ul><li>Everybody contributes </li></ul></ul><ul><li>Effective communication </li></ul><ul><ul><li>Constant & clear </li></ul></ul><ul><ul><li>Mutual understanding </li></ul></ul><ul><ul><li>Bad news too </li></ul></ul>
  4. 4. Software Project Roles <ul><li>Programmer </li></ul><ul><li>Project Manager </li></ul><ul><li>Technical Lead </li></ul><ul><li>Tester </li></ul><ul><li>Technical Writer/ Documentation Coordinator </li></ul><ul><li>Analyst </li></ul><ul><li>Designer </li></ul><ul><li>Marketing </li></ul><ul><li>Customer Delivery </li></ul><ul><ul><li>Installation </li></ul></ul><ul><ul><li>Configuration </li></ul></ul><ul><ul><li>Training </li></ul></ul>
  5. 5. Possible Organization <ul><li>Team Leader/Project Manager </li></ul><ul><ul><li>Motivate team members </li></ul></ul><ul><ul><li>Plan/Run Meetings </li></ul></ul><ul><ul><li>Prepare weekly status reports </li></ul></ul><ul><ul><li>Allocate tasks/workload </li></ul></ul><ul><ul><li>Maintain project files </li></ul></ul><ul><ul><li>Act as development engineer </li></ul></ul>
  6. 6. Possible Organization (2) <ul><li>Development Manager </li></ul><ul><ul><li>Lead team in producing development strategy </li></ul></ul><ul><ul><li>Prepare time and size estimates for product </li></ul></ul><ul><ul><li>Lead in development of SRS </li></ul></ul><ul><ul><li>Lead in producing design </li></ul></ul><ul><ul><li>Lead in development of SDS </li></ul></ul><ul><ul><li>Lead in developing test plan for development, integration and system testing </li></ul></ul><ul><ul><li>Lead in developing test materials and running tests </li></ul></ul><ul><ul><li>Lead in producing user-level documentation </li></ul></ul><ul><ul><li>Act as development engineer </li></ul></ul>
  7. 7. Possible Organization (3) <ul><li>Planning Manager </li></ul><ul><ul><li>Lead the team in producing project plan </li></ul></ul><ul><ul><li>Lead team in developing schedule for next iteration </li></ul></ul><ul><ul><li>Lead team in producing the balanced task plan </li></ul></ul><ul><ul><li>Track teams progress against plan </li></ul></ul><ul><ul><li>Act as development engineer </li></ul></ul>
  8. 8. Possible Organization (4) <ul><li>Quality/Process Manager </li></ul><ul><ul><li>Lead team in producing and tracking the quality plan </li></ul></ul><ul><ul><li>Alert team leader to quality problems </li></ul></ul><ul><ul><li>Lead team in defining and documenting the processes and process improvement plan. </li></ul></ul><ul><ul><li>Establish team development standards </li></ul></ul><ul><ul><li>Review proposed changes to baseline </li></ul></ul><ul><ul><li>Act as moderator for reviews </li></ul></ul><ul><ul><li>Act as recorder at team meetings </li></ul></ul><ul><ul><li>Act as development engineer </li></ul></ul>
  9. 9. Possible Organization (5) <ul><li>Support Manager </li></ul><ul><ul><li>Lead team in defining support needs and obtaining tools and facilities </li></ul></ul><ul><ul><li>Chair Configuration Control Board and Configuration Control </li></ul></ul><ul><ul><li>Maintain the Configuration Control System </li></ul></ul><ul><ul><li>Maintain system glossary </li></ul></ul><ul><ul><li>Maintain issue and risk tracking system </li></ul></ul><ul><ul><li>Act as reuse advocate </li></ul></ul><ul><ul><li>Act as a development engineer </li></ul></ul>
  10. 10. Why Teams Can Fail <ul><li>Personnel Problems </li></ul><ul><ul><li>Team leaders unwilling to confront and resolve problems </li></ul></ul><ul><ul><li>Cover up ignorance </li></ul></ul><ul><ul><ul><li>“ I don’t know how to explain… it just works” </li></ul></ul></ul><ul><ul><li>Excessive desire for privacy </li></ul></ul><ul><ul><ul><li>“ I don’t need anyone to review my…” </li></ul></ul></ul><ul><ul><li>Territorial </li></ul></ul><ul><ul><ul><li>“ No one else can fix the bugs in my code.” </li></ul></ul></ul><ul><ul><li>Grumble about team decisions & revisit past discussions </li></ul></ul><ul><li>Communication </li></ul><ul><ul><li>“ What we have here is a failure to communicate…” </li></ul></ul>
  11. 11. Dysfunctional Team Members <ul><li>Hitchhikers </li></ul><ul><li>Couch Potatoes </li></ul>
  12. 12. Some Advice... <ul><li>Everyone on your team should not be exactly like you </li></ul><ul><li>Remember diversity of project team roles </li></ul><ul><li>Be careful of mixing projects and close friends </li></ul><ul><li>Class is a lot of work… but it’s worth it </li></ul><ul><ul><li>Faculty Interaction </li></ul></ul><ul><ul><li>Letters of recommendation </li></ul></ul><ul><ul><li>Interview fodder </li></ul></ul><ul><li>Get on a project you have some interest in!!! </li></ul>
  13. 13. Team Selection

×