1. CSC 492 Senior Design Projects Lab Policies, GitHub, Submission System, Testing, Written Documentation Overview, Teaming CSC Senior Design Center Ms. Margaret Heil, Director Dr. Sarah Heckman, Mr. Ignacio Domínguez, Dr. Lina Battestilli, & Dr. David Sturgill, Technical Advisors Christa Cody, Nick Freeman & Zach Cleghern, TAs

2. Today’s Agenda n Lab Policies – IT Staff n GitHub & Submission System – Nick n Testing - Nick n IPR Guidelines – Ms. Heil n Brainstorm n Stages of Teaming n Ground Rules n Team Roles

3. First Section of Agenda n Lab Policies – IT Staff n GitHub & Submission System – Nick n Testing - Nick n IPR Guidelines - MRH IPR Guidelines - MRH

4. Second Section of Agenda n Brainstorm n Stages of Teaming n Ground Rules n Team Roles

5. Team “A Team is a small number of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they hold themselves mutually accountable.” From The Wisdom of Teams, Creating the High-Performance Organization - Katzenbach & Smith, 1993

6. Brainstorming Exercise Leadership

7. Four Stages of Teaming  Forming  Storming  Norming  Performing

8. Forming  Bringing People Together to Form a Team  Characterized by Uncertainty  Finding Out: z How members are chosen z Purpose z What do I do? Leader Directs

9. Storming  Occurs When a Team First Encounters Conflict  Struggle for Power  Finding Out: z If conflict resolving ground rules are effective! z That conflict can be positive Leader Coaches

10. Norming  How a Group Operates As a Team  Establishment of Norms Via Personalities & Ground Rules  Finding Out: z How members interact z Different learning/working styles z Individuals’ strengths & deficits Leader Supports

11. Performing  High Level Performance of Task  Evaluation of Work  Characterized by Confidence Leader Delegates

12. Situational Leadership 1 - Forming 2 - Storming 3 - Norming 4 - Performing Low High Directive Behavior Supportive Behavior Low High

13. Ground Rules: A Common Work Approach Guidelines Agreed Upon by Entire Team Used to Manage Decision Making & Conflicts Dynamic Define Roles n Posted in Work Space Reviewed at Each Meeting

14. Sample Ground Rules 1. Prepare Agendas for Each Meeting. 2. Be on Time. 3. Be Open to What Other Team Members Have to Say. 4. Support Participation from All. 5. Take Minutes - Rotate Responsibility. 6. Follow Agenda. 8. When Conflicts Arise, Follow These Rules: - Acknowledge that a problem exists. - Examine problem. - Explore alternatives. - Decide on most appropriate alternative.

15. Team Roles – Team Software Process n Team Leader n Development Manager n Planning Manager n Quality/Process Manager n Support Manager

16. Team Roles - Technical Function n Coordinator Of n Requirements Analysis n Design n Implementation n Testing & Usability n Documentation

17. Team Roles – Generic Managerial n Team Leader [Information Technology (I/T) Lead] n Team Facilitator n Team Member

18. Team Leader/Facilitator Conducts Team Meetings Encourages Participation by All Team Members Ensures That Meeting Minutes are Taken Leads Team in Decision Making Processes Keeps Team Focused on Purpose or Task Ensures Project File Maintenance

19. Team Leader/Facilitator Ensures Involvement of All Team Members Resolves Conflicts per Ground Rules Clarifies & Summarizes Key Points of Meetings Combines Ideas of Team Members to Help Reach Consensus Sometimes Makes Final Decision Updates Task Plan

20. Team Member Participates in Meetings & Decisions Makes Suggestions n Clarifies Ideas n Freely Asks for Clarification Prepares Presentations & Reports Helps to Establish & Follow Ground Rules Completes Tasks Records Minutes Evaluates Team Meetings